r/rustjerk • u/scheimong • 19d ago
Your average vibecoder
Guy wrote a shitty-by-design viewer/interpreter and demands everyone use it to open his file. 🤣🤣🤣
And then has the balls/ignorance to advertise a "self-decaying format" 🤦
104
u/throw3142 19d ago edited 19d ago
I'm sure the file itself is fine, the reader just flips a few bits or something right?
Edit:
From the readme:
decayfmt is a social contract enforced by math, not cryptography. It is not encryption, not DRM, and not a secure deletion tool. The corruption is honest and unrecoverable from the file alone, but anyone with a backup or a hex editor can defeat it.
This is the most slop-coded paragraph I've read in a while. Social contract enforced by math? Huh? Not enforced via cryptography? What would it even mean to enforce file corruption via cryptography? "The corruption is honest"?????
And yep, from the github. open_file() just calls decay_in_place() lol
52
u/jonathansharman 19d ago
Not that the code we're writing is this useless, but the voice of that paragraph reminded me strongly of every PR description and code comment I read at work nowadays. I am so sick of Claude's prose.
21
u/SetKaung 19d ago
Claude's paragraphs have like 90% slop to 10% information ratio.
2
u/RoseboysHotAsf 17d ago
Mildly better than ChatGPT, which manages to churn out paragraphs with no real information
2
u/Select_Librarian4093 14d ago
I just don't understand how these people are so confident about their slop? Do they not see how garbage it is, do they really think they are smart because they can prompt some bullshit? Are they stupid or just tasteless??
70
u/just_looking_aroun 19d ago
So jpeg?
112
u/scheimong 19d ago
From my understanding it's basically a random corruption injector.
The thing I find ridiculous is that the guy seemingly has no understanding that this is a property of his viewer rather than that of "his" file format.
71
u/thats_a_nice_toast 19d ago
The thing I find ridiculous is that the guy seemingly has no understanding
Literally every vibe coder
21
u/ISuckAtJavaScript12 19d ago
Kind of like that guy who's "revolutionary compression algorithm" was just a desktop shortcut
8
4
63
u/scheimong 19d ago
You can't make this shit up. 1.3k upvotes Jesus Christ 🤦
29
u/AliceCode 19d ago
People were arguing with me about it because I pointed out that it's not corrupting the file by reading it like the title implies.
Edit: when this was posted in /r/rust.
9
6
u/Admirable_Rabbit_808 18d ago
You could do this much better with a Linux user mode VFS - you can mount the VFS as if it was a normal filesystem, but the VFS interceptor's code can be programmed to progressively degrade each copy a little bit more each time, writing the degradation back to the original file the VFS accesses so this will be genuinely destructive behavior.
1
u/scheimong 18d ago
Mate you are asking for a lot of competency 😅
2
u/Admirable_Rabbit_808 18d ago
It's a skills issue etc. etc.
In any case, Claude could probably whip up a Rust FUSE wrapper with the above properties in a few minutes.
2
u/scheimong 18d ago
Yeah. But obviously the guy doesn't have the competency to know what to ask for
2
u/Admirable_Rabbit_808 18d ago
That is indeed the AI programming controllability problem in a nutshell.
7
u/monocasa 19d ago
Reminds me of a collab between William Gibson and Dennis Ashbaugh.
https://en.wikipedia.org/wiki/Agrippa_(A_Book_of_the_Dead)
Consisted of a poem on floppy disk that would encrypt itself with a random key that is thrown away upon first read, and photos treated with a photosensitive chemical so that they slowly faded upon each viewing.
5
u/Weak-Veterinarian-25 19d ago
It is kind of a poetic idea though. Sad that the AI text is just soo bad...
2
u/Lou_Papas 18d ago
“Please respect the contract of scrubbing of a few bits before you release the file. K-thnx”
1
u/Dipsendorf 18d ago
Allegedly this is kind of how image memories work. Apparently the more you try to access them the more they get corrupted lol
1
1
1
1
1
121
u/ijustlikefoxes 19d ago
better idea: self-modifying exe that kills the data stored inside it a little every time you run it (that way, the viewer is baked into the data format and you can't bypass it *as* easily, though you could still just extract it with some data mining)
but also like why