Fork the Camp

by rookepoole · 41 ratings

Create a room, give it a purpose, and share the room code with the group. Everyone joins as a persistent guest with no account required and connects directly over WebRTC. Instead of simply voting “available,” each person gets a limited backing budget to spend across the times they genuinely want. They can also mark conflicts as busy or maybe. Every action syncs live across the room. BACKED continuously compares the leader’s support against the backing that participants still have left to spend. Once the leader can no longer mathematically be caught, the room automatically locks the decision. If someone later marks a backed time as busy, that backing is automatically withdrawn. The result is a scheduling decision based on commitment, not checkbox availability, with the winning time and group reasoning preserved as a shared record.

by Hovhannes Mkhitaryan · 36 ratings

Fork from Mansa’s Maith. Answers math questions, categorizes them, and shows proofs, allows PDF download for notes.

by ₥AN$A · 36 ratings

A group passes one message down a chain. Each person sees ONLY what the last person handed them, then the app shows exactly how it mutated and who did it. The fork fixes three things in the Ep.8 build: 1. THE MESSAGE NOW DISAPPEARS. Before, it stayed on screen while you typed — so it measured deliberate paraphrase, not memory. Now you tap to reveal, get a countdown scaled to length (4-15s), the composer is LOCKED while it's up, then the text is removed from the DOM. Enforced server-side, so reloading isn't a free second look. Paste is blocked and typing speed recorded — a hop that comes back near-verbatim typed faster than anyone composes gets flagged LIKELY COPIED. 2. ONE BAD LINK NO LONGER POISONS THE RUN. Every claim used to be scored against the original seed, so one person going off-script marked every ribbon "dropped" and made the rest meaningless. Breaks are now detected (MAD outlier, robust to the single wild hop that inflates sigma), named, and the analysis re-baselines: per-segment fidelity, a second decay line, and a second flow diagram from where the chain actually restarted. Host can undo a turn. 3. THE BLINDING WAS BYPASSABLE. Player IDs were broadcast and join trusted a client-supplied one — you could read the host's ID off the wire, rejoin as them, and be handed the seed. Seats now carry a secret token, never broadcast. Live run from tonight: 13% survived against the original, 34% re-baselined after the break, break correctly attributed. The abduction called it "vividness, 78% confidence." The salience-5 detail (a cat asleep in a pastry box) outlived every other claim — textbook Bartlett sharpening.

by Auny 🧡 · 33 ratings

SignTrail by @rookepoole is a browser-based PDF signing tool that produces byte-match integrity receipts, but left the audit trail trapped in a companion JSON file. This remix automatically appends a tamper-evident, DocuSign-style Certificate of Completion page directly to finalized PDFs. When you finalize a document, SignTrail generates the verification ID and completion timestamps, synthesizes an audit page detailing the original SHA-256 fingerprint, signer identity, and field inventory, and binds it permanently into the PDF before computing the final signed hash. To use it, drop any PDF into the workspace, place and complete your fields, and select Finalize document. The final PDF now carries its human-readable certificate on the last page while maintaining SignTrail's strict byte-for-byte cryptographic receipt verification.

by kaleb · 31 ratings

Red team work usually lives in chat threads, spreadsheets, and someone's notes, so findings get lost and nobody agrees on what's critical. CodeRed gives the crew one board. A tester files a finding with repro steps and evidence. A reviewer sets the severity, assigns an owner, and validates it. A maintainer resolves it once the fix is verified. Every step shows up in a live feed so the whole team sees the state of the engagement without asking. And between engagements, the crew sharpens up in the training lab: realistic scenarios where you write the report you'd actually file, get scored against a reference answer, and climb the leaderboard.

by Is Wilson · 26 ratings

The flow is basically: signed PDF ↓ calculate SHA-256 ↓ compare with receipt ↓ receipt ↓ recalculate receipt digest ↓ compare with stored digest ↓ both match ↓ VERIFIED