The people who know least what freedom is, because they’ve been convinced freedom to be an ignorant asshole is the same thing as freedom from an oppressive upper class.

It’s not End to End and The guy in the Middle. The message is encrypted from one end to the other. The detail about who has a copy of the key doesn’t spoil that fact, and I guarantee you Meta doesn’t care about using E2EE as a marketing term even if it misrepresents their actual product by matter of status quo. What matters is what they can theoretically argue in a court room.

A proper solution would be to have an open standard that specially calls out these details, along with certifications issued by trusted third parties.

Yeah. E2EE isn’t a single open standard. It’s a general security concept / practice. There’s no way to argue that they don’t really have E2EE if in fact they do, but they keep a copy of the encryption key for themselves. Also, the workers client app can simply have the “decrypt step” done transparently. Or, a decrypted copy of the messages could be stored in a cache that the client app uses… who knows? E2EE being present or not isn’t really the main story here. It’s Meta’s obvious deceitful-ness by leveraging the implicit beliefs about E2EE held by us common folk.