quixit

reviving the format

posted by grassnose on April 15, 2026 · 2 mins read

new coordinates

moved from atlanta to victoria, bc. different pace, different light. the kind of change that rearranges how you spend your time and what you reach for.

setting up

last session before the move / may 2025:

new room now. haven't "finished" many songs in the last couple years but the process has grown / new workflows, better routing, sharper ears for what to keep and what to let go. sometimes the work around the work is the work.

once the gear was talking again, it was hard not to think about what else could come back.

reviving the format

years ago there was a community called em411 that ran something called mixit / structured cycles where participants would upload samples then remix those samples into full tracks. everyone walked away with a curated pack. it was simple and it worked.

the format stuck with me. the constraints, the feedback loop, the way shared material pushed you somewhere you wouldn't go alone. when it went away nothing really replaced it.

first attempt was about a year ago / filebrowser instance and a whole bunch of cobbled together bash. it worked well enough to run a cycle but it wasn't something that could hold up on its own.

building it back

so now i've been building quixit / a real attempt to bring that cycle back. sample phase, song phase, pack delivery. the bones are the same. the tech is different.

it's been a grind. cycles of a different kind / writing migrations, wiring up upload validation, getting auth right, testing end-to-end. the kind of work where you don't hear anything for weeks and then suddenly the thing does what it's supposed to.

not done yet; the core loop is there / accounts, cycles, samples up and paginated. enough to see the shape of what it's becoming.

it was simple and it worked. trying to make it that again.

the conversation so far: