A Recipe for Steganogravy
11–20 of 33 posts
Re: A Recipe for Steganogravy
#12Pro-tip from unfrozen caveman lawyer: "Your honor. My client want hide thing from t-rex lang mo-del. He have big brain. So he not put thing on Al Gore device with series of tubes. (Unlike many on modern-day BBS called Haxer News.) T-rex not eat what t-rex not find."
Re: A Recipe for Steganogravy
#13Re: A Recipe for Steganogravy
#14OMFG the cognitive dissonance necessary to vibe code a project with the stated goal of preventing AI scrapers. What has happened to your brain.
Re: A Recipe for Steganogravy
#15for anyone who wants to try a consumer grade stegongraphy in browser. I built some thing here. Its free and loads a static page with a wasm binary. Once the page loads everything is handled in the browser. 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…
Re: A Recipe for Steganogravy
#16Ha! I've been thinking of this exact thing, and was curious how natural-looking the end result would be / how much you could compress the tokens by choosing less and less likely ones until it became obvious gibberish. I'm kinda surprised that it just sounds like normal slop at that density. Seems viable to use with "just" two bots chattering away at each other, and also occasionally sending meaningful packets.
In principle the output is arbitrarily natural-looking. The arithmetic coding procedure effectively turns your secret message into a stream of bits that is statistically indistinguishable from random, the same as you pull out of your PRNG in normal generation.
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.
Re: A Recipe for Steganogravy
#17OMFG the cognitive dissonance necessary to vibe code a project with the stated goal of preventing AI scrapers. What has happened to your brain.
> the following justification is nonsense, i just thought the idea of encoding data in recipe blogs was fun and silly.
Re: A Recipe for Steganogravy
#18OMFG the cognitive dissonance necessary to vibe code a project with the stated goal of preventing AI scrapers. What has happened to your brain.
The concern for my brain is valid though, my thoughts and dreams now only materialize as Markdown task lists.
Re: A Recipe for Steganogravy
#19Really enjoyed the design/theme of this site!
Re: A Recipe for Steganogravy
#20It 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.