I just use this
- 0 Posts
- 33 Comments
Joined 2 days ago
Cake day: March 19th, 2025
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
Yes it will always play catchup. However a combined 8 years of targeted Apple Silicon development expertise has left the project in the past month. A big loss to the team is also all the organizational momentum from that as well. Hopefully another team picks up the project if this team cannot finish it.
I’ve contributed to quite a few opensource projects in the past. I know how to work around binary blobs and what troubleshooting, reverse engineering it takes.
Yes, I know. Asahi has been a couple years behind apple architecture. It took almost two full years before M1 was supported.
It’ll be be even longer if the top devs keep leaving the project.
SpaceX and Starlink next. I’m tired of funding his bullshit with my tax dollars.
Give a month will yah? I got puts at 170
I’m lucky to have only had one system nuked by a faulty power supply that shut down during a kernel update.
I usually just reinstalled back then. But I didn’t get into it till the late nineties. Back when Ian was still on the list serves.
Unless you mean nuking the OS or borking the bootloader. Then yeah, countless.
Right?! This is why I love the Fediverse and FOSS.
Have a good night/day
Hope you find new fun ideas as well!
I think that’s by design and the nature of the setup. Anyone with the URL can communicate.
If your other comms method is compromised this doesn’t have much use. Which is a different problem all together. I think this would work great as something like a deadrop so two completely faceless people can communicate. I like it a lot.
I don’t know yet. It’s more a thought experiment than anything else.
https://github.com/muke1908/chat-e2ee
Looks like the URL is part of the seed and salt which is cool.
Proving who you are is done in another stream. Like MFA.
You do a one time pad, generate the URL with that. Communicate what’s needed, then the URL dies.
I’m still noodling with it.
Just because I and my family benefit now, doesn’t mean it’ll stay that way. Also again, I don’t want to support or platform an app that charges others, who are not me, to share their own collection.
If they want to charge for the Plex TV or Plex Movies they host, and leave the app free of cost for a person’s own personal collection to be shared. That’s fine.
I have no confidence that’ll happen though.
Hell is other people especially in FOSS.
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/
Cool, now they can correct the “mistake” made regarding Army Maj. Gen. Charles C. Rogers …
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
Fragility is by design as it’s ephemeral comms. Swapping the js decryption doesn’t make sense as wouldn’t the client just fail or refuse the message stream as the decrypt/encrypt changed? It’s an interesting problem. Thanks for giving me something to noodle on.
Most previous “recalls” were software updates. This is a mechanical connection of the rear quarter panel. It’s a big sheet of stainless that can become a sail on the highway and rip itself off of the truck. I personally think a 4’x3’ panel of 1/8th inch stainless panel flying at my car while I’m driving 65mph to be a pretty big deal.
So yes this is a big deal, highlights all the bullshit cost cutting measures that were placed on the project and most of all shows that Musk actively makes any tech he touches worse.