Thanks! I’ll definitely be addressing this soon.

They’ll probably fix it in a future beta without my action, it’s happened before in the first beta release. ¯\_(ツ)_/¯

After v1 I’ll look into it but the API is pretty immature, it doesn’t even support CORS :/

edit: After Lemmy v1

I’ll look into it when I get back from vacation

I could see that argument, but I also wanted to pick the best instance for most people, not necessarily an instance that works in every country with every shitty law. We’re all volunteers here.

And I might change in the future, or create a way for the app to chose a fallback default instance for a better user experience.

Zip is a cool instance :)

Thanks for investigating. I’ll keep my eye out but I have t seen it. Can you replicate on another device?

If you email me at hello@vger.app with the file I can take a look.

Are you on iOS or android? It should automatically strip the getvoyager part on paste into comment

Have you tried resetting hidden posts?

Yes, that’s something I’ve thought about doing

The main reason is SSR so sharing in messages provider the preview image and whatnot. Also more control over the onboarding, and avoiding confusing the PWA with the native app. That’s a nice alternative though!

Universal Links that are verified, like go.getvoyager.app, will automatically open in the app. The Lemmy links are there, but are “unverified” and won’t open in the app unless the user configures them to. Also, adding unverified domains isn’t possible in iOS. So this is a much more universal, zero-config option.

Mastodon redirect is great and works with voyager, but is more of a power user thing. Go.getvoyager.app works out of the box :)

This service requires knowing that the other party also has and exclusively uses Voyager.

Well, kinda. It is one click to open the Lemmy link directly. I’ve also thought about adding config options to the service to auto redirect to the Lemmy instance, to make it unobtrusive for other app users. The code is open source so I’m happy to hear suggestions to make it work better!

Cool :)

Are you the bot author? If so have you considered using Lemmys alt text field directly? This would display the text with the image is some clients like voyager. It would also federate to Mastodon (post body doesn’t federate). You could also keep the text in the post body and do it both places :)

Maybe considered in https://www.w3.org/2025/03/26-mse-text-tracks-minutes.html?

I will probably investigate after Lemmy v1 is released, no promises though. Support for two platforms would add a significant amount of development overhead.

For losing your position, I recommend enabling and using the hide posts button. You can always temporarily unhide and/or reset by long pressing the hide button. 🙂

I’d say about 50% of reloads is an iOS bug where indexeddb crashes. Apple is aware of that one but they haven’t fixed it yet… so should get a bit better eventually.

Looks like it loads flakey. Issue with the image host maybe? Here is screenshot of Lemmy-ui via Lemmy.zip also not working.

That would be super cool! I think it could be accommodated in Lemmy API. Have you tried making a feature request there?