Voyager is now available on Flathub!
Enjoy!
Edit: Better keyboard navigation is coming soon(tm)
https://flathub.org/en/apps/app.vger.voyagerOpen linkView original on vger.socialEnjoy!
Edit: Better keyboard navigation is coming soon(tm)
https://flathub.org/en/apps/app.vger.voyagerOpen linkView original on vger.socialThis is a longstanding bug, and it’s partly YouTube’s fault. But it also appears that a small change could fix this issue on Voyager’s end.
Some, not all, but quite a lot, of videos will not show the thumbnail when browsing a community with large previews enabled.
My working theory:
The issue is the uploader didn’t make a dedicated thumbnail when they posted the video on YouTube. YouTube has to take a frame from the video itself and use that as the thumbnail on their website.
In Voyager, if a dedicated thumbnail was created, it shows up in all views. But if YouTube generated one from a video frame, it does not.
However, it does show all thumbnails when the Voyager previews are smaller.
For whatever reason, Voyager is willing to pull the YouTube-generated thumbnail in that view. Maybe it has to do with a resolution cut off, that generated thumbnails are usually from older, lower-resolution videos. But most all videos being uploaded today are in at least 1080p anyway. And a blurrry thumbnail would be preferable to the thumbnail meant to indicate a deleted video. I imagine it discourages people from clicking on them in the first place.
Is it possible to let the (potentially) smaller thumbnail through on large previews in Voyager?
Hi there
I really like voyager's ui and thanks hugely to the devs for making it. I'm probably being dumb but is there any way to join a "custom" instance, not in the list that defaults to lemmy.zip? I've created an account elsewhere.
I'm using 2.49.1, f droid installed.
Lately I’ve been encountering the issue where after so many posts (I havent counted how many) my feeds will end with “Failed to load more posts. Try again?”
The try again option doesn’t succeed in loading more posts.
I figured I’d post here to see if anyone else has encountered this issue lately as I recall it’s happening a few times in the past, but has been split between app issues and instances using outdated Voyager versions.
I’m using Voyager 2.49.1 on iOS. Thanks for any input!
Hi!
I don't know whether this bug is commonly known, or if it's something on my end. On both Firefox Desktop and Android, media, such as images and videos, randomly fail to load. This usually happens when browsing a media focused community, after interacting with a couple posts it seems to stop loading media correctly.
If I reload the page, sometimes that helps if I have the specific post open, but that has the annoying backlash that going back means reverting back to the top after the reload. Most of the times however, this is not a workaround and makes browsing a community rather annoying in general. Sometimes media are loaded when first seen (like when browsing All), but even then it will produce broken media posts daily.
Thank you!
cross-posted from: https://lemmy.world/post/53277250
I wanna host communities for obscure topics
Is there any way to suppress ads in Voyager? Given that the Israeli’s are using ads to spread malware not having them pop up is a priority.
Not sure if this is a Voyager thing or a my instance thing, but at least one a day my scrolling is interrupted by this
I’m planning to switch to the iPhone Duo in a week, and I’m curious if anyone has tried Voyager on, say, the Z Fold 8 or another passport-style foldable. Or, if indeed Voyager will have support for the Duo, with the navbar moved to the side instead of the bottom?
Edit: For anyone else curious, as of October 24th it works okay on the Duo. It’s great on the front screen, it’s good in portrait mode on the inner screen, it’s merely okay in landscape mode on the inner screen. Just like most iPhone apps that haven’t been updated for the Duo.
Not sure if this broke in an update, but all posts are full size and won’t change to compact even though it’s selected.
Basically, I'm wondering if Voyager plans to make it easier to interact with comments and media by already displaying the options before clicking.
This must be how the developers of YAML felt...
My last feature request was a bust! I'm back with a new one that I hope doesn't already exist this time lol
The ability to set private tags for communities and/or instances in an easily visible way. Perhaps coloured labels can be set.
For example:
[email protected] may have a green coured tag saying "small community, no politics, consensus: Velma hot"
[email protected] may have a red tag saying "crazy mod. Avoid if possible. Cheeseburgers welcome"
Etc.
In my mind this would help me categorize my short notes and thoughts on each of the quadrillion instances and communities within them.
Just a private note for mental organization.
Thoughts?
i type the name in, it shows up in the list, and I select it- but it never adds to the list.
I was just wondering why the heck I never see authors names on posts in the feed, looks like it was an option that was disabled (by default?).
pretty much title, I’ll be scrolling through my feed in the middle of reading something and it will randomly jump back to the beginning
Edit: leaving this for other silly geese like me who missed the toggle. The answer is in the comments here!
My request is for a toggle to hide all vote counts in comments and on posts or anywhere they appear.
I'd like it if the up vote and down vote buttons were still visible and clickable because voting is still a form of abuse and spam prevention, but I personally find the vote counts themselves distracting and unneeded.
Is an optional toggle for that possible to implement?
Thank you Voyager devs, I really like your app.
As you can see in the screenshot, I typed this and it's being hidden by the keyboard. Version 2.49.1 on Android; Gboard version 18.2.4.969776716-release-arm64-v8a at time of testing.
It appears that since v2.49.1 the Android status bar is no longer visible on my phone.
Android 14 Nokia X20
If anyone else is seeing this, I'll open a bug report on GitHub.
Edit: I've now created an issue on GitHub.