<aside> ℹ️ If you see this post published in September 2024 or reading from the future, Arcade just ended.

The remaining sessions are being reviewed and the shop should be open for a few weeks, but until then thanks for all the projects I saw on the scrapbook channel. Check my collection of Arcade projects I starred on GitHub, including my own.

Please keep your eyes peeled on Hack Club Slack and its socials on what's next.

</aside>

Quick Links

In a hurry? Here are the quick links, summarized for your pleasure:

• From Chris Walker of Hack Club HQ (for those not in the Slack workspace):
• The tracking issue for Arcade: https://github.com/andreijiroh-dev/personal-launchpad/issues/4
• Zach Latta in the wild: How do you do, fellow Hack Clubbers? (Changelog Interviews podcast), The Art of Code (TEDxYouth@Talinn)

It might be a bit silent on socials and hauling between autistic burnout and school, but GitHub and GitLab activity say something different, and this issue on my personal launchpad issue tracker says it all.

Hack Club what?

Chris Walker (2024) from the HQ described it as “**hacker culture for teenagers, institutionalized**” and “the hacker-oriented arm of the public education system.” It was founded by @zachlatta as a sixteen-year-old teen wished they had in high school.

The projects I built

Here's the rundown of what I have built during Arcade 2024:

• proxypartylab - The Caddy edition of hackclub/proxyparty for Recap Time Squad’s domains and friends, with documentation and even GitHub issue forms for others to request to set it up on their domains and let us do the infra work.
• golinks rewrite - A rewrite of my golinks (and now link shortener) in Cloudflare Workers
• dotenv-tools CLI - a CLI tool to centrally managed dotenvx-encrypted secrets over git a la gopass
• lorebooks.wiki Badges API - img.shields.io-like API, but using Deno KV for storing badge data, plus some Hack Club badges

proxypartylab - It’s proxyparty but in Caddy

The GCP Compute Engine VM setup is pretty Debian with a custom build of caddy via xcaddy build, and deploying changes via GitHub Actions over Tailscale (because you wouldn't want to poke around firewalls for the Caddy admin API and cause major nightmares).