u/LZRBRD

Most QR generators are quite limited stylistically. I quite like seeing differentiated designs that attract the eye but also compliment their immediate context e.g. poster

Bar.codes is our free to use qr code generator. The piece I'm happiest with is custom SVG support for the dots, your own shape instead of a fixed preset list, plus a solid range of frames and customisation controls. Exports in multiple formats, 200px up to 2000px so it holds up in print.

Appreciate any feedback. If you get use out of it and want to show support, please share it about.

Most QR generators are quite limited stylistically. I quite like seeing differentiated designs that attract the eye but also compliment their immediate context e.g. poster

Bar.codes is free to use. The piece I'm happiest with is custom SVG support for the dots, your own shape instead of a fixed preset list, plus a solid range of frames and customisation controls. Exports in multiple formats, 200px up to 2000px so it holds up in print.

Appreciate any feedback. If you get use out of it and want to show support, please share it about.

Ciarán and Khalil

Hi Folks, I've been building RedMsg "Red Message", an unofficial Man United fan site. The page I'm happiest with is the Transfers aspect, there I try to turn the usual chaos of transfer rumours (contradictory reports, recycled claims, quiet retractions) into a clean per-player view with evidence or artefacts to inspect. There's also a Season Review and a Lab section for data visualisation experiments, both still WIP.

I'm a United fan but the site is really a public testbed for a custom harness for persistent multi-agent orchestration systems I've been building. Getting a bunch of specialised LLM sub agents to try to behave like a stable software system without pretending the human can step away.

A few things that turned out to matter way more than prompting:

• The harness is built to keep the human at the top of the pyramid. This isn't a "set it running and walk away" system. The agents do the legwork monitoring, research, extraction, de-dup, scoring, writing but the harness deliberately puts the onus on me to govern the orchestration. Think newsroom: the agents are reporters and fact-checkers, but there's still an editor-in-chief, and taste, judgement and editorial standard live with the human. The point of the architecture isn't to remove me from the loop, it's to give me a clean control surface to govern from.
• An orchestrator can't supervise itself. A model will happily produce a plan, run it, and confidently report success that didn't happen. So there's a layer of critic agents reviewing important plans and findings. Final authority on direction and quality is still mine.
• The transfer ledger is append-only. Every claim is stored as an immutable event in SQLite; a Python process rebuilds the "current truth" projection from the full history using the latest scoring rules. Source data never gets overwritten, and a player's status can be regenerated from scratch. The frontend never touches the DB it just reads generated JSON.
• Files > chat history as a persistence layer. Agents pass work as structured Markdown/JSON artefacts rather than one giant shared conversation. Primitive, but inspectable and recoverable across crashes, restarts and model changes and it means I can read what any agent did and intervene.
• A green build doesn't mean the UI works. Added a Playwright smoke test that clicks every route after a fixed-position overlay passed the build and silently broke the footer in prod.

Stack: Vue 3 + Vite, Express on Node 20, SQLite for the ledger + flat JSON for everything published, Anthropic for the agents (Claude Code for orchestration and mostly Sonnet for sub agents with some Qwen), custom orchestration harness (veilCLI), single Linode box behind nginx, pm2/cron holding it together.

Still early and imperfect. I'd love any feedback on

• Appearance
• Contents
• Whether the Transfers page actually makes the reporting easier to follow

Site: redmsg.com