This was so god damn good!

I’m no cryptography expert but I don’t see how they could implement this with true anonymity or without it being spoofed in other browsers. There is currently no way to know with absolute certainty what browser/client web traffic is actually coming from and game anti-cheat devs will probably tell you it’s a nightmare of a problem.

The way I see this working is making it a Mozilla account thing and not a Firefox thing through some sort of stateless cross-origin cookie the sites agree to support. But then, you’re giving up at least some privacy because even if the sites you visit don’t know who you are, you’ll still have to trust that Mozilla is logging anonymized visit counts and that some CEO 5 years from now isn’t going to change that for a quick buck.

Maybe I’m just out of my depth here and someone’s gonna correct me (please do if I’m wrong).

Fair enough, just saw the “if you’re not an IT worker” comment haha

Ah, my use case right now is almost exclusively streaming stuff from my laptop to a phone with HEVC support over a local network so I can just turn transcoding off and be okay.

I did however have issues with my lack of transcoding (I turned it off myself, not Jellyfin’s fault. Pitchforks down, people) on a tablet without hardware HEVC support though so I may have to experiment with it soon.

FWIW I had to go in and turn the feature off but there’s also a good chance it was using CPU instead of GPU

Oh come on, it’s better to be helpful if you can rather than just saying “for you” and adding nothing else to the conversation.

Seriously I’m sure they’d love to try it again if the issue is resolved. I know I wouldn’t pick Plex over Jellyfin unless I had no choice.

When you say “hardware encoding”, are you talking about using your GPU for stuff like transcoding when streaming to devices?

I ask because I actively disable all transcoding because I run jellyfin off my laptop and don’t wanna overwork it so to speak. I just assumed it was using the GPU.