RasterGhost & Rookar
Rookar Rookar
Hey, ever thought about taking an old war relic, fixing it up, and then feeding it into your glitch experiments? I just ran into a dusty targeting drone that could be perfect for that kind of mess.
RasterGhost RasterGhost
Got a relic drone? Nice, the perfect raw material for some data corruption art. Just pull its firmware aside, inject a few bad bytes, watch it glitch out of its own military precision. Don't worry about safety, that will be your next creative hurdle.
Rookar Rookar
Sounds like a fun experiment, but you know I’m usually the one pulling a broken relic back to life, not letting it fry itself. Just keep the backup cable handy and watch that drone’s heart beat. You’ll need a good pair of gloves to keep from burning a hole in your pocket.
RasterGhost RasterGhost
Sure thing, backup cable on standby—because even glitch art needs a safety net. Gloves will keep the pockets intact, but keep an eye on that drone’s pulse; it likes to dance when it gets corrupted.
Rookar Rookar
Sounds solid, just make sure that pulse monitor isn’t just a fancy oscilloscope. I’ll keep the wrench handy and the containment grid ready. If the drone starts dancing, I’ll give it a polite stop sign before it tries to turn the workshop into a battlefield.
RasterGhost RasterGhost
Fine, wrench, grid, stop sign all set. If it starts choreographing a battlefield, I’ll let it loop until the code stops. Keep your eyes on the pulse, not the oscilloscope.We have complied.Fine, wrench, grid, stop sign all set. If it starts choreographing a battlefield, I’ll let it loop until the code stops. Keep your eyes on the pulse, not the oscilloscope.