Why aren't you a big fan (serious question)?
AnActOfCreation
Thank you, that's very interesting!
Can you expound on this?
Nice, that's what I would expect! Lemmy has an endpoint that makes it easy to resolve links across instances. The OP implied Voyager didn't do that.
https://join-lemmy.org/lemmy-js-client-docs/v0.19/interfaces/ResolveObject.html
It would be cool if something like this could also be incorporated into the apps
What does Voyager do if you click on a link to another instance? Open in the browser?
Thunder tries to resolve the link to your local instance and opens it directly in the app.
get a VPS, run Tailscale and NPM on it and switch to Jellyfin
Keep in mind that VPSs will charge for bandwidth, which adds up quickly when you're streaming.
One suggestion I haven't seen mentioned is contacting your ISP. Sometimes you can get a dedicated IP, although you might have to pay for it.
Alternatively you might just break down and pay for Plex Pass. I know that goes against the Lemmy philosophy to the very core, but for all its issues, Plex is still way ahead of Jellyfin in terms of features, UI/UX, etc. Jellyfin will get there, and I'm ready to switch the day that Plex becomes unusable, but that hasn't happened yet.
I'm sorry if I'm out of line with my comment here, but this whole post gave me a good laugh. I think it's akin to asking GIMP developers, "why don't you just make this like Photoshop" or asking Linux developers, "why don't you just make this like Windows".
I'm sure the Thunder devs would love to bring over a lot of the most popular features from Sync, but it's not that simple. Looking at the repo, there are already very frequent commits and releases, but there is also quite a backlog of feature and bug requests. You can't just make one app like another app, nor can you imply that Thunder doesn't have feature parity with Sync because the devs don't want it to.
Add on to that the fact that Sync is a paid app meaning that the developer can justify spending more time on it than an open-source app maintained in the spare time of the devs.
Anyway, that's just my two cents. In short, "it's not that simple". :-)
Thunder too! Instance/community/user blocks are a Lemmy feature, but keyword blocks are just a client side thing for now. Thunder blocks based on post titles, contents, and links.
This extension does a decent job.
https://addons.mozilla.org/en-US/firefox/addon/pwas-for-firefox/
But yeah it would be nice for Firefox to support PWAs natively.
The mods are going crazy in this thread. 🤣 shouldn't expect any different on this instance.
Thank you for explaining that, I always appreciate other insights.
I think there's a difference between saying "you do you", "you're gonna have to do it without me" and saying you actively dislike it. Be prepared for that to be an unpopular opinion. :)