Yeah, it's been pretty useful.

This is also why I love open source. In corporate, it would be all "patent that so no one can do anything remotely similar" and with FOSS, I'm like "here is a cool thing you might like; please take".

Also, I may have a "Part II" of this post for the remote instance browsing feature. Every time I've shown that to someone, they look at me like it's witchcraft. Would love to see that more widely adopted as well.

Definitely for the PWA and f-droid builds, but idk how happy Google and Apple would be to have an app doing this in their stores. IANAL

Can you also add a ticket for them to support spoilers?

I use Jerboa myself (was on RiF before), though I've also heard good things about Voyager.

The Boost for Lemmy app is pretty good.

I barely know what lemmy is, something something fediverse. I use the sync app, moved over from sync for Reddit.

https://www.lemmyapps.com/

Can filter by platform and feature :)

My favorites are sync and thunder, but I recommend thunder since it's FOSS, i'm just waiting for hold to peek.

https://lemmy.ca/post/26097116?scrollToComments=true

There are 3 apps that pass the "Does this actually display posts correctly?" test:

• Jerboa
• Alexandrite
• Voyager

Everything else should be considered in a testing phase. Don't pay for an app that can't do spoilers correctly.

Edit: Don't pay for an app that doesn't format text correctly in general, but not doing spoilers correctly is probably the most jarring.

Artic On iOS has been really enjoyable for me. Voyager is a close second. My biggest pet peeve with voyager is not hiding the bars on scroll. Otherwise I would use it.

Voyager for iOS. Not sure about the robot os.

I just installed the default app that it prompted me with. I wonder if other apps can have meaningful more features?

I'm more proposing the general idea to be adopted by other apps; just using my implementation as an example.

would it be possible to let the user add/remove options?

Add? Definitely (and fairly easily). Remove? Not so much (at least in my implementation). Those are the only 3 I know of right now that work reliably. If there are ever more than 3, I would probably move to a dynamic method where you'd just enable certain ones from a list (kind of like Searx-NG if you're familiar with that). A user adding a custom one would work like adding a search provider to a browser (e.g. https://archiver.example.com/?url=%s)

In practice, I tend to need all 3 depending on the source URL in the post. Some don't have a copy of the target or don't render certain sources as well as others, so having a few to choose from is often needed. Allowing user-custom ones is a great idea though.

If you add a link in the menu to some fediverse post, people can suggest changes to the defaults, or exchange their personalizations

I sort-of do that already with suggestions for the built-in Invidious/Piped instances list, but ask that they be submitted via Github or the Tesseract Lemmy community (users can define their own Inv/Piped instances as of a few versions ago). Dunno if I'd want the link to that in the selector menu, but could easily link it from the settings panel where you'd hypothetically edit the archive sources.

Thanks for the feedback; I'll probably work on adding support to at least add custom archive services in one of the next releases (and probably eventually work toward a fully customizable version).

Love it!

Possibly, depending on the app and developer.