mutual_ayed

I just use this

https://github.com/nylonee/watchlistarr

Late May

You can too

https://wiki.archiveteam.org/index.php/ArchiveTeam_Warrior

Short TSLA.

Puts at 170 will pay out very nicely.

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.

https://medium.com/sessionstack-blog/how-javascript-works-cryptography-how-to-deal-with-man-in-the-middle-mitm-attacks-bf8fc6be546c

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/

https://github.com/muke1908/chat-e2ee