Memespeech: Censor-proof end-to-end encryption
obsessivefacts.com
obsessivefacts.com
It basically does what memespeech is doing, except much better. Both parties would need to agree on a cover text (let's say, a chapter from the NIV Bible). It then generates some text via GPT-2 trained on this cover text, with your hidden message encoded in it.
You'd then send this generated text to the recipient (which actually looks like a normal message written in the style of your cover text). They'd enter the same chapter of the NIV Bible along with your generated text, which then lets it recover your hidden message.
Basically, memespeech looks like you're hiding something, both to the human eye and to machine learning models. NeuralSteganography solves both of these issues, as it looks like regular human-readable texts to both humans _and_ ML models (Harvard's paper goes into more detail on this https://arxiv.org/abs/1909.01496 ).
There's also the famous illegal number from AACS[2].
[1]: https://www.fcc.gov/consumers/guides/obscene-indecent-and-pr...
[2]: https://en.wikipedia.org/wiki/AACS_encryption_key_controvers...
There are more robust solutions like GPG, but Memespeech was designed to be easy for people who already have established trust with the party they're communicating with (and could exchange a decryption password off-channel).
This might be entertaining, but it definately doesn't fix the problem it tries to solve. Any jury in the land would still convict you if this was used to pass messages which would otherwise be illegal. If this is serious it is as stupid as saying "let's agree wearing Yellow socks means 'kill that guy', they can't arrest me for the colour of my socks!"
I think the courts have generally held that you can't simply throw speech onto some otherwise prohibited activity to gain First Amendment protections. For instance, see the case about the man who tweeted a GIF at Kurt Eichenwald with the intention of provoking a seizure - the fact that the GIF also contained words (... which were "you deserve a seizure for your posts") seems unlikely to say that the act of sending the GIF itself was protected speech.
Bad: Courts might begin issuing surveillance warrants (or worse) to TLAs based on the most innocuous personal communications, because "we're pretty sure that happy birthday e-card contains an encrypted message".
In either case, I completely agree if the message is deciphered by authorities, they've got you dead to rights, whether it's done by PGP, GPT bible verses, or yellow socks on Tuesday.
EDIT: I was commenting primarily on the GPT technique, but now having read the Memespeech page, totally agreed that it wouldn't even slightly stand up to scrutiny in court, as one needs no prior knowledge to decode the message and demonstrate that there is no other legitimate explanation for the communication.
Even if this software were banned, a couple of points remain: - It's unprovable that any block of Memespeech text has something encrypted in it unless you know the password - It's easy for a developer to write their own Memespeech implementation based on the documented specification.
Not saying that anyone would violate a hypothetical (and probably unconstitutional) law, but it would be hard to enforce.
It's pretty easy (relatively speaking) to run your own transport that doesn't go through a third party, at which point you can just use OTR or whatever. Then you're immune from banned-in-the-sense-of-blocked, and you can make your own risk decisions about banned-in-the-sense-of-illegal. (Also, depending on the details of the law, this might be perfectly legal too, e.g., "big tech must give us backdoors" doesn't need to imply "everyone who runs encryption must give us backdoors.")
It does seem like Memespeech has an advantage if you're using a third-party platform as a channel and you don't want to be blocked, i.e., you want to exchange encrypted-and-not-backdoored messages over Facebook Messenger because you can no longer trust its own encryption. I agree that this seems less likely to be blocked than literally sending base64 over the channel. But it still can get blocked - Facebook is under no obligation to transport all "Free Speech" (whatever that means) from user to user. If Facebook says, on our platform we disallow text with >20% uppercase letters, they can do that legally and constitutionally. The government could force them to do it, but they could also do it on their own (e.g. a spam detector might do it, honestly).
So you basically end up in a steganography arms race: you want to send messages that look to Facebook like actual genuine messages so they don't block you, but they contain coded information that is end-to-end encrypted using modern cryptography. I suppose it depends on a number of external factors as to whether that's easier than setting up your own transport.
For instance, if your goal is just successfully sending messages and you don't care about legality, another easy (relatively speaking) thing is to run Noise Protocol over your favorite shortwave digital mode. Then you don't have to worry about being blocked at all.
The thought experiment is: Banning text message that are clearly readable (with or without message hidden inside, every message could hide something, even not on purpose, so everyone is 'guilty' when chatting) means you're banning freespeech (all chat message).
I don't think the method was meant to be taken too seriously, it seems to be some kind of statement.
- Docs and detailed format specification: https://gitlab.com/obsessivefacts/memespeech#memespeech-java...
It encodes your message into the bill of rights.