Voyager

7032 readers
15 users here now

The official lemmy community for Voyager, an open source, mobile-first client for lemmy.

Download on App Store

Download on Play Store

Use as a Web App

Download on F-Droid

Rules

  1. Be nice.
  2. lemmy.world instance policy

Sponsor development! 👇

Number of sponsors badge

💙

founded 2 years ago
MODERATORS
1
 
 

Voyager now has experimental Piefed support in the App Store and Play Store. F-droid rolling out soon. 🥳

Make sure your app is up to date (v2.37.0 or greater) and enjoy!

https://getvoyager.app/

P.S. Support is under active development and there are known and unknown issues. Please post any feedback or questions!

::: spoiler Background image credit

https://images.nasa.gov/details/hubble-observes-one-of-a-kind-star-nicknamed-nasty_17754652960_o

Astronomers using NASA’s Hubble Space Telescope have uncovered surprising new clues about a hefty, rapidly aging star whose behavior has never been seen before in our Milky Way galaxy. In fact, the star is so weird that astronomers have nicknamed it “Nasty 1,” a play on its catalog name of NaSt1. The star may represent a brief transitory stage in the evolution of extremely massive stars.

First discovered several decades ago, Nasty 1 was identified as a Wolf-Rayet star, a rapidly evolving star that is much more massive than our sun. The star loses its hydrogen-filled outer layers quickly, exposing its super-hot and extremely bright helium-burning core.

But Nasty 1 doesn’t look like a typical Wolf-Rayet star. The astronomers using Hubble had expected to see twin lobes of gas flowing from opposite sides of the star, perhaps similar to those emanating from the massive star Eta Carinae, which is a Wolf-Rayet candidate.

Instead, Hubble revealed a pancake-shaped disk of gas encircling the star. The vast disk is nearly 2 trillion miles wide, and may have formed from an unseen companion star that snacked on the outer envelope of the newly formed Wolf-Rayet. Based on current estimates, the nebula surrounding the stars is just a few thousand years old, and as close as 3,000 light-years from Earth.

2
 
 

I keep getting the same error message today: (It’s a screenshot, approximately 199kb)

“Problem uploading image: Failed to upload image. Please try again.”

  • Was able to post yesterday but not today. I managed to crop the screenshot to 70kb but still got the same error message.
  • cleared cache on Voyager settings, deleted and reinstalled Voyager
  • now it won’t let me post without photo
3
 
 

Can’t tell why. Inbox works great on all the other lemmy and piefed servers i’ve tried. But not quokk.au (piefed).

The inbox on quokk.au piefed web ui works good.

4
 
 

Ie.

My voyager blocklist looks empty on my quokk.au piefed account.

But on the pieded web UI i can see I have a long blocklist

5
6
17
Image zooming issue (startrek.website)
submitted 6 days ago* (last edited 5 days ago) by hopesdead@startrek.website to c/voyagerapp@lemmy.world
 
 

Hello. I’ve encountered an issue relating to zooming with images at random a few times within the last month. When attempting to zoom, at random the tap field will continue to zoom (even the pinch and pull gesture affects this) until the image has reached a maximum zoom. At this point the image will resize itself to the normal size or do nothing. Whenever this occurs, no other controls work. Only way to stop the behavior is force quoting the app.

EDIT: iPhone 13

7
 
 

I'm not really sure how describe this. Since about 2.37.2, whenever I go back to Home after being on one of the other tabs for a short while I end up in a different place from the one where I left Home.

I have marking as read on scroll turned on and I can see that the posts above my new position are unread.

I'm on the Android app and it still happens in 2.39.0.

Edit: Also, pressing Home to get to the top of the list doesn't work anymore when that happens. It just goes up a few posts at a time.

Edit 2: Just realised, the tab is called "Posts".

~~Edit 3: It doesn't happen when I'm on a post and then go back to the list.~~

Edit 4: Just happened after going back from a post.

8
9
 
 

Back again 30s later with another bug report, sorry lol. This one occurs when adding images to post text in piefed

10
 
 

Fair warning: I’ve checked the piefed web front end to see if this was an instance problem or a voyager problem, but wasn’t able to enable separated upvotes / downvotes on there so this might not be on your end of things. If that’s the case sorry for an irrelevant bug report!

The bug: certain posts show in piefed with -1 downvotes like so
post with -1 downvotes

While in lemmy they show zero downvotes

same post viewed from lemmy with zero downvotes

Interestingly, downvoting the post makes it zero downvotes which makes me wonder if it’s a piefed issue rather than voyager

same post from piefed, downvoted, with the downvotes now showing zero

