Absolutely correct. The truth that’s already out there is disgusting enough, leaves a bad taste in my mouth.

https://en.m.wikipedia.org/wiki/Prince_Andrew_%26_the_Epstein_Scandal

https://theconversation.com/prince-andrew-the-monarchy-has-a-long-history-of-dismissing-womens-suffering-165927

https://www.bbc.com/news/uk-58871849

Yes; the royal family does leave a poor taste in one’s mouth, generally.

Jokes on you, I don’t have any lips!

Nobody drives in NYC there’s too much traffic

It’s Project 2025.

I’ve seen more scientists, phd students, post grads, and STEM college students at protests than at any other time in my 30 years of protest. I’ve been involved in organizing countless protests online and now spend hours every week cultivating or building networks for dissidents and community organizers.

I don’t know which scientists you’re talking to in the meatspace, but you might want to find different ones. Before they’re all in the EU or Canada.

Which strawman are you yelling at in particular?

All US stocks half off

I just use this

https://github.com/nylonee/watchlistarr

Late May

Short TSLA.

Puts at 170 will pay out very nicely.

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

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

https://discuss.grapheneos.org/t/general

https://github.com/GrapheneOS/os-issue-tracker/issues

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.