This is NOT a file format that corrupts itself. This is a file reader that corrupts files. There's a big difference. Nothing about the format itself causes or requires corruption. A better tagline would be "decayfmt is a social contract enforced by pinky promise".
Basically what you want is a custom PCIe device that can P2P DMA the DRM-encrypted frame data to GPU DRM-protected memory directly, more corrupted each time.
Can still be replayed, but would likely require special hardware to do so.
Might be visually cooler and a gesture at decayed compute history if the decay pixels land as black and white (1 and 0) instead of color.
RBG noise damage does happen digitally for image damage, while hue protected noise damage is more organic -- a more filmish look. Most people prefer hue protected noise (saturation and lightness variance fine). It's likely this would look older and more decayed given our biased association with film grain.
For this, monochrome noise with a target grey level (e.g. 20% grey) would be visually nice, but the 1s and 0s would be even more old timey computer museum decay.
Comments
This is NOT a file format that corrupts itself. This is a file reader that corrupts files. There's a big difference. Nothing about the format itself causes or requires corruption. A better tagline would be "decayfmt is a social contract enforced by pinky promise".
Dammit! This renders it completely unusable.
True, but only a little bit each time you read it.
Basically what you want is a custom PCIe device that can P2P DMA the DRM-encrypted frame data to GPU DRM-protected memory directly, more corrupted each time.
Can still be replayed, but would likely require special hardware to do so.
Just package it as "decayfs", a FUSE that corrupts stored data each time files of these formats are read.
I came here for this comment.
"A file format that corrupts itself a little every time you open it" simply isn't possible.
It's almost like the author is ragebaiting with this AI generated non-sense.
this is genius territory
decayfmt guy here, people are pressed by a repo that starts its readme with tung tung tung sahur
A good reminder that satire really is an art.
Author of decayfmt here, it is indeed a pinky promise.
Noticing project name is decayfmt not damagefmt.
Might be visually cooler and a gesture at decayed compute history if the decay pixels land as black and white (1 and 0) instead of color.
RBG noise damage does happen digitally for image damage, while hue protected noise damage is more organic -- a more filmish look. Most people prefer hue protected noise (saturation and lightness variance fine). It's likely this would look older and more decayed given our biased association with film grain.
For this, monochrome noise with a target grey level (e.g. 20% grey) would be visually nice, but the 1s and 0s would be even more old timey computer museum decay.