I’m holding off on Fluxer until they decide how they’re going to implement federation, since the designs they’ve communicated publicly so far have all seemed like they prioritize siloing and putting excessive load on self-hosted nodes.
Their first proposed solution would’ve required each self-hosted server to be able to handle every user on every other server in the network - a proposal which they’ve since scrubbed from their page.
The latest proposal I can find at least speaks about aggregating connections through the users server, so it’s not as insane (Only requiring each self-hosted server to be able to handle requests from every other server on the network). But it still forbids intelligent caching, and instead seems to consider recommending the use of cloudflare to reduce the load from their design to be a good solution.

I made an NFC/QR code card for my wifi details at home, and that also includes the details written in clear text on the card, since some devices simply don’t do QR (or NFC in my case).

It doesn’t really solve my use-case, since we do a combination of direct stream when possible, as well as local sync/cache but only for transcoding purposes. As well as local users only, with the federated sharing taking care of permissions, so that we don’t transfer user information between eachother.

Jellyswarrm is certainly a lot closer than other solutions people have suggested though.

The lack of library sharing is what’s keeping me on Plex.

The ability to watch media across servers, and even transparently pull it for local transcode when necessary is just an amazing feature.