Hell is other people especially in FOSS.
mutual_ayed
I still don't see how
swap to a modified JS that exfiltrates the e2ee key
or
add additional keys
Wouldn't significantly change the recieved hash and break the stream thus ending comms. Also unless you're hosting and building it yourself you have to trust the recipient and the cloud host.
I agree if an attacker owns the server comms can be compromised. I thought that was the benefit of the ephemeral nature. It's for quick relay of information. Best practices would probably include another cypher within the messages themselves like a one time pad or some such.
https://www.itstactical.com/intellicom/tradecraft/uncrackable-diy-pencil-and-paper-encryption/
What's going on over there?
https://www.theregister.com/2025/02/13/ashai_linux_head_quits/
https://marcan.st/2025/02/resigning-as-asahi-linux-project-lead/
I just wanna run fedora on an M4 already
Edit: I hope she feels safe and is able to put whatever it was behind her. She's a brilliant engineer.
https://asahilinux.org/2022/12/gpu-drivers-now-in-asahi-linux/
Yes, that's great for me and mine, but not for others. I don't like to support or platform/promote applications that require a subscription for any access at all.
The problem is Plex aren't Netflix in my usecase. I'm sharing my library with my friends.
Now if they'd like to charge for the content they host. Great more power to 'em, but I feel icky with a payment or subscription model that charges to deliver my collection to my friends and family.
So, like I said. I'll likely start migrating to jellyfin and start the conversation with people in how to get the jellyfin app on whatever device they have.
It has. Strangely enough they posted a code of conduct after that feedback and started weilding the ban hammer. However I cannot speak to outside forums like XDA or Reddit or even comms here. I tend to stick to their forums or github
Can you expand more on the key management? I thought https://chat-e2ee-2.azurewebsites.net/ passes a PSK Through the header and sets that as a cookie in the browser to sign further comms. I could be mistaken of course.
A lot of flatpaks early on wouldn't survive a major point release upgrade or worst case would hold on to dependencies and the user would end up with an unbootable mess after an upgrade.
I haven't seen that recently though.
However I regularly run appimages on my fedora silverblue system so take what I say with a grain of salt.
The more people that short the stock....the better for everyone.