Voyager

8047 readers
37 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 this behavior randomly, across multiple accounts. This happens when using both lemmy and piefed accounts.

The only work around I've found is to block a community which forces a reload.

Not sure why it is happening, but it's frustrating to keep having to either reload the feed or block and unblock a community.

Appreciate the app, it's awesome, just figured I'd report the issue!

3
 
 

There is an option under settings>filters>looking for language filters, but adding a language does not work. Is there a way to filter out posts in languages I don’t speak?

4
 
 

Is there any plan on voyager making logins to piefed possible?

5
 
 

When I minimise the app and come back, or let my phone sleep and come back, Voyager puts a large blank border around the whole UI and begins behaving strangely. Sometimes it crashes, but most times, buttons and gestures stop working.

This happens when tabbing away or when the phone sleeps.

iOS 26.3 on iPhone 13.

Voyager 2.43.2

6
 
 

Not sure if I’m missing a setting or a visual cue, is there a way to identify an edited comment from the front end?

7
 
 

How the bug occurs

  • have Voyager open
  • receive a text from an app that uses bubbles
  • type a reply back in the bubble
  • gray screen where keyboard was and pushes the Voyager app up

This didn't use to happen before. Not sure how to fix the issue aside from restarting Voyager every time it happens

8
 
 

Sometimes when browsing the “All” feed, I will come across a post and recognize that I definitely do not want to see posts from its community in the future.

It would be nice if “Block Community” was added as an option from the “more” (…) button in each post of the feed view.

Unless I am missing a simpler way to block a community from the feed view which doesn’t involve navigating to the community feed in question and then choosing “block community” from there…

9
 
 

Blocked users’s comments still show up in my feed, but when I click on the account, it looks like the block is working. This is on piefed.zip.

10
 
 

When I attempt to edit a comment that I already submitted, especially if I'm trying to backspace text, I put the text cursor at the desired part of my comment but if I backspace more than once (i.e. holding the backspace button), the cursor jumps to the very end and starts deleting the end of the comment.

Interestingly this very same glitch would happen to me on the reddit app when I used to use reddit.

Does anyone else get this on Voyager? Is it a known bug?

Edit: I suppose it would be helpful to add, I'm on Android.

11
 
 

Howdy!

Just a random question that came to mind. When browsing all the instances, plenty are in foreign languages for me, such as the German one in the pic.

Is there a native way in Voyager to translate into English?

12
 
 

Basically the title. When I comment, the app zooms out.

13
 
 

Just a heads up.

14
 
 

The stats surprised me. I had no idea I'd commented that much!

15
 
 

@aeharding@vger.social

I can’t seem to get my piefed.zip account to connect. It was working fine a day or two ago, but now all I get is the spinning circle. I have a couple of other. piefed accounts, and Voyager connects just fine to them. Any idea what could be causing this?

16
 
 

iOS User here

Noticed yesterday that using the “Share” function is generating an intermediary vger.to link that encourages the viewer to download the Voyager app.

That link shows the text from a post, but other content like Video is missing.

Lemmy is already plenty readable from a browser. If I want send someone a link to something, I now have extra steps to copy and paste the URL. Defeats the point of the share button, doesn’t it?

I’d expect this behavior from corpo social media like Facebook or Reddit, it’s a bit disappointing to be seeing it from what is otherwise my favorite Fediverse app.

Is there any justification for this behavior that I’m not considering?

17
 
 

I’ve held off posting about this for a while since I assume it’s known or being worked on but it’s been long enough. Any time I block a community in a feed it jumps back up the feed by a significant amount and even unloads previously loaded post. As opposed to handling it like Mlem, for example, which just removes the relevant post you used to block the comm and keeps you in the same position. Also Voyager has been crashing a good amount for me lately but hopefully a cache clear will fix this.

Edit: There you go didn’t expected this to be so common. Also for posterity, cache clear doesn’t seem to have helped.

18
16
submitted 1 month ago* (last edited 1 month ago) by CombatWombatEsq@lemmy.world to c/voyagerapp@lemmy.world
 
 

I was super excited to see that Voyager added experimental support for Piefed. I went a created an account on feddit.online, and tried to log in… and got a connection error. No worries, it’s experimental. That was like 5 months ago and it’s still happening and I’m starting to suspect it’s not going to get better on its own. I use a password manager, and it’s saying “connection error” so I feel like it’s probably not bad credentials? Did I choose a bad instance or is this client-side?

19
 
 

iPhone 17 Pro, iOS 26.2. When looking at a post if I sleep my phone and unlock it, the Voyager window will look shrunken, not filling the screen. The top bar remains the same. Force quitting and reopening resolves the issue.

20
 
 

Hopefully I’m just doing something wrong but I still see comments from users I have blocked on Voyager. Is this a known bug?

21
 
 

If I close the browser and later go back it throws up the little update flag even though I am on the version the update is offering.

22
 
 

Lemmy seems to be overrun by post and ditch throwaway accounts right now posting controversial or divisive content. Because these accounts are created, post, and self delete their accounts and repeat you can't simply just block these users. This is happening on multiple instances and communities too so you also can't just filter out the offending instance.

Please add a filter for content posted by new accounts. Lemmy already has a New Account Highlightenator feature, which is helpful (tho sometimes the baby face tag gets pushed off screen if the username is long when Always Show Author is turned on), but I'd like to just not see anything from these accounts. Not a perfect solution, but could be helpful.

Edit: Looks like the bot people don't like this idea since it's already being downvoted by accounts that no longer exist.

Edit 2: Just watching them come in. Up to 8 now and not one of these accounts exist any longer. Just proving my point that they really don't want to be filtered out.

23
 
 

sh.itjust.works seems fine in a web browser, but it doesnt load for me on Voyager. Am I the only one with this problem?

24
 
 

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

So, I joined Lemmy.world as it was the biggest instance.

Is there a way that does not include creating another two or three basically pointless accounts to view other instances in the "local" view.

For example: Say that I am Canadian, (I am not, but it works for this example) and I joined the lemmy.ca, but I also want to see what goes on at sh.itjust.works without having to subscribe to every single community in both.

25
 
 

So I'm reading a post, tab out for a while, and when I come back the app reloads and I have not found any way to go back to said previous post, is there any way to view a history of read posts? And if there isn't, are there any clients that do have this feature?

And before anyone brings up likes and saves, those aren't in the order that I read them, but in the order that they're originally posted. I know that in lemmy 1.0.0 they've megred better like ordering, but until lemmy v1 releases I would like to know how I can go back to read things I wasn't finished reading yet, either on this app or alternatives

Thank you!

view more: next ›