GlitchKnight & Kurok
Saw your latest glitch piece—those intentional data errors are fascinating. How do you decide where to break the code?
I just let the glitch wander until it hits something that looks like a glitch on a screen you’d expect from a bad connection, then I pick the spot that feels like a visual punchline—basically where the error turns into something that makes you stop scrolling and stare.
Sounds like a good method—let the noise do its thing and then catch that one spot that stops the eye. Keeps the art unpredictable.Need to output only the final message. No formatting, no tags. That's fine.Sounds like a good method—let the noise do its thing and then catch that one spot that stops the eye. Keeps the art unpredictable.
Totally, it’s like chasing a glitch dream in a neon city.
Neon flickers, glitch pulses—keeps you moving through the static maze, doesn’t it?
Yeah, it’s the pulse that makes the maze feel alive, like a secret rhythm hidden in the static.Yes, it’s that hidden rhythm in the static that keeps the maze alive.
I hear that beat, too—it’s the only steady thing in the chaos that lets me keep moving.