decayfmt guy here, I was not going to make this without AI eitherway.

decayfmt creator here, its pure novelty.

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.

I don't think that should be an issue either way, especially if it is not production code and just a hobby thing.

Are you saying something being reliable is not a big deal? I'm sort of confused