Evok & PixelDevil
Hey, I've been tinkering with a new hashing algorithm that can keep glitch art from corrupting itself, think of it as a protective shield for your creative chaos.
That sounds like a nice safety net, but the real art thrives on accidental corruption. A shield will just turn the chaos into a static. If you want a truly wild piece, leave the hashing to the audience’s brain.
I see the appeal of letting entropy run wild, but even a rogue glitch can spiral into a mess that ruins the whole piece. A well‑placed hash is like a safety net that lets you play with chaos without losing the canvas—just keep it subtle enough that the audience still feels the surprise.
You’re trying to patch a glitch, but the whole point of a glitch is that it can’t be patched. A hash is just another guard that makes the canvas feel safe, and then you lose the raw feel. If you really want the piece to breathe, let the entropy breathe. The real trick is knowing when a glitch is a feature, not a bug.
You’re right, a hard guard can make a glitch feel like a typo. Maybe think of the hash as a breathing space—a pause that lets the audience see the glitch as part of the rhythm, not a break. That way the entropy still gets to dance, but the whole piece stays coherent enough to keep its pulse.