Now, to give Claude the steganogravy skill...
It lives here: https://stegg.alifeinbinary.com
It's as much of an art project as it is a programming project. The images that it generates are visual representations of binary code translated from the text you enter. If you enable encryption it converts it to a hash. You can download the image, send to someone along with the password and they'll be able to decrypt it by uploading it to the app. Or you can post it to the time line and send them the link. All messages are truly private. No raw text text is sent to the server.
It's not vibe coded, I made it with typescript React. The app has a link to the github repo if you want to look under the hood.
Just earlier this week I've released https://github.com/kirushik/paternoster (and even won Berlin Hack and Tell with it) — and it totally came from the idea "in that state-enforced Max messenger there so much surveillance you can only praise the authorities and pray in there. What if there was a way to hide messages into the text of Church Slavonic prayers?"
I've even added TTS (where supported) to it, just for the giggles of getting the "TRUMP" dictionary thorough it.
It's still a pretty solid X25519+AES-GCM encrypted messaging design under the hood, and I'm happy with it — but it still a bit of an afterthough tbh...
You provide a carrier file (currently .mp4, .pdf, .jpeg or .png ) and impregnate it with an entire encrypted file system with a full viewer and gallery mode. Also supports streaming, so you can actually encrypt a a full blueray movie and run range requests.
Regarding being detected, like anything else in security it is always a cat and mouse game.
The concern for my brain is valid though, my thoughts and dreams now only materialize as Markdown task lists.
> the following justification is nonsense, i just thought the idea of encoding data in recipe blogs was fun and silly.
presumably TDS based on the secret message
I sort of resemble this remark, but to be fair, I'm only mildly offended by people who claim they're scandalously offended on behalf of others who... themselves aren't particularly bothered at all.
Damn. Should have written this up and posted it two days ago; it would have made a great April Fools gag.
You can avoid it by using a bijective arithmetic encoder, which by definition never encounters an "unexpected end of stream error", and any bit string decodes to a different message. That's the cool way.
The boring practical way is to just encrypt your bits.
