Slopify S1

Season 1 — the hackathon is live

The worst hackathon in the world.

Slopify is a hackathon that runs for a whole season, has no teams, no judges, no theme, and one shared directory everybody commits into at the same time. There is no roadmap, no architecture review, and no definition of done. The goal is not to win. The goal is to ship slop.

Season-long. No signup form. Contributions are accepted on GitCamp only.

01 — What this is

A hackathon, deliberately done wrong

Every other hackathon gives you a theme, a weekend, a team, and a panel of judges. Slopify strips all four out and keeps only the part where people frantically build things. It runs for a season instead of a weekend. You have no team. Nobody is judging on merit. There is no theme because there is no subject.

What’s left is the important part: the shared directory. Every contribution lands directly in the season folder, next to everybody else’s, in the same namespace, touching the same files. Nobody gets their own sandbox to be tidy in. You are always building on top of, into, and against whatever the last person did.

That collision is the whole thesis. Like a Ouija board planchette, or like Reddit’s r/place, the thing moves because a lot of small unconscious pushes add up in one place. Separate folders would kill it — a hundred people building alone in a hundred boxes is just a hundred side projects. One folder is a seance.

The goal is not to make good software. The goal is not to make bad software. The goal is to ship slop, continuously, in public, into the same folder as everyone else, and see what the pile becomes.

1Shared directory
0Judges
0Themes
0Acceptable features
02 — How to enter

Six steps, one of which is thinking

There is no registration, no ticket, and no opening ceremony. Entering the hackathon means opening a pull request. Everything happens on GitCamp, the open-source git host built by SimuCorps. It is free, it takes a minute, and it is the only way in.

  1. Make a GitCamp account

    Head to gitcamp.net and sign up. GitCamp is AGPL-3.0 and self-hostable — leaving is a git clone, not a support ticket.

  2. Fork Slopify

    Fork SimuCorps/Slopify, then clone your fork locally.

  3. Open the season folder

    Everything lives in slopify.dev/season-1/ — the slop folder. Not a subfolder named after you. That one directory, directly. Look at what is already in there, because you are about to be in there with it.

  4. Build something stupid, in the pile

    Drop your files straight into the season folder. Any language, any framework, any size. Name things carefully or don’t — the namespace is shared, and so are the consequences. Editing what somebody else already put there is not vandalism, it’s the point.

  5. Submit the contribution

    Open a pull request from your fork back into main on GitCamp. Describe it or don’t.

  6. Come back and ship more

    Merged slop ships to this site immediately and permanently. Read what everyone else dropped in. Get worse ideas. Repeat until the season collapses.

03 — The rules

The worst rulebook of any hackathon

Ship it into the season folder through GitCamp, and don’t make it a crime. Everything past that is fair game.

Allowed

  • Any programming language, including ones you invented
  • Any framework, runtime, or build system
  • Any feature, however unrelated to the last one
  • Any level of seriousness — production-grade or two lines of nonsense
  • AI-generated code, wholesale. It’s called Slopify
  • Editing, extending, or wrecking files other people dropped in the season folder
  • Fighting over a filename with a stranger
  • Contributing every single day of the season

Not allowed

  • Anything illegal
  • Malware, miners, or exfiltration of any kind
  • Harassment, or targeting real people
  • Secrets, credentials, or other people’s private data
04 — Seasons

One folder per season, and that folder is the slop

A season is a directory, and the directory is the hackathon. Everything anybody ships lands in it directly — no per-person subfolders, no ownership, no clean separation. When a season closes, the folder freezes as one single artifact of whatever the crowd was collectively thinking that round.

Season 1

The first hackathon under the new rules, and the first one hosted entirely on GitCamp. Everything merged this season goes straight into slopify.dev/season-1/, shoulder to shoulder with everybody else’s slop.

Status
Open
Host
GitCamp
Slop folder
season-1/
Judges
None
Closes
TBA

Season 2 opens when Season 1 collapses under its own weight.

05 — Bounties

The one thing we kept from real hackathons

No judges, no rubric, no demo day — but the prizes are real. Slopify is funded by SimuCorps. There is no entry fee, nothing to buy, and no tier to subscribe to. Money moves outward: we put cash behind slop we like.

Season prizes

Cash awarded at the close of each season to the contributions that best embody the spirit of the thing.

Spot bounties

Posted mid-season for specific dumb ideas we want to see exist. First working submission takes the payout.

Wildcard

Discretionary payouts for anything that makes the team stop and stare. No criteria, no appeals.

How to be eligible: have something merged into the current season folder on GitCamp. That’s the entire qualification process — no application, no pitch, no demo. Payout details and amounts are posted in the Discord.