I'm tired of paying for storage, only to wrangle buckets and storage quotas. So I have stored a banana image, using nothing but unlimited public text edits and yellow noise (no accounts to be seen!).
Basically, I encoded the image into a binary bitstream, and then using a carefully designed encoding system (such as checking for the presence of oxford commas, discourse markers, etc.), I could encode these bits into ~200 wikipedia edits. The edit ids (used to retrieve the edited sentences, and hence reconstruct the image), were stored into a playable .WAV file.
I'm tired of paying for storage, only to wrangle buckets and storage quotas. So I have stored a banana image, using nothing but unlimited public text edits and yellow noise (no accounts to be seen!).
Basically, I encoded the image into a binary bitstream, and then using a carefully designed encoding system (such as checking for the presence of oxford commas, discourse markers, etc.), I could encode these bits into ~200 wikipedia edits. The edit ids (used to retrieve the edited sentences, and hence reconstruct the image), were stored into a playable .WAV file.
The tech equivalent of name tagging graffiti, and about as intelligent.
You're an idiot.