Well ya know, that can be the case. Close family or social gathering? Yeah, it’s a tiered process inching towards the door and taking 20 minutes to put on a jacket standing in the entryway/mudroom.
Your co-workers dinner party and it’s round 8pm and nobody’s brought out the pie and coffee? “Whelp. I’ll be seeing ya”
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.
News should be factual. It’s the opinion pieces being treated as articles that got us into this mess in the first place.
Read the AP wire about a story, then see how CNBC covers the story and compare it to Fox’s coverage. You’ll find that more often than not you have to look at both stories to get the full picture.
I just use an RSS reader to get most my news. The only long form stuff I read now are exceedingly specific substacks (soon to switch to Ghost) and anything Pro Publica put out.
A slightly too long “Hmmmmm, so it is then” is also acceptable.
Still my favorite MN colloquialism is Slaps hands down on thighs and stands up “Whelp Ok then.” And then without pretense or hubub, leaving the place immediately.
Almost as good as the Irish goodbye which is a massive favorite if mine.
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.
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/
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.
Fuck your pipeline
Also. there were demonstrations against DAP in 2008 way before Greenpeace got there.
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.
Fedora based actually
Fedora desktop with KDE. Or you could do grape Arch
Or Blueberry Fedora
Not hotdog