I agree with this take, and recently I actually read this article that criticizes how server centric fedi is as a whole. If it’s hard and expensive for a layperson to self host, but you need to have an account associated with a specific server, then you’re going to end up with a system where you’re under the whims of a instance owner still. Not to mention the whole pick a server step severely hurts our adoption rates.

I like the idea of having an account just being a public and private key pair. Theoretically you could make one client side, use it to sign your messages, and servers could verify the signature and distribute your post without needing to have an explicit account for you. You could send every message to a random instance and it’d still work. You wouldn’t have to worry about links to the “wrong instance” and you wouldn’t have to attach your identity to a instance that might shut down or be bought by a bad person. The server would be essentially irrelevant.

Gotcha. In that case I’ve already set that all up in sonarr/radarr directly, using shared docker volumes.

I never heard of those tools, but I have a jellyfin server. By “support” for jellyfin, does that mean it has like a plugin or something to request media from within jellyfin?

I get the appeal, but between the massive community if plugins, and it being self hostable, I think it still gets most (but not all) of the benefits of open source

This looks cool, but I’m not sure there’s any reason to use it over Foundry if you already have a license.