Upvoting doesn’t affect the downvotes as you’d expect. I’ve seen this same bug with other posts, but this is the first one I’ve thought to snag screenshots of. Thanks!

11
 
 

I can't see pictures posted by feddit.org users in Voyager right now. When I view !ich_iel@feddit.org f.e., I see a lot of "Failed to load media".

And I can't use my feddit.org account in Voyager right now. It says "Failed to load more posts".

I don't experience these problems when I use Lemmy web UI.

Voyager 2.38.0 on Android

12
 
 

https://sh.itjust.works/post/41694715

For some reason, this link post is showing up as an image with no link for me.

13
 
 

I saw matrix.to, and was inspired. vger.to happened to be available and it much shorter than go.getvoyager.app. :)

Example: https://vger.to/lemmy.zip/post/43215939

14
 
 

Since I updated to the latest version of the app - to fix an issue I was having with another error, I can no longer view feddit.uk instance. I initially thought feddit.uk was down and went to view in browser. If I click from an external browser URL and point it to Voyager to control opening it, I get an unknown URL error after the attempt at loading has timed out. (See attached video). I can view other instances e.g. lemmy.ml or lemmy.world but not this one. I downloaded Jerboa just to check but haven't used it yet.

Edited to add video

EDITED - Thanks for the replies. It must be my devices so. I thought it might be my DNS settings which I have set to Adguard DNS, but I disabled that and it made no difference. I will do a fresh install of it tomorrow and see if that helps.

15
 
 

hi,all

I can't connect to the instance(fasheng.ing)
with use 2.37.2 version

but there's no problem with 2.36.0 version

Why is that :D

16
 
 

I am having an issue where after about 50 posts I'm getting an error message saying it failed to load media. I am using the beta version of the app so I am not sure if that plays a part. Never had this issue before. I've gone through my settings a couple times but couldn't see anything that changed. It happens on both the local and All feeds. Anyone know a solution?

17
 
 

I’d love to be able to configure Tapestry, my feed reader, to open Lemmy posts in Voyager, but not sure where to start.

I was able to configure it to open Mastodon posts in Ivory but Ivory showed up as an option. I don’t know if that was a hard coded option or if maybe the app is registered as a Mastodon client with the OS somehow?

18
 
 

I get "Failed to load media" message whenever I try to upload an image or video in voyager... 🤷

I tried again in the first comment below.

19
 
 

I have been running a personal lemmy server for a long time and using Voyager (web app). The other day I updated as I have done dozens of times before, and it wouldn’t load any posts. I tried logging out and clearing my cache, but when I try to log in to lemmy.masto.community, it just says there was a problem connecting.

The server is obviously up and working or I wouldn’t be able to post this. And logged out, I seem to be able to browse public servers with Voyager. It has just suddenly become incompatible with… something? This is a managed service on Elestio, so it’s maintained automatically.

I figured if I waited a few days it would sort itself out since I can’t be the only one. But I don’t see any posts about this so now I’m wondering if I’m the only one. Any ideas? Thanks!

20
 
 

Edit: Just realised this is a duplicate of https://lemmy.blahaj.zone/post/28237901

If your default comment sort isn’t “hot”, the when you look at the comments on a post it will be sorted by “hot”, your comment sort will only be applied to a post once you refresh that post.

21
 
 

cross-posted from: https://lemmy.world/post/32292198

Sometimes I really want to just delete a post but I think thats a bit heavy-handed and I keep hoping theres a way to simply mute it so its not disrupting me when I've moved on from it but dont want to invalidate all the repliers and also posterity

22
 
 

Reposted something, am getting notifications on the bottom bar for every reply. How can I deactivate that for that post only?

Thanks!

23
 
 

I have top comment order as default. I go into a post, the icon shows it's ordered by top comments. The comments aren't ordered by points though. If I change the order to something else and back to top, oy orders by top.

On GrapheneOS, voyager 2.37.0.

Edit: same on 2.37.1.

24
 
 

I noticed that in a /c view, post text is hidden by default for a media post.

Is there a way to have that text exposed by default?

Example: When viewing !trams_trolleys_streetcars@lemmy.blahaj.zone

I don't see the post text for my latest post to the /c : https://ani.social/post/16029609

edit: Looking at it further, It's emulating the Lemmy web interface: I have to click a little "+" icon next to the post's title to expose the post text there.

But there's no way to expose the post text with one click in Vger's /c or Home/All/Local/Moderator feed views.

25
 
 

My settings for default sort, appearance, favorites, etc. have reset twice this month, which I can't remember happening ever before. Is the problem on my end, or have there been app updates that required it?

I've found the backup/restore button now, so I can hopefully recover it next time.

view more: next ›