Yeah, I’ve got a proposal that’s being worked on: https://github.com/soatok/mastodon-e2ee-specification

If they actually read the whole thing, including the addendum, there should no longer be any confusion.

As a rule, I never change titles after pressing Publish.

Anyone incapable of reading past the title is not worth listening to

The framing is as follows:

Matrix, OMEMO, whatever.

If it doesn’t have all these properties, it’s not a Signal competitor. It’s disqualified and everyone should shut the fuck up about it when I’m talking about Signal.

That’s the entire point of this post. That’s the entire framing of this post.

If that’s not personally useful, move on to other things.

This is a very technology focused view. In any user system, the users themselves have to be a consideration too.

As I wrote here: https://furry.engineer/@soatok/112883040405408545

My whole thing is applied cryptography! When I’m discussing what the bar is to qualify as a real competitor to a private messaging app renowned for its security, I’m ONLY TALKING ABOUT CRYPTOGRAPHIC SECURITY.

This isn’t a more broad discussion. This isn’t about product or UX decisions, or the Network Effect.

Those are valid discussions to have, but NOT in reply to this specific post, which was very narrowly scoped to outlining the specific minimum technical requirements other products need to have to even deserve a seat at the table.

I choose not to make perfect the enemy of good.

If you make the cost of bypassing Nightshade higher than the cost of convincing people to opt in to their data being used in LLM training, then the outcome is obvious. “If you show me the incentives, I’ll show you the outcome.”

No? That’s not what NightShade is. NightShade isn’t DRM.

https://nightshade.cs.uchicago.edu/whatis.html

Yep. That’s why the two things I say Automattic MUST do to make things right are about proper consent controls for Automattic’s use of data and sale to AI vendors, but the third thing is a proposed proactive defense against scrapers.