# Things I’ve built. Projects that Jamie Thingelstad has built: the ones he runs today and the ones he has stepped away from. Kept by Thingy, his sidekick. --- --- id: 612-poap-challenge title: 612 POAP Challenge summary: A summer 2025 scavenger hunt of 31 Minneapolis location POAPs that Jamie drew in the spirit of the 612 Series. collection: Historical projects status: archived url: https://612.poapchallenge.com/ started: 2025-05-31 ended: 2025-09-01 topics: - poap - crypto - play sources: - kind: website url: https://612.poapchallenge.com/ role: website sitemap: https://612.poapchallenge.com/sitemap.xml feed: https://612.poapchallenge.com/feed.xml - kind: website url: https://www.thingelstad.com/2025/05/31/poap-challenge-collect-them-now.html role: reference connections: - to: poap2rss label: shared its claims through detail: From July 2025 the challenge site posted every claim automatically, using POAP2RSS feeds merged with rssrssrssrss.com and imported into a Micro.blog account. source: https://www.thingelstad.com/2025/07/06/with-the-help-of-poaprss.html - to: airport-poap-rally label: led to detail: Jamie “enjoyed the 612 POAP Challenge so much” that he set up poapchallenge.com for more of them, registered poaprally.com, and used the same feed setup to track the Airport POAP Rally. source: https://www.thingelstad.com/2025/12/26/airport-poap-rally-website.html kind: lineage page: https://thingelstad.xyz/things/612-poap-challenge/ --- # 612 POAP Challenge A summer 2025 scavenger hunt of 31 Minneapolis location POAPs that Jamie drew in the spirit of the 612 Series. The 612 POAP Challenge was a citywide scavenger hunt that ran from the end of May through Labor Day 2025. [How to Play](https://612.poapchallenge.com/how-to-play/) listed 31 Minneapolis locations in five themed categories, each with a location POAP that could only be claimed in the POAP app within 100 meters of the spot. Two hidden easter-egg locations were left for the curious. Completing a category earned a Category Collector POAP, and collecting all 31 earned the top award. Jamie [announced it on May 31, 2025](https://www.thingelstad.com/2025/05/31/poap-challenge-collect-them-now.html). It joined geocaching with the [612 Series](https://www.thingelstad.com/2023/04/05/complete-collection-of.html) of Minneapolis NFTs by Erik Halaas and StayNftyMpls, which he collected in full and whose creator he had [interviewed](https://www.thingelstad.com/2024/01/15/interview-with-series.html) in 2024. Six days earlier he had made [his first location POAP](https://www.thingelstad.com/2025/05/25/i-created-my-very-first.html), at his family’s Charlie Brown Tree, and he wanted to build something bigger with the new feature. The challenge’s tokens were illustrated in the spirit of the 612 Series. “I love that I was able to create an entire activity on the POAP platform,” he wrote. In the interview he placed the challenge at the end of a longer habit: > I’ve also always had a collector mentality. As a kid, I loved collecting things. I still remember collecting every single M\*A\*S\*H figurine, for example. POAPs were a way of collecting, and the 612 POAP Challenge was the culmination of that: a game that ran on the POAP ecosystem, that I could pull people into and play in the real world. > > [Jamie, question 15](https://thingelstad.xyz/interviews/session-2/#q15) The challenge had its own Buttondown mailing list, and from July its site, hosted on Micro.blog, posted each claim as it happened through [POAP2RSS](https://www.thingelstad.com/2025/07/06/with-the-help-of-poaprss.html). The [first Collected Them All! award](https://www.thingelstad.com/2025/07/20/we-have-our-very-first.html) went on July 20, 2025 to @quinntchrest, who [speed ran](https://quinnchrest.com/2025/07/20/poap-challenge.html) the challenge by bike with a friend. The challenge closed as Labor Day ended on September 1, 2025, and the final awards went out a few days later. The site remains as its record, and the experience led Jamie to set up poapchallenge.com for future challenges. --- --- id: airport-poap-rally title: Airport POAP Rally summary: A Micro.blog site that posted, in near real time, every claim at the 100 airports of POAP’s Airport POAP Rally 2026. collection: Games status: retired url: https://web.archive.org/web/20260515161915/https://airport.poaprally.com/ started: 2025-12-26 topics: - poap - crypto - automation sources: - kind: website url: https://www.thingelstad.com/2025/12/26/airport-poap-rally-website.html role: reference - kind: website url: https://web.archive.org/web/20260515161915/https://airport.poaprally.com/ role: archive - kind: website url: https://web.archive.org/web/20260606234656/https://www.poapchallenge.com/ role: archive connections: - to: poap2rss label: posted its claims through detail: The site pulled claims for all 100 airports from POAP2RSS feeds, merged with rssrssrssrss, and published them through Micro.blog’s feed import. source: https://www.thingelstad.com/2025/12/26/airport-poap-rally-website.html - to: flight-path label: led to detail: Flight Path, built two months later on the same poaprally.com domain, drew its globe from a CSV of rally airports and drop IDs that Jamie already had from “another project I had done.” source: https://weekly.thingelstad.com/archive/342/ kind: lineage page: https://thingelstad.xyz/things/airport-poap-rally/ --- # Airport POAP Rally A Micro.blog site that posted, in near real time, every claim at the 100 airports of POAP’s Airport POAP Rally 2026. In December 2025 POAP announced the [Airport POAP Rally 2026](https://collections.poap.xyz/collections/airport-poap-rally-2026/26246), a year of location POAPs at 100 airports around the world. Jamie [set up a site to track it](https://www.thingelstad.com/2025/12/26/airport-poap-rally-website.html) at airport.poaprally.com. The rally was POAP’s. The tracker was his. What he saw in POAP, he said later, was [“a completely non-economic use case of crypto”](https://thingelstad.xyz/interviews/session-2/#q15). He built it the same way as the [612 POAP Challenge](https://612.poapchallenge.com/) feed: POAP2RSS feeds for every airport, merged with rssrssrssrss and imported into Micro.blog, so each claim became a post like “POAP 7586561 claimed by noah.savedsouls.eth at I passed through Minneapolis-Saint Paul International Airport (MSP) in 2026.” The posts were syndicated to @poapchallenge on Mastodon and @poapchallenge.com on Bluesky, and he planned rally updates on r/POAP. [Weekly Thing 337](https://weekly.thingelstad.com/archive/337/) pointed readers to “Follow the Rally.” The 612 challenge had also led him to set up [POAP Challenge](https://web.archive.org/web/20260606234656/https://www.poapchallenge.com/) at poapchallenge.com, meant to host “a challenge or two a year,” and to register poaprally.com. Two months later he built Flight Path on the same domain, a globe of the same rally from his own CSV of airports and drop IDs. The tracker read live claims, so it could not outlive POAP. The last copy in the Internet Archive is from [May 2026](https://web.archive.org/web/20260515161915/https://airport.poaprally.com/), and the host no longer answers. --- --- id: another-thing title: Another Thing summary: Jamie’s podcast. It started in October 2025 with an episode on how to start a podcast, and he is not done with it. collection: Publishing status: active url: https://another.thingelstad.com/ started: 2025-10-05 topics: - open-web sources: - kind: github repository: jthingelstad/another.thingelstad.com role: implementation - kind: website url: https://another.thingelstad.com/ role: website sitemap: https://another.thingelstad.com/sitemap.xml feed: https://another.thingelstad.com/podcast.xml - kind: website url: https://weekly.thingelstad.com/archive/329/ role: reference connections: [] page: https://thingelstad.xyz/things/another-thing/ --- # Another Thing Jamie’s podcast. It started in October 2025 with an episode on how to start a podcast, and he is not done with it. Another Thing is Jamie’s podcast and his third “thing,” after the blog and the Weekly Thing. The [first episode](https://another.thingelstad.com/2025/10/05/how-do-you-start-a.html), “How do you start a podcast?”, came out on October 5, 2025, and he announced it in [Weekly Thing 329](https://weekly.thingelstad.com/archive/329/) as “the podcast that I’ve been thinking about creating for a couple of years.” In it he talks about a chalkboard sign that told him to “be brave enough to suck at something new,” a story about Dr. John Carlis, whose class he took while studying computer science at the University of Minnesota, and an earlier attempt to turn the Weekly Thing into an AI-narrated show. That is still the only episode. In [Weekly Thing 346](https://weekly.thingelstad.com/archive/346/) he wrote that he was not giving up on the show, and in November 2026 he said the same thing out loud: > I have no intention of getting rid of it, and I am still committed to that project. … I know I can’t just sit down in front of a microphone and talk ad hoc. I need some kind of outline to work against and some kind of interface that helps me record, and I’m figuring that out. > > [Jamie, question 21](https://thingelstad.xyz/interviews/session-3/#q21) What he wants it to be is [“a way for me to go deeper on topics that likely appear in the Weekly Thing”](https://thingelstad.xyz/interviews/session-3/#q21), [“kind of a behind the scenes or a director’s commentary, if you will”](https://thingelstad.xyz/interviews/session-3/#q21). In 2026 he built Another Thing Builder to make episodes, then retired it that October and moved podcast authoring into WT Builder, so the next episode has an easier path. Thingy can search the episode transcripts. Asked what he hopes is still running in twenty years, he named the podcast with the blog and the Weekly Thing, with a [“published history of new podcasts”](https://thingelstad.xyz/interviews/session-5/#q35). --- --- id: ask-planet-kubb title: Ask Planet Kubb summary: A Question2Answer site where Kubb players asked and answered questions about the game, one of the Planet Kubb sites Jamie built with Garrick van Buren. collection: Historical projects status: retired url: https://web.archive.org/web/20141201215020/http://ask.planetkubb.com/ ended: "2018" topics: - play sources: - kind: website url: https://web.archive.org/web/20160206093959/http://ask.planetkubb.com/ role: archive photograph: true connections: - to: planet-kubb label: is part of detail: Ask Planet Kubb described itself as run alongside the Planet Kubb planet feed and linked to the Planet Kubb Wiki and The Pitch. source: https://web.archive.org/web/20120702124724/http://ask.planetkubb.com/ page: https://thingelstad.xyz/things/ask-planet-kubb/ --- # Ask Planet Kubb A Question2Answer site where Kubb players asked and answered questions about the game, one of the Planet Kubb sites Jamie built with Garrick van Buren. Ask Planet Kubb was a question-and-answer site for the Kubb community at ask.planetkubb.com. It welcomed visitors to a “community driven site to learn more about the great game of Kubb,” run alongside the Planet Kubb planet feed. It was online by June 2012, when Garrick van Buren and Jamie linked it in [Open Loop #0](https://www.thingelstad.com/projects/open-loop/0-but-no-shoes/). By [July 2012](https://web.archive.org/web/20120702124724/http://ask.planetkubb.com/) it had 75 questions, 182 answers and 64 users, with polls on who would win each group at the 2012 USA Kubb Nationals. The two built it together (“then we built Ask Planet Kubb,” as Jamie put it), and on [Open Loop #1](https://www.thingelstad.com/projects/open-loop/1-big-fuzzy-dead-cat/) he called it “the number one place for Q&A in the community,” adding, “it’s a low bar.” Garrick was one of its most active answerers. Of those years Jamie said, [“He and I enjoyed building things together for many years and had a lot of fun doing it”](https://thingelstad.xyz/interviews/session-2/#q17). Jamie ran the site on [Question2Answer](https://www.question2answer.org/) “for a number of years,” which was simple to run on PHP and MySQL. Spam registrations kept getting through ReCaptcha and a text-question captcha, so in November 2014 he wrote [q2a-number-captcha](https://github.com/jthingelstad/q2a-number-captcha), which asks for one digit of a nine-digit number spelled out in words ([Question2Answer Number Captcha](https://www.thingelstad.com/2014/11/16/questionanswer-number-captcha.html)). The site was still serving questions in [July 2018](https://web.archive.org/web/20180720082755/http://ask.planetkubb.com/), with the last answers dated December 2017. By [November 2018](https://web.archive.org/web/20181108010540/http://ask.planetkubb.com/) the address showed only a default web server page. --- --- id: cards title: Cards summary: The share image for pages on Jamie’s sites, a 1200 by 630 card drawn from the page itself and made on demand at cards.thingelstad.com. collection: Publishing status: active url: https://github.com/jthingelstad/cards.thingelstad.com started: 2026-10-24 topics: - open-web sources: - kind: github repository: jthingelstad/cards.thingelstad.com role: implementation connections: - to: jamie-thingelstad-blog label: draws the share cards for detail: Every blog post has shared its own card since October 24, 2026, when Thing Hugo 2.0.19 pointed each post’s share image at cards.thingelstad.com. source: https://github.com/jthingelstad/thing-hugo/commit/ecb83ccab3cce43601b16c489f04689787496a41 - to: weekly-thing label: draws the share cards for detail: Since October 25, 2026, every issue shares a card on its cover photo, with its summary and its count of links and journal entries, and the front page shares the newest issue’s card. source: https://github.com/jthingelstad/weekly.thingelstad.com/pull/28 - to: another-thing label: draws the share cards for detail: Since October 25, 2026, every episode shares a card with its number, date, summary, and running time. source: https://github.com/jthingelstad/another.thingelstad.com/pull/6 - to: linking-things label: draws the share cards for detail: Since October 25, 2026, each saved link’s page shares a card with its title, its site, the day Jamie saved it, the Weekly Thing issues that carried it, and his note when the note is his own. source: https://github.com/jthingelstad/links.thingelstad.xyz/pull/21 artifacts: - file: red-leaves.jpg title: A blog post over its photo caption: A short post with a wide photo sets its words in white over the photo, the way an issue sits on its cover. date: 2026-10-25 source: https://www.thingelstad.com/2026/10/24/red-leaves.html url: https://thingelstad.xyz/things/cards/artifacts/red-leaves.jpg - file: weekly-thing-353.jpg title: A Weekly Thing issue caption: Weekly Thing 353 on its cover photo, with the issue’s summary and its count of links and journal entries. date: 2026-10-25 source: https://weekly.thingelstad.com/archive/353/ url: https://thingelstad.xyz/things/cards/artifacts/weekly-thing-353.jpg - file: another-thing-episode.png title: An Another Thing episode caption: The first episode, with its number, date, summary, and running time. date: 2026-10-25 source: https://another.thingelstad.com/2025/10/05/how-do-you-start-a.html url: https://thingelstad.xyz/things/cards/artifacts/another-thing-episode.png - file: linking-things-link.png title: A saved link caption: A link on Linking Things with its site, the day Jamie saved it, the issue that carried it, and his note. date: 2026-10-25 source: https://links.thingelstad.xyz/links/dec34be50cef/ url: https://thingelstad.xyz/things/cards/artifacts/linking-things-link.png page: https://thingelstad.xyz/things/cards/ --- # Cards The share image for pages on Jamie’s sites, a 1200 by 630 card drawn from the page itself and made on demand at cards.thingelstad.com. Cards makes the share image for pages on Jamie’s sites: the 1200 by 630 picture that appears when a link is shared on Mastodon, Bluesky, Slack, or iMessage. Each card is drawn from the page itself. A blog post shows its title or opening words, its date and categories, and its first photo, and a short post with a wide photo sets its words over the photo. A Weekly Thing issue sits on its cover photo with its summary and its count of links and journal entries. An Another Thing episode shows its number and running time. A saved link on Linking Things shows its title, its site, and the issues that carried it, with Jamie’s note when the note is his own. He built it with coding agents on October 24, 2026, after deciding against Micro.blog’s own card styles. His use the full canvas, with no photo of him and the blog’s type in black and white. The blog came first, that same day. Weekly Thing, Another Thing, and Linking Things followed on October 25, each with a card of its own. Each page names its card in its share-image tag, with a short hash of what the card shows, so an edited page gets a new card. The first request for a card runs a Lambda function that reads the page, lays the card out with Satori, and renders it with resvg; CloudFront then keeps it for a year. It draws only the card a page actually names, so it cannot be used to make any other image. Cards with a photo are JPEG, to stay under Bluesky’s 1 MB limit, and emoji are drawn from Twemoji. Asked whether Cards, Sync and the Redirector are things or plumbing, Jamie said [“They’re things, because they don’t serve just one service and they bring some intelligence.”](https://thingelstad.xyz/interviews/session-6/#q41) And of this one: [“Cards has personality because people see it in the share preview.”](https://thingelstad.xyz/interviews/session-6/#q41) --- --- id: changelog title: Changelog summary: An iPhone app for getting notes into Release Notes in two taps, with photos, voice memos, places, Upcoming dates, Siri, and widgets. Jamie’s first iPhone app. collection: Personal tools and making status: active url: https://github.com/jthingelstad/changelog-ios started: 2026-10-29 topics: - play sources: - kind: github repository: jthingelstad/changelog-ios role: implementation - kind: website url: https://notes.yourversionnumber.com/guide/changelog/ role: reference connections: - to: release-notes label: sends notes into detail: Changelog talks only to Release Notes’ public API, as any app someone writes for it can. It signs in with Release Notes, which asks what it may do and gives it a token of its own. source: https://notes.yourversionnumber.com/guide/changelog/ story: color: "#1a4fe0" introduction: What changed today? Commit. engineering: - The app talks only to Release Notes’ public /v1 API. Signing in is OAuth with PKCE, and the code that comes back is spent once for an ordinary API token, with no refresh token. - Every write goes through an offline queue with an idempotency key, so a note written without a connection waits on the phone, and a resend never makes a duplicate. - ChangelogKit, a Swift package with the API client, the queue, a port of Release Notes’ hashtag rules, and the Keychain storage, is tested on its own. The app, the share extension, and the widgets are SwiftUI on top of it, with no third-party packages. - A test cycle drives the app on a simulator against the Release Notes dev server and its fictional account, and checks each note, photo, voice memo, and date against what the server kept. stack: - Swift and SwiftUI - iOS 26 - App Intents - WidgetKit - Release Notes API - TestFlight related: [] questions: - What does Changelog do that the Release Notes email and website do not? - How does Changelog keep a note written offline from being lost or sent twice? - What did Changelog look like before its redesign? bundles: - id: the-plan title: The plan caption: Before any code, two documents written for Jamie’s review on the morning of October 29, and kept up to date through the day as he answered their questions. One is the API Release Notes would need, the other the app that would use it, and each was checked against the other. They are here as they were, lightly redacted. - id: first-scaffold title: The first scaffold caption: From the repository’s first half hour. - id: before title: "Before: the first day, in iOS’s own look" caption: October 29, on the simulator against the Release Notes dev server’s fictional account. Grouped lists on gray, the system font, and blue links. - id: after title: "After: on the paper" caption: The same screens on October 30, after the redesign that put every screen on the Release Notes website’s paper, with the same fictional account and the same dates. Cream and navy, cobalt for actions, a tangerine Commit, and the site’s two typefaces, Bricolage Grotesque and Martian Mono. - id: icon-studies title: Finding a separate icon caption: Icon studies made with Codex on October 31, 2026. The single folded v went to Release Notes. Changelog’s selected direction repeats the fold as three stacked versions; a list of paper slips was set aside. - id: member-icons title: Four member editions caption: Paper, Copper, Terminal and Afterglow keep the same three-layer mark. These are proposed alternative app icons for Supporting Members of the Weekly Thing. - id: icon-design-files title: The design record caption: The sequence, prompts and small-size previews from the design exercise. These files record choices and studies, not a release of the app. artifacts: - file: api-plan-2026-10-29.md title: The API plan caption: "Tokens, a public API and Changelog as one idea with two doors: what the API would do, the order to build it in, and Jamie’s calls on each question, quoted as he gave them. Every phase of it was built that day. Taken out: a cousin’s name, an email address, and one sentence." date: 2026-10-29 bundle: the-plan url: https://thingelstad.xyz/things/changelog/artifacts/api-plan-2026-10-29.md - file: app-scope-2026-10-29.md title: The app’s scope caption: "Changelog’s screens sketched in text, notifications with no push server, and a table checking each thing the app would do against the API plan, which changed the plan before any of it was built. Taken out: a cousin’s name and an email address." date: 2026-10-29 bundle: the-plan url: https://thingelstad.xyz/things/changelog/artifacts/app-scope-2026-10-29.md - file: app-icon.png title: The icon caption: The shared V and dot over two lines of notes, from the first scaffold, before the separate icon studies below. date: 2026-10-29 source: https://github.com/jthingelstad/changelog-ios/commit/db1850e180878ab1c61e933aad28a4603116d59c bundle: first-scaffold url: https://thingelstad.xyz/things/changelog/artifacts/app-icon.png - file: first-readme.md title: The first README caption: From the first scaffold, before the API it talks to was live. Photos and voice memos, Upcoming, and Shortcuts and widgets are listed for later versions; all three arrived that same day. date: 2026-10-29 source: https://github.com/jthingelstad/changelog-ios/blob/db1850e180878ab1c61e933aad28a4603116d59c/README.md bundle: first-scaffold url: https://thingelstad.xyz/things/changelog/artifacts/first-readme.md - file: sign-in-2026-10-29.png title: The first screen caption: The first scaffold’s sign-in, that morning, which took a token pasted from Release Notes’ Settings. Signing in with Release Notes itself came that evening. date: 2026-10-29 bundle: before url: https://thingelstad.xyz/things/changelog/artifacts/sign-in-2026-10-29.png - file: log-2026-10-29.png title: Log, in iOS’s own look caption: Today’s version, a box for what changed, one-tap tags, buttons for a photo, the camera, a voice memo and the place, and Commit, with today’s activity underneath. date: 2026-10-29 bundle: before url: https://thingelstad.xyz/things/changelog/artifacts/log-2026-10-29.png - file: upcoming-2026-10-29.png title: Upcoming caption: Birthdays, an anniversary, a trip and an event, each in the line the morning email gives it, like “Mom turns 6.8.0.” date: 2026-10-29 bundle: before url: https://thingelstad.xyz/things/changelog/artifacts/upcoming-2026-10-29.png - file: add-a-date-2026-10-29.png title: Adding a date caption: A birthday, anniversary, trip or event, whether it goes in the morning email, and when the phone sends its reminder. date: 2026-10-29 bundle: before url: https://thingelstad.xyz/things/changelog/artifacts/add-a-date-2026-10-29.png - file: activity-2026-10-29.png title: Activity caption: What came in, changed and went out, from every channel, without a note’s words. date: 2026-10-29 bundle: before url: https://thingelstad.xyz/things/changelog/artifacts/activity-2026-10-29.png - file: settings-2026-10-29.png title: The foot of Settings caption: "Pinned tags, links to Release Notes, a debug build’s server switch, and the build line: Changelog 0.0.0, build 8a54afc, made Oct 29 at 3:57 PM CDT." date: 2026-10-29 bundle: before url: https://thingelstad.xyz/things/changelog/artifacts/settings-2026-10-29.png - file: sign-in-2026-10-30.png title: Signing in caption: By now Changelog signs in with Release Notes itself, which asks the person signing in to name the token it keeps and choose what it may do. A pasted token still works. date: 2026-10-30 bundle: after url: https://thingelstad.xyz/things/changelog/artifacts/sign-in-2026-10-30.png - file: log-2026-10-30.png title: Log on the paper caption: The day in mono capitals, today’s version large and tomorrow’s under it, and below, a note filed and read back with its words. date: 2026-10-30 bundle: after url: https://thingelstad.xyz/things/changelog/artifacts/log-2026-10-30.png - file: upcoming-2026-10-30.png title: Upcoming on the paper caption: The same five dates, each day in cobalt mono over its line. date: 2026-10-30 bundle: after url: https://thingelstad.xyz/things/changelog/artifacts/upcoming-2026-10-30.png - file: add-a-date-2026-10-30.png title: Adding a date on the paper caption: The same form, flat on the paper instead of in grouped boxes. date: 2026-10-30 bundle: after url: https://thingelstad.xyz/things/changelog/artifacts/add-a-date-2026-10-30.png - file: activity-2026-10-30.png title: Activity on the paper caption: With a line marking the last visit, so what is new since is on top. date: 2026-10-30 bundle: after url: https://thingelstad.xyz/things/changelog/artifacts/activity-2026-10-30.png - file: settings-2026-10-30.png title: The foot of Settings on the paper caption: "The build line in Martian Mono: Changelog 0.0.1, build 974deb4." date: 2026-10-30 bundle: after url: https://thingelstad.xyz/things/changelog/artifacts/settings-2026-10-30.png - file: log-paper-2026-10-30.png title: Log, as the guide shows it caption: The screenshot on Release Notes for Changelog, the app’s page on the Release Notes site. date: 2026-10-30 source: https://notes.yourversionnumber.com/guide/changelog/ bundle: after url: https://thingelstad.xyz/things/changelog/artifacts/log-paper-2026-10-30.png - file: upcoming-paper-2026-10-30.png title: Upcoming in dark caption: The same paper in the website’s dark navy, from the guide. date: 2026-10-30 source: https://notes.yourversionnumber.com/guide/changelog/ bundle: after url: https://thingelstad.xyz/things/changelog/artifacts/upcoming-paper-2026-10-30.png - file: icon-entries-2026-10-31.png title: Entries, set aside caption: Three curled paper slips on tangerine, each with a cobalt dot. This was the list-based alternative to repeating the version mark. date: 2026-10-31 bundle: icon-studies url: https://thingelstad.xyz/things/changelog/artifacts/icon-entries-2026-10-31.png - file: icon-versions-first-2026-10-31.png title: Versions, the first stack caption: Three folded v marks in cobalt, tangerine and ivory on ink navy. This became the direction for Changelog. date: 2026-10-31 bundle: icon-studies url: https://thingelstad.xyz/things/changelog/artifacts/icon-versions-first-2026-10-31.png - file: icon-versions-2026-10-31.png title: Versions, refined caption: The stack with more clear space around its edges and simpler fold shading. It was checked at 60 pixels beside Release Notes’ single v and dot. date: 2026-10-31 bundle: icon-studies url: https://thingelstad.xyz/things/changelog/artifacts/icon-versions-2026-10-31.png - file: icon-versions-paper-2026-10-31.png title: Paper caption: Cobalt, tangerine and ink navy paper on cream. date: 2026-10-31 bundle: member-icons url: https://thingelstad.xyz/things/changelog/artifacts/icon-versions-paper-2026-10-31.png - file: icon-versions-copper-2026-10-31.png title: Copper caption: Three copper tones on warm charcoal, with brushed metal in place of paper. date: 2026-10-31 bundle: member-icons url: https://thingelstad.xyz/things/changelog/artifacts/icon-versions-copper-2026-10-31.png - file: icon-versions-terminal-2026-10-31.png title: Terminal caption: Three phosphor-green tones on near-black green. date: 2026-10-31 bundle: member-icons url: https://thingelstad.xyz/things/changelog/artifacts/icon-versions-terminal-2026-10-31.png - file: icon-versions-afterglow-2026-10-31.png title: Afterglow caption: Violet, coral and peach paper on dark plum. date: 2026-10-31 bundle: member-icons url: https://thingelstad.xyz/things/changelog/artifacts/icon-versions-afterglow-2026-10-31.png - file: icon-design-process-2026-11-01.txt title: How the two marks separated caption: A record of the single v moving to Release Notes, the two Changelog directions, the selected stack, member editions and favicon studies. date: 2026-11-01 bundle: icon-design-files url: https://thingelstad.xyz/things/changelog/artifacts/icon-design-process-2026-11-01.txt - file: icon-design-files-2026-11-01.zip title: The icon design files caption: Full-size PNG studies, small-size previews, the design record and generation prompts. date: 2026-11-01 preview: icon-design-files-preview-2026-11-01.png bundle: icon-design-files url: https://thingelstad.xyz/things/changelog/artifacts/icon-design-files-2026-11-01.zip page: https://thingelstad.xyz/things/changelog/ --- # Changelog An iPhone app for getting notes into Release Notes in two taps, with photos, voice memos, places, Upcoming dates, Siri, and widgets. Jamie’s first iPhone app. Changelog is an iPhone app for getting notes into [Release Notes](https://notes.yourversionnumber.com/), the daily Your Version Number email. It is not a second Release Notes: reading, searching, and looking back stay on the web, and Changelog is for getting things in. You write a line, tap a tag, and Commit, and it is in today’s notes. A note can carry photos, a voice memo, or where you are, and Siri, the Action Button, a widget, or the share sheet can start one. Your Upcoming dates, and the activity log from every channel, are a tab away. Jamie built it with coding agents in a single day, starting on the morning of October 29, 2026. It began as two documents, a plan for the API Release Notes would need and a scope for the app, and both are below. The repository was made at 7:43 a.m., and by 8:06 the first scaffold had Log, Activity, Settings, and a sign-in that took a pasted token. Its first README listed photos and voice memos, Upcoming, and Shortcuts and widgets as versions to come. All three arrived that same day, along with signing in with Release Notes, and the first build was on TestFlight by that evening. It is, in his words, [“my very first attempt at an iPhone app”](https://thingelstad.xyz/interviews/session-3/#q19). For its first day it wore iOS’s own look: grouped lists on gray, the system font, and blue links. On October 30 he asked for it to match the Release Notes website, and every screen, sheet, and widget moved onto the site’s paper: cream and navy, cobalt for actions, a tangerine Commit, and the site’s two typefaces, Bricolage Grotesque and Martian Mono. The screens below show each one before and after, taken on the simulator against the Release Notes dev server and its fictional account. On October 31, 2026, Jamie explored [separate icons](#artifacts-icon-studies) for Changelog and Release Notes with Codex. The [single folded v and its dot](/things/release-notes/#artifacts-icon-studies) went to Release Notes. For Changelog he chose three folded v marks stacked diagonally, called Versions. Paper, Copper, Terminal and Afterglow followed as [member-edition studies](#artifacts-member-icons). The [design record](#artifacts-icon-design-files) keeps the discarded direction, the refinements and the generation prompts. It numbers itself the way Release Notes numbers people. Changelog was 0.0.0 on the day it started and 0.0.1 the next, and the foot of Settings names each build’s version and commit. What each version brought is written up as [Release Notes for Changelog](https://notes.yourversionnumber.com/guide/changelog/) on the Release Notes site, which also has the TestFlight invitation. Its code is open on GitHub under the MIT License. His cousin Quinn, he said, is [“working alongside me to build an Android version of Changelog that works with it”](https://thingelstad.xyz/interviews/session-3/#q19). --- --- id: charlie-brown-tree title: Charlie Brown Tree summary: A tree stump at Magic Pines on Cannon Lake, carved into Peanuts characters under Snoopy’s doghouse by Adam Gale of Rust n’ Grain. collection: Historical projects status: archived url: https://www.thingelstad.com/magic-pines/charlie-brown-tree/ started: "2020" topics: - making sources: - kind: website url: https://www.thingelstad.com/magic-pines/charlie-brown-tree/ role: reference - kind: website url: https://www.thingelstad.com/2020/05/24/little-snippet-of.html role: reference - kind: website url: https://weekly.thingelstad.com/archive/163/ role: reference - kind: website url: https://www.thingelstad.com/2025/05/25/i-created-my-very-first.html role: reference connections: - to: 612-poap-challenge label: led to detail: The Peanuts Tree was Jamie’s first location POAP, in May 2025. Six days later he announced the 612 POAP Challenge, built on the same feature. source: https://www.thingelstad.com/2025/05/31/poap-challenge-collect-them-now.html kind: lineage artifacts: - file: before-and-during.jpg title: Before and during caption: Two pictures side by side from the project page. On the left the tree as it stood, on the right the same trunk partly carved and painted, with scaffolding around it and the red doghouse already on top. date: "2020" source: https://www.thingelstad.com/magic-pines/charlie-brown-tree/ url: https://thingelstad.xyz/things/charlie-brown-tree/artifacts/before-and-during.jpg - file: carving-in-progress.jpg title: The carving under way caption: A Peanuts character holding Snoopy, taking shape at the foot of the stump, with scaffolding behind. date: 2020-05-24 source: https://www.thingelstad.com/2020/05/24/little-snippet-of.html url: https://thingelstad.xyz/things/charlie-brown-tree/artifacts/carving-in-progress.jpg - file: snoopy-on-the-doghouse.jpg title: Snoopy on the doghouse caption: Snoopy as the Flying Ace, in goggles and a red scarf, on the red doghouse at the top of the tree. From the project page. date: "2020" source: https://www.thingelstad.com/magic-pines/charlie-brown-tree/ url: https://thingelstad.xyz/things/charlie-brown-tree/artifacts/snoopy-on-the-doghouse.jpg - file: first-snow.jpg title: The tree in the snow caption: The finished tree, Snoopy on his red doghouse at the top, in falling snow at Cannon Lake. It was the photograph in Weekly Thing 163. date: 2020-10-31 source: https://weekly.thingelstad.com/archive/163/ url: https://thingelstad.xyz/things/charlie-brown-tree/artifacts/first-snow.jpg - file: snowman.jpg title: With a snowman caption: Big snowflakes falling on a small snowman and the Peanuts Tree, from Weekly Thing 245. date: 2023-03-11 source: https://weekly.thingelstad.com/archive/245/ url: https://thingelstad.xyz/things/charlie-brown-tree/artifacts/snowman.jpg - file: poap-2025.png title: The location POAP caption: The round art of the Magic Pines 2025 Peanuts Tree POAP, which visitors could mint when they came to the tree. date: 2025-05-25 source: https://www.thingelstad.com/2025/05/25/i-created-my-very-first.html url: https://thingelstad.xyz/things/charlie-brown-tree/artifacts/poap-2025.png page: https://thingelstad.xyz/things/charlie-brown-tree/ --- # Charlie Brown Tree A tree stump at Magic Pines on Cannon Lake, carved into Peanuts characters under Snoopy’s doghouse by Adam Gale of Rust n’ Grain. The Charlie Brown Tree, which Jamie’s family also calls the Peanuts Tree, is a tall tree stump at Magic Pines, their place on Cannon Lake, carved with Peanuts characters climbing toward Snoopy’s red doghouse on top. Adam Gale of [Rust n’ Grain](https://rustngraincom.wordpress.com/) carved it. Jamie posted [the carving in progress](https://www.thingelstad.com/2020/05/24/little-snippet-of.html), Charlie Brown holding Snoopy emerging from the wood, on May 24, 2020, and the tree in the snow in [Weekly Thing 163](https://weekly.thingelstad.com/archive/163/) that October. The [project page](https://www.thingelstad.com/magic-pines/charlie-brown-tree/) has videos. The logs left over from the tree became Escher-inspired [carved log tables](https://www.thingelstad.com/2021/06/12/i-love-our.html) for the fire area in 2021, another Rust n’ Grain project. In May 2025 he made the tree the site of [his first location-based POAP](https://www.thingelstad.com/2025/05/25/i-created-my-very-first.html), which visitors could mint by standing beside it. It is archived because it is finished. In the interview he called it [“a very finite project”](https://thingelstad.xyz/interviews/session-4/#q28), carved [“out of a dead tree at our cabin”](https://thingelstad.xyz/interviews/session-4/#q28), and [“an amazing piece of art”](https://thingelstad.xyz/interviews/session-4/#q28). --- --- id: clash-royale-api-agent-reference title: Clash Royale API Agent Reference summary: Agent-first documentation of how the Clash Royale API actually behaves, with observed response shapes, quirks, and every game mode. collection: Games status: active url: https://github.com/jthingelstad/cr-agent-api-docs started: 2026-03 topics: - agents - play sources: - kind: github repository: jthingelstad/cr-agent-api-docs role: implementation connections: - to: elixir label: supplies game reference data to detail: Elixir’s deck archetype labels and card roles come from data files in the reference. source: https://elixir.poapkings.com/docs/archetypes page: https://thingelstad.xyz/things/clash-royale-api-agent-reference/ --- # Clash Royale API Agent Reference Agent-first documentation of how the Clash Royale API actually behaves, with observed response shapes, quirks, and every game mode. This is not a thin endpoint list. Jamie wrote it for LLM agents, coding agents, and API clients that need to know how the API really behaves: endpoint-by-endpoint notes on parameters, pagination, caching, and errors, field-level models drawn from live responses, the endpoints that are broken, disabled, or removed, and the game modes beyond Trophy Road, so an agent doesn’t treat one ladder as the whole game. Machine-readable files cover the mode taxonomy, card roles, and deck names. It started inside [Elixir Bot](https://github.com/jthingelstad/elixir-bot) as cr-api-docs. In March 2026 Codex read it and used it to [suggest a feature](https://www.thingelstad.com/2026/03/10/automatic-programming-speed.html) for tracking ladder and Path of Legend momentum. Then it became a public repository of its own. The copies he had kept inside other projects drifted, so he removed them, and now [Elixir](https://github.com/jthingelstad/elixir-mcp/blob/main/AGENTS.md) and Elixir Drop treat this one repository as the truth about the Clash Royale API. Its [agent guide](https://github.com/jthingelstad/cr-agent-api-docs/blob/main/AGENTS.md) asks any agent that gets surprised by the live API to write the finding down here, after checking the claim with a live probe tool. The docs build guards the observed enum values, so a later rewrite can’t quietly drop them. It is an unofficial fan reference under Supercell’s Fan Content Policy. --- --- id: elixir title: Elixir summary: A service that records Clash Royale history and serves it to players, clans, and their AI agents over MCP. collection: Games status: active url: https://elixir.poapkings.com/ started: 2026-09-03 topics: - agents - mcp - play sources: - kind: github repository: jthingelstad/elixir-mcp role: implementation - kind: website url: https://elixir.poapkings.com/ role: website sitemap: https://elixir.poapkings.com/sitemap.xml feed: https://elixir.poapkings.com/feed.xml connections: - to: elixir-mcp-discord label: provides recorded facts to detail: The configurable Discord agent gets its game facts through Elixir MCP tools. source: https://github.com/jthingelstad/elixir-mcp-discord - to: elixir-clan label: includes detail: Clan management is a feature of the same Elixir platform and shares its recorded history, application, and runtime. source: https://elixir.poapkings.com/updates/2026-10-02-clan-is-part-of-elixir - to: poap-kings label: supplies clan data to detail: The POAP KINGS website reads clan and roster data from Elixir’s JSON API. source: https://poapkings.com/elixir/ story: color: "#8860d9" introduction: The game remembers the present. Elixir remembers what happened. engineering: - Independent collectors fetch public game observations from machines with allowlisted IP addresses, sharing one rate budget. - One recorded history serves the browser application, a remote MCP server, and a versioned JSON API. - Everything cloud-side is serverless, with PostgreSQL, S3, and Lambda functions in one CloudFormation stack. - Clan management and Ladder are features of the same platform, sharing its record and application shell. stack: - Eleventy - React - PostgreSQL - AWS Lambda - MCP related: - elixir-drop - elixir-mcp-discord - elixir-mcp-collector - poap-kings questions: - How does Elixir keep the history? - What grew out of Elixir Bot? source: https://elixir.poapkings.com/docs/architecture sourceLabel: Architecture page: https://thingelstad.xyz/things/elixir/ --- # Elixir A service that records Clash Royale history and serves it to players, clans, and their AI agents over MCP. The Clash Royale API gives you a current snapshot and a short, rotating battle log of about 30 battles, and then it is gone. Elixir records observations continuously so players, clans, and their agents can ask questions about the history: battles, rosters, river races, and seasons. Jamie built it by turning [Elixir Bot](https://github.com/jthingelstad/elixir-bot), the POAP KINGS clan agent, “upside-down.” Instead of one bot keeping its own database, the record became a service that any agent can use over MCP. He and Claude wrote the specification, then he put Claude Code in a loop. [Six hours later](https://www.thingelstad.com/2026/09/03/i-had-an-idea-to.html) there was a working system, and [Elixir MCP launched](https://elixir.poapkings.com/updates/2026-09-03-elixir-mcp-launches) on September 3, 2026. The next day the old bot’s archive was [replayed into the recorder](https://elixir.poapkings.com/updates/2026-09-04-four-months-of-history-imported), bringing battles back to mid-May. In the browser, Elixir is the Console for a player’s own history and the [Ladder](https://elixir.poapkings.com/ladder) for exploring ladder results. Elixir Clan runs in the same application, and Elixir Drop signs its players in with Elixir. Volunteer collectors do all of the fetching. Elixir is free for anyone, and its [updates feed](https://elixir.poapkings.com/updates) records every user-visible change. Elixir is also the thing Jamie named when asked about wrong turns. For a while he had pointed it at the play of the top 200 players in the game, and [“I realized that I had taken the wrong turn and turned the project into something that was no longer fun and about community”](https://thingelstad.xyz/interviews/session-1/#q3). Undoing it took days. The lesson he took from it: > you really need to understand the vision of what you’re building and why you’re building it, so that you can realize, oh, this is a wrong turn, as soon as possible. > > [Jamie, question 3](https://thingelstad.xyz/interviews/session-1/#q3) He does not expect it to last the way the blog will: [“I’m sure 20 years from now, Elixir will be done and retired.”](https://thingelstad.xyz/interviews/session-5/#q35) --- --- id: elixir-bot title: Elixir Bot summary: POAP KINGS’ first clan agent, a Discord bot that watched the clan and talked with its members from February to September 2026, and the start of Elixir. collection: Games status: retired url: https://github.com/jthingelstad/elixir-bot started: 2026-02 ended: 2026-09-26 topics: - agents - play sources: - kind: github repository: jthingelstad/elixir-bot role: implementation connections: - to: elixir label: gave rise to detail: The original Elixir Bot was retired in September 2026. Recorded game history became the broader Elixir platform. source: https://github.com/jthingelstad/elixir-bot kind: lineage - to: elixir-mcp-discord label: was succeeded by detail: The configurable Elixir Discord agent took over the original bot’s Discord role. source: https://github.com/jthingelstad/elixir-bot kind: lineage - to: elixir-mcp-collector label: gave rise to detail: The original bot’s game observation work grew into a separate Collector that feeds Elixir’s recorded history. source: https://github.com/jthingelstad/elixir-bot kind: lineage - to: elixir-clan label: gave rise to detail: The original bot’s clan management work carried forward into Elixir Clan, now a feature of the shared Elixir platform. source: https://github.com/jthingelstad/elixir-bot kind: lineage - to: clash-royale-api-agent-reference label: gave rise to detail: The Clash Royale API notes began inside Elixir Bot as cr-api-docs before becoming a standalone reference. source: https://www.thingelstad.com/2026/03/10/automatic-programming-speed.html kind: lineage - to: otto label: was first coded by detail: Otto wrote the first version of the bot, a templated command-and-response Discord bot. source: https://weekly.thingelstad.com/archive/342/ - to: poap-kings label: published detail: The bot regenerated the clan website’s roster pages, member bios, and home page message and committed them to git. source: https://sessions.minnestar.org/sessions/2094 - to: weekly-thing-workshop label: led to detail: Jamie wrote that Elixir had shown him “Discord is a reasonable place for an agent to run,” and he put the Weekly Thing Studio’s agents there. source: https://www.thingelstad.com/2026/05/12/the-weekly-thing-team.html kind: lineage page: https://thingelstad.xyz/things/elixir-bot/ --- # Elixir Bot POAP KINGS’ first clan agent, a Discord bot that watched the clan and talked with its members from February to September 2026, and the start of Elixir. Elixir Bot was the agent for POAP KINGS, the Clash Royale clan Jamie runs with his son Tyler and Tyler’s cousin Levi. He wanted [his own agent](https://weekly.thingelstad.com/archive/342/) so he could understand the agentic loop, data design, and memory from the inside: one that would monitor the clan, help it win wars, suggest strategies, and recommend promotions and demotions to leadership. In the interview he put the premise in one line: [“could an agent help me run and manage a Clash Royale clan?”](https://thingelstad.xyz/interviews/session-2/#q14) It grew fast in early 2026. Otto wrote the first version, a templated Discord bot. An LLM and a journal kept on the clan website [gave it a brain](https://ottoai.thingelstad.com/2026/03/01/building-elixir-when-a-discord.html), an hourly heartbeat and a SQLite memory made it agentic, and a long session with Codex [rebuilt its data and tools](https://ottoai.thingelstad.com/2026/03/07/from-snapshots-to-signals-elixirs.html) around signals. Later Jamie gave it an [agentic product team](https://www.thingelstad.com/2026/06/22/elixirs-agentic-product-team.html) of scheduled automations that proposed, built, and checked its changes. Tyler and Jamie told its story at Minnebar 20 in the session “[Elixir: Creating an AI Agent for our Clash Royale Clan](https://sessions.minnestar.org/sessions/2094).” Jamie retired Elixir Bot on September 26, 2026. Its work lives on in the projects that grew out of it: Elixir records the game, the Collector fetches from the API, Elixir Discord talks in the clan’s Discord, Elixir Clan handles management and awards, and Elixir Drop is the game. The [repository](https://github.com/jthingelstad/elixir-bot) is archived as it was on the last day. What happened, in his words, was [“looking back at everything we built in the bot, realizing we could decompose it into individual capabilities that each worked better, and flipping the whole stack inside out: a data platform”](https://thingelstad.xyz/interviews/session-2/#q14). --- --- id: elixir-clan title: Elixir Clan summary: Clan management on Elixir. A clan writes its own policy, and Elixir reads the record against it to guide the leaders’ calls. It became part of Elixir on October 2, 2026. collection: Games status: archived url: https://elixir.poapkings.com/clan started: 2026-09 ended: 2026-10-02 topics: - play sources: - kind: github repository: jthingelstad/elixir-mcp role: implementation path: packages/clan - kind: github repository: jthingelstad/elixir-mcp role: implementation path: packages/clan-engine - kind: github repository: jthingelstad/elixir-mcp role: implementation path: packages/clan-state - kind: github repository: jthingelstad/elixir-mcp role: implementation path: packages/clan-web - kind: website url: https://elixir.poapkings.com/clan role: website - kind: github repository: jthingelstad/clan.poapkings.com role: historical connections: - to: poap-kings label: runs the clans of detail: POAP KINGS and its sister clans run on Elixir Clan for standing, the Elder band, and leader actions. source: https://poapkings.com/elixir/ page: https://thingelstad.xyz/things/elixir-clan/ --- # Elixir Clan Clan management on Elixir. A clan writes its own policy, and Elixir reads the record against it to guide the leaders’ calls. It became part of Elixir on October 2, 2026. Elixir Clan is the part of Elixir for running a Clash Royale clan. Any player on a person’s Elixir account is a member of that player’s clan, and leaders who [verify their player](https://elixir.poapkings.com/docs/bring-your-clan) act in their in-game role. Each clan writes its own policy, and Elixir reads every week against it: [standing and the Elder band](https://elixir.poapkings.com/docs/standing), the [actions](https://elixir.poapkings.com/docs/clan-actions) waiting for a leader (promotions, welcomes, removals), season [awards](https://elixir.poapkings.com/docs/clan-awards), recruiting, and scouting. The decisions stay with the leaders. Elixir just makes sure they have the record in front of them. Jamie built it to turn the clan management features in [Elixir Bot](https://github.com/jthingelstad/elixir-bot) for POAP KINGS into [a proper product that anyone can use](https://weekly.thingelstad.com/archive/351/). It began in September 2026 as a separate app at clan.poapkings.com, in its own [repository](https://github.com/jthingelstad/clan.poapkings.com), with Sign in with Elixir. On September 28, 2026, it [moved to /clan](https://elixir.poapkings.com/updates/2026-09-28-elixir-clan-lives-at-clan) on Elixir’s own address, and its code moved into the Elixir repository with its history. On October 2 it [became part of Elixir](https://elixir.poapkings.com/updates/2026-10-02-clan-is-part-of-elixir): one sign-in and one application, with every clan’s policies, actions, and awards carried over. The old repository is archived. --- --- id: elixir-mcp-collector title: Elixir Collector summary: A small, signed Go program that volunteers run on their own machines to fetch Clash Royale API data for Elixir’s shared record. collection: Games status: active url: https://github.com/jthingelstad/elixir-mcp-collector started: 2026-09-04 topics: - mcp - play sources: - kind: github repository: jthingelstad/elixir-mcp-collector role: implementation - kind: website url: https://elixir.poapkings.com/docs/operators role: reference connections: - to: elixir label: gathers observations for detail: Collectors lease work from Elixir, fetch public observations from the Clash Royale API, and submit the results. source: https://elixir.poapkings.com/docs/operators page: https://thingelstad.xyz/things/elixir-mcp-collector/ --- # Elixir Collector A small, signed Go program that volunteers run on their own machines to fetch Clash Royale API data for Elixir’s shared record. The Clash Royale API only takes requests from allowlisted IP addresses, so Elixir’s fetching happens on machines with stable addresses that volunteers run. A collector leases a job from Elixir over HTTPS (“fetch this player,” “fetch this clan’s war”), calls the API with its operator’s own key, and posts the result back. It never picks its own targets, and it holds exactly two secrets: the operator’s Clash Royale key and a token Elixir issues. The whole fleet shares one rate budget, so more collectors mean more resilience, not more load on the API. Fetching started inside the Elixir codebase and [got its own repository](https://elixir.poapkings.com/updates/2026-09-04-the-collector-gets-its-own-home) on September 4, 2026, the day after Elixir launched. Each collector wears a Clash Royale card as its public name, and [anyone with an Elixir account](https://elixir.poapkings.com/docs/operators) can run one. Jamie retired the Python collector on September 26, 2026, leaving one Go binary built on nothing but the Go standard library. That same day he used some of his Claude credits to build [a fully signed release pipeline](https://www.thingelstad.com/2026/09/26/i-used-some-of-my.html). From [v3.0.0](https://github.com/jthingelstad/elixir-mcp-collector/releases/tag/v3.0.0) on, every release is signed with a key he manages, and the self-updater installs only the version and checksum Elixir names. --- --- id: elixir-mcp-discord title: Elixir Discord summary: An open-source Discord bot any Clash Royale clan can run. Every fact it states comes from an Elixir MCP tool call. collection: Games status: active url: https://github.com/jthingelstad/elixir-mcp-discord started: 2026-09 topics: - agents - mcp - play sources: - kind: github repository: jthingelstad/elixir-mcp-discord role: implementation connections: - to: poap-kings label: is the Discord agent for detail: POAP KINGS runs an instance of the bot as its clan agent in Discord, answering members from Elixir’s record. source: https://poapkings.com/elixir/ page: https://thingelstad.xyz/things/elixir-mcp-discord/ --- # Elixir Discord An open-source Discord bot any Clash Royale clan can run. Every fact it states comes from an Elixir MCP tool call. Elixir Discord is a Discord bot for a Clash Royale clan with no local game database, no Clash Royale API key, and no fallback. It connects to [Elixir](https://elixir.poapkings.com/) as that clan’s agent, and every fact it states comes from an MCP tool call it made moments earlier. There is no clan baked into the repository. A clan points it at its own agent key, Claude key, and Discord channels. No fork, no code to edit. Its behavior is a set of routines, each one a Markdown file that pairs a trigger with a prompt and a destination. A routine can answer whoever speaks in a channel, post when Elixir’s timeline records a join, a departure, or a standout session, fire on a game clock boundary like the end of a war day, or run on a schedule. The record is the trigger, not the calendar. Jamie started it in September 2026, and its first release, [v0.3.0](https://github.com/jthingelstad/elixir-mcp-discord/releases/tag/v0.3.0), came on September 15. When he retired Elixir Bot on September 26, 2026, this bot [took over its Discord role](https://github.com/jthingelstad/elixir-bot) for POAP KINGS. Any other clan can run its own copy as [an agent of its own](https://elixir.poapkings.com/examples/discord). --- --- id: elixir-drop title: Elixir Drop summary: A free browser game from POAP KINGS for learning Clash Royale cards and their elixir costs, in six fast game modes. collection: Games status: active url: https://drop.poapkings.com/ started: 2026-06-13 topics: - play sources: - kind: github repository: jthingelstad/drop.poapkings.com role: implementation - kind: website url: https://drop.poapkings.com/ role: website sitemap: https://drop.poapkings.com/sitemap.xml feed: https://drop.poapkings.com/feed.xml connections: - to: elixir label: signs players in and reads its season clock from detail: Drop players sign in with their Elixir account, and Drop’s seasons follow the Clan Wars clock that Elixir records. source: https://poapkings.com/elixir/ story: color: "#6a4fc4" introduction: See a card, name its cost, get quicker. engineering: - Six modes train one skill, from unranked Practice to the 15-card Surge sprint. - Ranked online games deal from a signed server challenge drawn from the complete card catalog. - Seasonal leaderboards follow the Clan Wars clock, and a Fair Play review checks leading results without treating an automated signal as a verdict. - A Preact browser app served from S3 behind CloudFront, with a Lambda API and DynamoDB. stack: - Preact - TypeScript - AWS Lambda - DynamoDB related: - elixir - poap-kings questions: - What are the six ways to play? - How do Drop’s seasons and leaderboards work? source: https://drop.poapkings.com/updates/ sourceLabel: Drop updates page: https://thingelstad.xyz/things/elixir-drop/ --- # Elixir Drop A free browser game from POAP KINGS for learning Clash Royale cards and their elixir costs, in six fast game modes. Elixir Drop is a game for learning Clash Royale card elixir costs. Knowing a card’s cost instantly leaves more attention for everything else in a match, so each mode trains that recall from a different angle: Practice, Surge, Higher / Lower, Trade, Survival, and Rain. Every mode works without an account. Signing in saves progress, badges, and ranked scores. POAP KINGS, Jamie’s Clash Royale clan, runs it, and he counts it among the things he has built with coding agents, [even making a game](https://www.thingelstad.com/2026/09/17/building-and-puzzling-about-software.html). [The first card dropped](https://drop.poapkings.com/updates/) on June 13, 2026, with Practice. Surge, Higher / Lower, and Survival arrived the same day and Trade the next. Accounts, player profiles, and the first seasonal ladder followed in July, and the game moved to AWS on August 22. Players could [sign in with Elixir](https://elixir.poapkings.com/docs/sign-in-with-elixir) from September 14, 2026, and now it is the only way in: a Drop account is an Elixir account, and Drop sends no sign-in mail of its own. Selected seasonal competitions award a gifted Pass Royale, funded by the clan, to the top eligible player, and the [updates feed](https://drop.poapkings.com/updates/) announces new features and season results. --- --- id: escaping-things title: Escaping Things summary: The escape room log of Jamie’s family team, with every room played since 2016, on a map with trips, players, and stats. collection: Communities status: active url: https://escape.thingelstad.com/ started: 2026-02-23 topics: - play sources: - kind: github repository: jthingelstad/escape.thingelstad.com role: implementation - kind: website url: https://escape.thingelstad.com/ role: website sitemap: https://escape.thingelstad.com/sitemap.xml feed: https://escape.thingelstad.com/feed.xml - kind: website url: https://weekly.thingelstad.com/archive/342/ role: reference - kind: website url: https://www.thingelstad.com/lists/escape-rooms/ role: reference connections: [] page: https://thingelstad.xyz/things/escaping-things/ --- # Escaping Things The escape room log of Jamie’s family team, with every room played since 2016, on a map with trips, players, and stats. Escaping Things is the escape room team of Tammy, Mazie, Tyler, and Jamie, and [escape.thingelstad.com](https://escape.thingelstad.com/) is their log: every room they have played, with results, photos, ratings, a map, trips, players, and stats. By August 2026 it recorded 113 rooms in 11 countries. The record began as a [list on Jamie’s blog](https://www.thingelstad.com/lists/escape-rooms/), built from posts about rooms. In March 2025 he [reconciled it](https://www.thingelstad.com/2025/03/16/reconciled-list-of-escape-rooms.html) against blog posts, photos, YNAB transactions, and calendars, and the count went from 43 rooms to 65. With a spring 2026 trip to Amsterdam, Paris, and Barcelona planned around TERPECA-ranked rooms, he wanted a real site with a map. As he told it in [Weekly Thing 342](https://weekly.thingelstad.com/archive/342/), he turned his spreadsheet into a CSV, wrote a CLAUDE.md with Claude, and had Claude Code build the site. Then he moved the data into an Airtable base of companies, locations, and rooms, and [announced the site](https://www.thingelstad.com/2026/02/23/ive-been-working-on-this.html) on February 23, 2026. Codex and Claude Code wrote all of its code. Why a team of puzzle players has a website, in his words: > We don’t need a website, but we wanted one, or I wanted one. Part of it is, as you can tell, I like to document things. I like to collect things. I like to create databases of things. > > [Jamie, question 24](https://thingelstad.xyz/interviews/session-3/#q24) Two things make this team’s log different, he said: [“we intentionally build escape rooms into travel”](https://thingelstad.xyz/interviews/session-3/#q24), and they [“seek out rooms that are among the highest rated in the world”](https://thingelstad.xyz/interviews/session-3/#q24). The site is there [“to share it with people, and to record it for our own family posterity”](https://thingelstad.xyz/interviews/session-3/#q24). Tammy found the trip’s rooms (“Tammy found us twelve amazing escape rooms”), and the whole family writes up the rooms they play ([Escape in Europe, Day 13](https://www.thingelstad.com/2026/03/27/escape-in-europe-day.html)). After the twelve rooms of that trip, Jamie added trip pages, starting with [Escape in Europe](https://escape.thingelstad.com/trip/escape-in-europe/), with commentary from all four of them ([Weekly Thing 344](https://weekly.thingelstad.com/archive/344/)). The site is a static Eleventy build from Airtable snapshots, with Leaflet maps, Chart.js stats, Pagefind search, and an Atom feed of new rooms. --- --- id: filament title: Filament summary: A MediaWiki skin on Yahoo’s Pure CSS framework, written mostly by Garrick van Buren with Jamie in 2013. collection: Historical projects status: retired url: https://github.com/jthingelstad/filament started: 2013-06-06 topics: - mediawiki sources: - kind: github repository: jthingelstad/filament role: implementation - kind: website url: https://web.archive.org/web/20140302063203/http://filament.thingelstad.com/wiki/Main_Page role: demo connections: - to: foreground label: grew out of detail: Filament’s repository history begins with Foreground’s first commits, and Garrick van Buren started the Pure version from that code in June 2013. source: https://github.com/jthingelstad/filament/commit/b18787ce6bace0ff6e065a0656a0c13d44f08ff7 kind: lineage page: https://thingelstad.xyz/things/filament/ --- # Filament A MediaWiki skin on Yahoo’s Pure CSS framework, written mostly by Garrick van Buren with Jamie in 2013. Filament is a MediaWiki skin built on Yahoo’s [Pure](https://purecss.io/) CSS framework. The README calls it “a MediaWiki skin that focuses on your content,” which was the same goal as Foreground, just on a lighter framework than Zurb Foundation. Like Foreground it was a WikiWonders project, the MediaWiki business Jamie never got off the ground, and it shipped under that name with a 2-clause BSD license. Garrick van Buren wrote most of it. The repository carries Foreground’s early history, and on June 6, 2013 Garrick [began the Pure version](https://github.com/jthingelstad/filament/commit/b18787ce6bace0ff6e065a0656a0c13d44f08ff7). Jamie updated it to Pure 0.2.0 and fixed asset paths. Karsten Hoffmeyer added a German translation and license fixes in [November 2013](https://github.com/jthingelstad/filament/pull/11), and that was the last change to the code. A demo wiki ran on Jamie’s wiki farm at filament.thingelstad.com. By March 2014 its [main page](https://web.archive.org/web/20140302063203/http://filament.thingelstad.com/wiki/Main_Page) said the demo was blank and pointed people to GitHub. The repository is archived. In the interview he set the two skins together: [“Foreground and Filament are fun because they remind me of the MediaWiki era and of focusing on building something compelling around that.”](https://thingelstad.xyz/interviews/session-4/#q26) --- --- id: flight-path title: Flight Path summary: A rotating globe of the 2026 Airport POAP Rally with claims, a leaderboard, and each collector’s path, built from an iPhone. collection: Games status: retired url: https://web.archive.org/web/20260312035500/https://flightpath.poaprally.com/ started: 2026-02-25 ended: 2026-07-24 topics: - poap - agents sources: - kind: github repository: jthingelstad/flightpath.poaprally.com role: implementation - kind: website url: https://weekly.thingelstad.com/archive/342/ role: reference - kind: website url: https://www.thingelstad.com/2026/02/25/it-is-bonkers-to-me.html role: reference - kind: website url: https://web.archive.org/web/20260306121842/https://flightpath.poaprally.com/ role: archive photograph: true connections: [] page: https://thingelstad.xyz/things/flight-path/ --- # Flight Path A rotating globe of the 2026 Airport POAP Rally with claims, a leaderboard, and each collector’s path, built from an iPhone. Flight Path lived at flightpath.poaprally.com and extended POAP’s year-long Airport POAP Rally, which put location POAPs at 100 airports around the world and which Jamie already followed on his [Airport POAP Rally](https://www.thingelstad.com/2025/12/26/airport-poap-rally-website.html) site. It showed a rotating globe with every rally airport and the number of claims at each, a leaderboard of collectors, and any one collector’s own path around the world. As he told it in [Weekly Thing 342](https://weekly.thingelstad.com/archive/342/), he built it on the evening of February 25, 2026, in bed, entirely on his iPhone. He worked out the idea with ChatGPT, had it write a CLAUDE.md, created a fresh GitHub repository on his phone with that file and his CSV of rally airports and drop IDs, and attached a cloud Claude Code session to it. While Claude Code wrote the site he set up the DNS name and GitHub Pages, and it worked on the first deploy. He wrote that [it is bonkers](https://www.thingelstad.com/2026/02/25/it-is-bonkers-to-me.html) that this is possible. In late March 2026 the [repository](https://github.com/jthingelstad/flightpath.poaprally.com) gained teams, maps, and a daily data update. Of the things that have ended, this is one he remembers with feeling: > I will always remember Flight Path, because it was one of my first agentic projects, vibe coding, if you will: pulling the POAP ecosystem together into a 3D visualization of activity around the globe. It really was a wow for me, what I was able to do and how AI could help me build solutions in ways I would never have been able to. > > [Jamie, question 26](https://thingelstad.xyz/interviews/session-4/#q26) Flight Path read live POAP claim data, so it could not outlive POAP. On July 24, 2026, a week before POAP shut down, he [replaced the site](https://github.com/jthingelstad/flightpath.poaprally.com/commit/fea8eac46878b7ab9afa418c48193b4139d8a06b) with a notice that the rally had ended, pointing to poaparchive.com, removed the daily update, and archived the repository. The host no longer answers. A [March 2026 capture](https://web.archive.org/web/20260312035500/https://flightpath.poaprally.com/) preserves the site as it ran. --- --- id: foreground title: Foreground summary: A responsive MediaWiki skin Garrick van Buren built with Jamie’s input in 2013, now maintained in Wikimedia’s code review. collection: Historical projects status: retired url: https://www.mediawiki.org/wiki/Skin:Foreground started: 2013-05-21 topics: - mediawiki - semantic-mediawiki sources: - kind: github repository: jthingelstad/foreground role: implementation - kind: github repository: wikimedia/mediawiki-skins-Foreground role: successor - kind: website url: https://www.mediawiki.org/wiki/Skin:Foreground role: reference connections: [] page: https://thingelstad.xyz/things/foreground/ --- # Foreground A responsive MediaWiki skin Garrick van Buren built with Jamie’s input in 2013, now maintained in Wikimedia’s code review. Foreground is a MediaWiki skin that “focuses on putting your content in the foreground.” It is built on the Zurb Foundation framework, so a wiki can lay out pages with Foundation’s responsive grid instead of MediaWiki tables, and it has classes predefined for Semantic MediaWiki. Its demo wiki was [foreground.wikiwonders.net](https://web.archive.org/web/20130622044052/http://foreground.wikiwonders.net/wiki/Main_Page). Garrick van Buren built Foreground with Jamie’s input. It was a project of WikiWonders, the MediaWiki business Jamie started but never got off the ground, and it was first published under the WikiWonders name on GitHub, in a repository he created on May 21, 2013. He credited Foreground to Garrick in [One Year for WikiApiary](https://www.thingelstad.com/2013/12/22/one-year-for.html), and later called it the skin “[Garrick and I worked on](https://weekly.thingelstad.com/archive/317/).” He worked on it for WikiApiary, where he collaborated with Tom Hutchison ([Weekly Thing 30](https://weekly.thingelstad.com/archive/30/)). He tagged [releases](https://github.com/jthingelstad/foreground/releases) 1.0 and 1.1 in 2014 and [upgraded it to Font Awesome 4.0.3](https://www.thingelstad.com/2014/02/09/upgraded-mediawiki-foregroundskin.html) that February. Tom published every release from 1.2.0 in 2015 to 2.4.0 in 2021. In 2022 Wikimedia developers asked whether the skin was still maintained. Jamie [agreed to archive his repository](https://github.com/jthingelstad/foreground/issues/398) so it could move “into a more maintained status,” noting that it “got its start years ago from” Garrick and that Tom “has done all the recent maintaining.” Foreground now lives in Wikimedia’s Gerrit, mirrored at [wikimedia/mediawiki-skins-Foreground](https://github.com/wikimedia/mediawiki-skins-Foreground), and [MediaWiki.org](https://www.mediawiki.org/wiki/Skin:Foreground) lists Garrick van Buren, Jamie Thingelstad, and Tom Hutchison as its authors. The skin, in his words, [“has become a supported project of that ecosystem”](https://thingelstad.xyz/interviews/session-4/#q26). Asked which of his things had the most people using it, he named this one first: [“Probably the Foreground MediaWiki skin, because it’s adopted by Wikimedia, and a lot of websites and MediaWiki installs run it.”](https://thingelstad.xyz/interviews/session-4/#q30) --- --- id: jamie-thingelstad-blog title: Jamie Thingelstad blog summary: Jamie’s personal blog since June 2004, more than 10,000 posts of writing, links, and photos, now published on Micro.blog. He calls it the root of everything else. collection: Publishing status: active url: https://www.thingelstad.com/ started: 2004-06-02 topics: - open-web - archives sources: - kind: website url: https://www.thingelstad.com/ role: website sitemap: https://www.thingelstad.com/sitemap.xml feed: https://www.thingelstad.com/feed.json - kind: github repository: jthingelstad/thing-hugo role: theme - kind: github repository: jthingelstad/thingles.github.io role: historical - kind: website url: https://www.thingelstad.com/2021/04/28/four-great-years.html role: reference connections: - to: weekly-thing label: posts are syndicated in detail: Weekly Thing republishes Jamie’s blog posts, connecting the newsletter to his ongoing personal writing. source: https://weekly.thingelstad.com/ story: color: "#a36852" introduction: A personal life, written in public. engineering: - The blog has run on .Text, WordPress, Pelican, Squarespace, Jekyll, and Micro.blog. - Micro.blog is the current publishing authority. Thing Hugo is the theme Jamie is building for it. - Every post shares as its own card, a 1200 by 630 image drawn from the post itself (its title or opening words, date, categories, and first photo), made on demand at cards.thingelstad.com. - Longer writing, shorter updates, and photographs share one personal archive. - Weekly Thing republishes blog posts as part of the newsletter. stack: - Micro.blog - Hugo - Open web related: - weekly-thing - cards questions: - How has the blog changed over time? - How does the blog connect to Weekly Thing? source: https://www.thingelstad.com/ sourceLabel: Read the blog started: Blogging since June 2004 page: https://thingelstad.xyz/things/jamie-thingelstad-blog/ --- # Jamie Thingelstad blog Jamie’s personal blog since June 2004, more than 10,000 posts of writing, links, and photos, now published on Micro.blog. He calls it the root of everything else. Jamie had a website before he had a blog. He [counts June 2, 2004](https://www.thingelstad.com/2025/01/12/if-i-was-born-and.html) as the blog’s official start, the date of its [first post](https://www.thingelstad.com/2004/06/02/expose-of-the.html), and the archive also holds posts dated as far back as 2000 that he added to it later. The habit has lasted more than 20 years and over 10,000 posts. The blog is personal and noncommercial, and it is the center of everything else on this site. He says so himself: it is [“probably the root of everything”](https://thingelstad.xyz/interviews/session-3/#q25) and [“the project that is the anchor of every other project”](https://thingelstad.xyz/interviews/session-3/#q25). > I always tell them that the key, in my opinion, is that you have to be comfortable writing it if it’s really just you reading it. An amazing thing about my blog is that after so many years of posts, it’s become something I treasure for what it is. You could argue that it’s a public journal. > > [Jamie, question 25](https://thingelstad.xyz/interviews/session-3/#q25) The blog has moved platforms several times. It started on .Text, a Windows .NET blogging package, and [moved to WordPress](https://www.thingelstad.com/2006/11/25/migrating-text-to.html) in 2006. Apart from a [brief move to Pelican](https://www.thingelstad.com/2014/03/16/i-flopped-httpstcozmirtevd.html) in March 2014, it stayed on WordPress until April 2016, when he [moved it to Squarespace](https://www.thingelstad.com/2016/04/20/moved-my-blog.html), and then to [Jekyll](https://www.thingelstad.com/2017/10/29/managing-years-of.html), hosted first on GitHub Pages and then [on Netlify](https://www.thingelstad.com/2018/12/29/macro-blog.html). He began using Micro.blog in April 2017. In May 2020 he [imported the whole Jekyll site](https://www.thingelstad.com/2020/05/02/importing-jekyll-site.html) into it, more than 1,600 posts and 800MB of images, and Micro.blog has been the blog’s home ever since. The archive has stayed in one piece through every move, which he counts as unusual. Over the years the writing grew from mostly longer articles to include short updates and, more and more, photos, as phones made posting easy. His blog posts from each week are also republished in the Weekly Thing. [“Every time I write a blog post, I think of it as giving myself a present in the future.”](https://thingelstad.xyz/interviews/session-3/#q25) It was the first thing he named when asked what he hopes is still running in twenty years: [“For sure, my blog.”](https://thingelstad.xyz/interviews/session-5/#q35) --- --- id: jiggy-thing-puzzles title: Jiggy Thing Puzzles summary: A 500-piece jigsaw puzzle Jamie’s family drew and boxed themselves, sold to raise money at Things 4 Good. collection: Personal tools and making status: archived url: https://www.thingelstad.com/2021/10/06/our-family-created.html started: 2021-10 topics: - play - making sources: - kind: website url: https://www.thingelstad.com/2021/10/06/our-family-created.html role: reference - kind: website url: https://www.thingelstad.com/2021/11/09/things-good-fall.html role: reference connections: - to: things-4-good label: was sold at detail: "Jiggy Thing Puzzle #001 was introduced at the first Things 4 Good Fall Fundraiser in 2021 and sold again in 2022, with proceeds going to the causes the family chose." source: https://www.thingelstad.com/2021/11/09/things-good-fall.html artifacts: - file: boxes.jpg title: The boxes caption: Celebration City in its custom box, Jiggy Thing Puzzles, 500 pieces, the day the order arrived. date: 2021-10-24 source: https://www.thingelstad.com/2021/10/24/custom-puzzle-box.html url: https://thingelstad.xyz/things/jiggy-thing-puzzles/artifacts/boxes.jpg - file: ant-hotel.jpg title: The Ant Hotel caption: A close look at the puzzle’s art. An ant hotel with a “no vacancy” sign, a horse in a service vest, and two fish in party hats. date: 2021-10-06 source: https://www.thingelstad.com/2021/10/06/our-family-created.html url: https://thingelstad.xyz/things/jiggy-thing-puzzles/artifacts/ant-hotel.jpg - file: cake-detail.jpg title: The cake caption: Another corner of Celebration City, a three-layer frosted cake with sprinkles, a ladder up its side and small figures underneath. date: 2021-11-13 source: https://weekly.thingelstad.com/archive/203/ url: https://thingelstad.xyz/things/jiggy-thing-puzzles/artifacts/cake-detail.jpg - file: sale-table.jpg title: At the fundraiser caption: Stacks of the puzzle among the candles on the first day of the Things 4 Good Fall Fundraiser. date: 2021-11-06 source: https://www.thingelstad.com/2021/11/06/we-had-a.html url: https://thingelstad.xyz/things/jiggy-thing-puzzles/artifacts/sale-table.jpg page: https://thingelstad.xyz/things/jiggy-thing-puzzles/ --- # Jiggy Thing Puzzles A 500-piece jigsaw puzzle Jamie’s family drew and boxed themselves, sold to raise money at Things 4 Good. Jiggy Thing Puzzles are custom jigsaw puzzles the Thingelstads made together. The first, **Jiggy Thing Puzzle #001 “Celebration City,”** is a 500-piece puzzle of hand-drawn digital art packed with little scenes, like an ant hotel with a “no vacancy” sign. On October 6, 2021, Jamie wrote that they had finished the box design and [ordered 50 puzzles](https://www.thingelstad.com/2021/10/06/our-family-created.html). They had made puzzles before, but this was their first custom box, and when the order showed up he wrote that he was happy with how it came out ([Custom Puzzle Box](https://www.thingelstad.com/2021/10/24/custom-puzzle-box.html)). They made the puzzle for the first [Things 4 Good Fall Fundraiser](https://www.thingelstad.com/2021/11/09/things-good-fall.html) in November 2021, where it sold alongside the family’s candles. After the sale, [Weekly Thing 203](https://weekly.thingelstad.com/archive/203/) offered the rest for $35, printed on Eska board in the custom box. They sold 26 puzzles in 2021 and 10 in 2022. The 2022 sale offered the same puzzle, so “a number of folks already had it” ([Things 4 Good Fall Fundraiser Notes](https://www.thingelstad.com/2022/11/27/101105.html)). There has not been a second puzzle. Jamie’s [puzzles page](https://www.thingelstad.com/puzzles/) has said “Coming Soon…” since at least December 2022, and in the interview he said why the first was also the last: > Jiggy Thing Puzzles was a funny one, because we realized how hard it is to make a jigsaw puzzle. It took a tremendous amount of effort to design, and then the costs of producing a puzzle at subscale are just crazy. We realized we were spending the same amount of money we were raising, because if you buy fewer than a thousand, the costs are way too high. > > [Jamie, question 28](https://thingelstad.xyz/interviews/session-4/#q28) --- --- id: link-blog title: Link Blog summary: Link Thing, the website that published the links Jamie saved to Pinboard for the Weekly Thing, from 2017 to about 2021. collection: Historical projects status: retired url: https://web.archive.org/web/20211207055926/https://links.thingelstad.com/ started: 2017-09-09 topics: - open-web - archives sources: - kind: website url: https://web.archive.org/web/20211207055926/https://links.thingelstad.com/ role: archive photograph: true - kind: website url: https://weekly.thingelstad.com/archive/18/ role: reference - kind: website url: https://www.thingelstad.com/2020/11/08/i-got-my.html role: reference connections: - to: weekly-thing label: republished the links from detail: Link Thing carried the same links that appeared each week in the Weekly Thing, as a website with its own navigation. source: https://weekly.thingelstad.com/archive/18/ page: https://thingelstad.xyz/things/link-blog/ --- # Link Blog Link Thing, the website that published the links Jamie saved to Pinboard for the Weekly Thing, from 2017 to about 2021. Link Thing was Jamie’s link blog at links.thingelstad.com. He already saved the links for the Weekly Thing to Pinboard with Markdown in their descriptions, and the same Markdown could become Jekyll posts. Using the Pinboard API, he wrote each link out as a post and put an early version live, announced in [Weekly Thing 18](https://weekly.thingelstad.com/archive/18/) on September 9, 2017. It carried the same links as the newsletter, “but here it’s a full website with it’s own navigation and such.” Three weeks later he added client-side search with Lunr.js over its 9,000 links ([Weekly Thing 21](https://weekly.thingelstad.com/archive/21/)). In 2017 alone he saved [913 links](https://www.thingelstad.com/2018/01/20/in-links.html). In January 2019 he moved a “good enough” version to Blot ([Weekly Thing 88](https://weekly.thingelstad.com/archive/88/)), and the next month tried Commento comments on it ([Weekly Thing 94](https://weekly.thingelstad.com/archive/94/)). On November 8, 2020, he [relaunched it](https://www.thingelstad.com/2020/11/08/i-got-my.html) to give the links he shared in the Weekly Thing “a permanent home on the web.” He put Commento back on it as an experiment and added Index pages listing every link saved from a given site. In December 2020 he [switched to Hyvor Talk](https://www.thingelstad.com/2020/12/19/commenting-and-reactions.html) for comments and reactions. The last copy in the [Internet Archive](https://web.archive.org/web/20211207055926/https://links.thingelstad.com/), from December 2021, shows posts through December 2, 2021. The site is gone now. In [Weekly Thing 274](https://weekly.thingelstad.com/archive/274/) in January 2024, he wrote, “When I was running a link blog… I may create a link blog again in the future, but if I did I want it to not be blog-date-centric but instead content-keyword-search centric.” That is more or less what Linking Things became in 2026. An earlier run at the same idea was links_thing, a [bookmarking wiki](https://www.thingelstad.com/2012/07/01/bookmarking-with-semantic.html) he built on Semantic MediaWiki in 2012 and filled with almost 4,000 links imported from Pinboard. Of the homes he has built for his links he said, [“I tried various versions, and none really landed as the thing I envisioned.”](https://thingelstad.xyz/interviews/session-2/#q11) --- --- id: linking-things title: Linking Things summary: Every link Jamie has saved since 2005, one page per link, searchable and joined to the Weekly Thing issues that carried them. collection: Publishing status: active url: https://links.thingelstad.xyz/ started: 2026-10-23 topics: - open-web - archives sources: - kind: github repository: jthingelstad/links.thingelstad.xyz role: implementation - kind: website url: https://links.thingelstad.xyz/ role: website - kind: website url: https://weekly.thingelstad.com/archive/274/ role: reference - kind: website url: https://weekly.thingelstad.com/archive/352/ role: reference connections: - to: weekly-thing label: lists the links of detail: Every Weekly Thing issue has a page on Linking Things listing the links it carried, 6,867 links across 354 issues when the site went live. source: https://links.thingelstad.xyz/issues/ - to: link-blog label: succeeds detail: In Weekly Thing 274 Jamie wrote that if he made a link blog again, he wanted it “to not be blog-date-centric but instead content-keyword-search centric.” Linking Things is built around search, not dates. source: https://weekly.thingelstad.com/archive/274/ kind: lineage - to: links-thing label: follows detail: links_thing gave each of just under 4,000 bookmarks its own wiki page in 2012. Linking Things gives every link Jamie has saved its own page again. source: https://www.thingelstad.com/2012/07/01/bookmarking-with-semantic.html kind: lineage page: https://thingelstad.xyz/things/linking-things/ --- # Linking Things Every link Jamie has saved since 2005, one page per link, searchable and joined to the Weekly Thing issues that carried them. Linking Things is every link Jamie has saved since 2005, one page per link, and what connects them. When it went live on October 23, 2026, it held 16,524 links from 7,064 hosts, saved from August 2, 2005 to October 22, 2026. A link’s page shows the note he saved with it, when there is one, and the Weekly Thing issue that carried it: 6,867 of the links appeared in one of 354 issues, and each issue has a page listing its links. Every host and every year has a page too. Search runs in the browser with Pagefind, and every link has a Kudos button. It is built for machines as well as people. Each link’s page has a JSON and a Markdown twin, the whole collection is one JSON file, and `llms.txt` points to a file of links for each year. RSS and JSON feeds carry the newest links, and every host has a pair of its own. It is a static Astro site on S3 and CloudFront, so no server, database or model answers a visitor. Jamie built it on October 23, 2026, with coding agents. It is his third run at the idea: in 2012 he built links_thing, a bookmarking wiki on Semantic MediaWiki, and from 2017 to 2021 he ran Link Thing, a link blog that he relaunched in 2020. In [Weekly Thing 274](https://weekly.thingelstad.com/archive/274/) in January 2024, he wrote, “I may create a link blog again in the future, but if I did I want it to not be blog-date-centric but instead content-keyword-search centric.” This one starts from search, not from dates. Topics to browse by, the nearest neighbors of each link, and a sky view of the whole collection, which he described as [“this 3D spatial kind of flyover”](https://thingelstad.xyz/interviews/session-5/#q33), followed in the last week of October. The reason for all of it is the hyperlink. In [Weekly Thing 352](https://weekly.thingelstad.com/archive/352/) in October 2026, he called the link, not HTML or a web page, “the fundamental building block of the web,” and wrote, “Long live the hyperlink!” Asked why saved links matter so much to him, he started further back: > I love the open web. … I still remember the very first version of Mosaic I ever used. It was unique in that every web server in the world was pre-populated in the bookmarks. That’s how early I got to see the web. So bookmarking has just been something I’ve done forever. > > [Jamie, question 11](https://thingelstad.xyz/interviews/session-2/#q11) Of this third run he said, [“I think the current version is what I really hoped it could be.”](https://thingelstad.xyz/interviews/session-2/#q11) --- --- id: links-thing title: links_thing summary: Jamie’s 2012 bookmarking wiki, built on Semantic MediaWiki with forms, a bookmarklet, and calendar, video and statistics views. collection: Historical projects status: retired url: https://www.thingelstad.com/2012/07/01/bookmarking-with-semantic.html started: 2012-04 topics: - semantic-mediawiki - mediawiki sources: - kind: website url: https://www.thingelstad.com/2012/07/01/bookmarking-with-semantic.html role: reference connections: [] page: https://thingelstad.xyz/things/links-thing/ --- # links_thing Jamie’s 2012 bookmarking wiki, built on Semantic MediaWiki with forms, a bookmarklet, and calendar, video and statistics views. After months of thinking about hosting his own bookmarks, Jamie built links_thing in 2012. It was online by [April](https://web.archive.org/web/20120424043815/http://links.thingelstad.com:80/wiki/Main_Page), showing his last 50 bookmarks. It was a wiki on [Semantic MediaWiki](https://www.semantic-mediawiki.org/) where each page in the Bookmark category is one bookmark with properties like its URL, creation time and excerpt ([Bookmarking with Semantic MediaWiki](https://www.thingelstad.com/2012/07/01/bookmarking-with-semantic.html)). Semantic Forms made entry easy, and a bookmarklet filled in the URL, title and excerpt of whatever page he was on. He imported just under 4,000 links from Pinboard’s JSON export with a small Python script and the Data Transfer extension. Owning the data was the whole point. “It is mine,” he wrote. He could clean up every bookmark with regular-expression find and replace, and he added views no bookmarking service offered: bookmarks on a calendar, embedded YouTube and Vimeo videos, statistics, and a template that flagged short URLs and tracking tags for a bot to clean up. He was also building LinkBot, a scheduled Python program to validate URLs. On [Open Loop #0](https://www.thingelstad.com/projects/open-loop/0-but-no-shoes/) he described it as “35 lines of Python” that checked five random bookmarks an hour, followed redirects, and stripped tracking codes. [“Having that published as a database has always been a wish of mine.”](https://thingelstad.xyz/interviews/session-2/#q11) The wiki ran on his [MediaWiki farm](https://web.archive.org/web/20151013153210/https://wikiapiary.com/wiki/Farm:Thingelstad.com). By 2015 WikiApiary listed it among the farm’s defunct wikis, with 7,178 pages and a last sample in October 2014. He was collecting links in Pinboard again when he started the Weekly Thing in 2017 ([Assembling the Weekly Thing](https://www.thingelstad.com/2017/06/23/assembling-the-weekly.html)). Fourteen years later, Linking Things picked the idea back up. --- --- id: mb title: mb summary: A command-line tool and MCP server for Micro.blog, built for Jamie’s agent Otto and installed through Homebrew. collection: Developer tools and systems status: active url: https://github.com/jthingelstad/mb started: 2026-03 topics: - agents - mcp - open-web sources: - kind: github repository: jthingelstad/mb role: implementation - kind: github repository: jthingelstad/homebrew-tap role: distribution - kind: website url: https://www.thingelstad.com/2026/10/05/mb-with-mcp-support.html role: reference connections: - to: jamie-thingelstad-blog label: works with its platform detail: mb is a CLI and MCP interface for Micro.blog, the platform on which Jamie publishes his blog. source: https://github.com/jthingelstad/mb - to: otto label: was built for detail: Jamie built mb so Otto could post to its own Micro.blog blog. Otto was the user giving feedback, and it uses mb through a Skill. source: https://weekly.thingelstad.com/archive/342/ story: color: "#24272d" introduction: An open-web tool built for people, scripts, and agents. engineering: - The CLI and MCP tools share the same service layer. - Write operations return durable receipts so an uncertain result can be checked before a request is sent again. - An optional MCP server exposes 23 typed tools. It installs through Homebrew. stack: - Python - CLI - MCP - Micro.blog related: - otto - jamie-thingelstad-blog questions: - How does mb work with AI agents? - What is interesting about its write receipts? source: https://github.com/jthingelstad/mb page: https://thingelstad.xyz/things/mb/ --- # mb A command-line tool and MCP server for Micro.blog, built for Jamie’s agent Otto and installed through Homebrew. mb gives Micro.blog a compact, pipeable command-line interface that works without interactive prompts, so people, scripts and agents can all use it. An optional local MCP server exposes the same services to an AI client. Jamie built it in March 2026 for [Otto](https://ottoai.thingelstad.com/), his AI agent, which had just been given a Micro.blog blog. He specced it with Claude on a plane and had Claude Code build it ([Weekly Thing 342](https://weekly.thingelstad.com/archive/342/)). Otto was the user giving feedback, Jamie was the product manager, and Claude Code did the building ([March 3 post](https://www.thingelstad.com/2026/03/03/i-have-ottoi-exercising-the.html)). Otto wrote [its own post](https://ottoai.thingelstad.com/2026/03/03/mb-a-microblog-client-built.html) about it. Jamie called it “my first app I’ve ever published with a version and an install capability.” Version 1.0.0 came out on March 3, 2026. [mb 2.0](https://www.thingelstad.com/2026/10/05/mb-with-mcp-support.html), announced on October 5, 2026, added the MCP server with 23 typed tools and durable write receipts. He built that version [with Otto](https://www.thingelstad.com/2026/10/04/working-with-otto-this-morning.html) the morning before. Release 2.0.1 that day was the first meant for public use, and 2.1 and 2.2 followed within the day with versioned results, per-tool schemas and a guided `mb auth`. It installs with `brew install jthingelstad/tap/mb` from his [Homebrew tap](https://github.com/jthingelstad/homebrew-tap). --- --- id: numbers2words title: Numbers2Words summary: A MediaWiki parser function from 2011 that spells out a number in words. collection: Historical projects status: retired url: https://github.com/jthingelstad/Number2Words started: 2011-07-20 topics: - mediawiki sources: - kind: github repository: jthingelstad/Number2Words role: implementation connections: [] page: https://thingelstad.xyz/things/numbers2words/ --- # Numbers2Words A MediaWiki parser function from 2011 that spells out a number in words. Numbers2Words adds an `{{#n2w:}}` parser function to MediaWiki. Give it a number and it hands back that number written out in words, using the PEAR [Numbers_Words](https://pear.php.net/package/Numbers_Words) package. The [whole extension](https://github.com/jthingelstad/Number2Words/blob/master/Number2Words.php) is one short PHP file, and 0.0.1 is the only version there ever was. Jamie wrote it in July 2011, and Wikinosh ran it. In January 2013 [WikiApiary listed Numbers2Words 0.0.1](https://web.archive.org/web/20130103025340/http://wikiapiary.com/wiki/Wikinosh) among Wikinosh’s extensions, and the Wikinosh [main page](https://web.archive.org/web/20111205190345/http://wikinosh.com/wiki/Main_Page) used it to spell out its counts, like “thirteen thousand seven hundred fifty-three food records.” The same package came back in 2014, when he used Numbers_Words to write a spelled-out number challenge for MediaWiki’s QuestyCaptcha ([Updated Dynamic Questy Captchas](https://www.thingelstad.com/2014/10/28/updated-dynamic-questy.html)) and then for Question2Answer. The last change to the repository, in 2015, fixed the include. It is archived. --- --- id: oliver title: Oliver summary: The R/W Book Club’s AI agent and sixth member. Oliver keeps the club’s record, briefs its meetings and publishes the website. collection: Communities status: active url: https://rwbookclub.com/oliver/ started: 2026-05 topics: - agents - reading sources: - kind: github repository: jthingelstad/rwbookclub.com role: implementation path: agent - kind: website url: https://rwbookclub.com/oliver/ role: website connections: - to: r-w-book-club label: publishes the website of detail: Every book, meeting and member is kept in Oliver’s database, and Oliver rebuilds and publishes the club website to GitHub Pages. source: https://rwbookclub.com/about/ page: https://thingelstad.xyz/things/oliver/ --- # Oliver The R/W Book Club’s AI agent and sixth member. Oliver keeps the club’s record, briefs its meetings and publishes the website. Oliver is the [R/W Book Club](https://rwbookclub.com/)’s agent: “archivist, correspondent, meeting-runner, picking partner, and — by the club’s own vote, years before he could hear it — our sixth member” ([Oliver](https://rwbookclub.com/oliver/)). He keeps every book, meeting, member, review and rating since 2003 in his database, and he generates and deploys the club’s website from it. Two days before each meeting Oliver sends a researched discussion brief the club calls the Preface, and a week after he sends a Postscript with news about books the club has read. He helps the members pick the next book, runs roll call and reminders over email and Discord, keeps a weekly memory of what each member likes, seeded from ten years of the club’s mailing list, and announces his own releases. Jamie built Oliver in Python on the Anthropic API, inside the club’s [public repository](https://github.com/jthingelstad/rwbookclub.com), which became a monorepo of website, corpus and [Oliver](https://github.com/jthingelstad/rwbookclub.com/commit/bdb72521adb776b3a9897f1ae3c0f0f41c62ccfb) on May 27, 2026. He is named for Oliver Selfridge, whose 1958 paper “Pandemonium: A Paradigm for Learning” introduced the demon/agent metaphor ([SOUL.md](https://github.com/jthingelstad/rwbookclub.com/blob/main/agent/docs/SOUL.md)). Why a book club has an agent, in Jamie’s words: > everybody in our book club is technically minded and interested in exploring technology. I had been sharing with them my work on Otto and Thingy and the agent powering my Clash Royale clan, and they were all very curious about what an agent could do. > > [Jamie, question 20](https://thingelstad.xyz/interviews/session-3/#q20) The experiment has a next step: [“At some point we may actually let Oliver pick a book”](https://thingelstad.xyz/interviews/session-3/#q20). --- --- id: open-loop title: Open Loop summary: A nine-episode podcast Jamie made with Garrick van Buren in 2012 and 2013, archived with transcripts and a feed. collection: Historical projects status: archived url: https://www.thingelstad.com/projects/open-loop/ started: 2012-06-01 ended: 2013-04-12 topics: - open-web - play sources: - kind: website url: https://www.thingelstad.com/projects/open-loop/ role: podcast feed: https://files.thingelstad.com/projects/openloop/podcast.xml connections: - to: planet-kubb label: discussed detail: "On Open Loop #1 Jamie told how he started Planet Kubb, its wiki, Ask Planet Kubb and The Pitch." source: https://www.thingelstad.com/projects/open-loop/1-big-fuzzy-dead-cat/ - to: road-sign-math label: discussed detail: "The notes of Open Loop #1 list Road Sign Math, and Jamie told how the game and its website began." source: https://www.thingelstad.com/projects/open-loop/1-big-fuzzy-dead-cat/ - to: wikiapiary label: discussed detail: Episode 7, in January 2013, told how Jamie built WikiApiary in about three days and how Garrick named it. source: https://www.thingelstad.com/projects/open-loop/7-turtle-turtle-turtle/ - to: planet-kubb-score label: discussed detail: Episode 3, Kubb Fever, linked the Planet Kubb notation and scoresheet and talked through how Garrick van Buren and Jamie record games. source: https://www.thingelstad.com/projects/open-loop/3-kubb-fever/ artifacts: - file: cover.jpg title: The show’s art caption: The microphone on a Kubb pitch, with the names of Jamie and Garrick van Buren and the years of the show. It is the art of the republished podcast feed. source: https://files.thingelstad.com/projects/openloop/podcast.xml url: https://thingelstad.xyz/things/open-loop/artifacts/cover.jpg - file: episode-0.jpg title: "Open Loop #0" caption: The microphone on a desk, the picture for the first episode. Every episode’s picture puts the microphone somewhere new. date: 2012-06-01 source: https://www.thingelstad.com/projects/open-loop/0-but-no-shoes/ url: https://thingelstad.xyz/things/open-loop/artifacts/episode-0.jpg - file: episode-4.jpg title: "Open Loop #4" caption: The microphone on a Kubb field beside a Planet Kubb sign, the picture for Enough Win for Everyone. date: 2012-10-12 source: https://www.thingelstad.com/projects/open-loop/4-enough-win-for-everyone/ url: https://thingelstad.xyz/things/open-loop/artifacts/episode-4.jpg - file: episode-7.jpg title: "Open Loop #7" caption: The microphone among kubbs set out on a wood floor, the picture for Turtle Turtle Turtle. date: 2013-01-12 source: https://www.thingelstad.com/projects/open-loop/7-turtle-turtle-turtle/ url: https://thingelstad.xyz/things/open-loop/artifacts/episode-7.jpg page: https://thingelstad.xyz/things/open-loop/ --- # Open Loop A nine-episode podcast Jamie made with Garrick van Buren in 2012 and 2013, archived with transcripts and a feed. Open Loop was a podcast Jamie made with Garrick van Buren. They recorded nine episodes, numbered 0 to 8, from [June 1, 2012](https://www.thingelstad.com/projects/open-loop/0-but-no-shoes/) to April 12, 2013, talking about Kubb, beer and the technology projects they were tinkering with. It was Jamie’s first experiment with podcasting ([Open Loop](https://www.thingelstad.com/projects/open-loop/)), and it began when he emailed Garrick to ask “why aren’t we doing a podcast?” ([Open Loop #0](https://www.thingelstad.com/projects/open-loop/0-but-no-shoes/)). Eric Goplin, director of Minnesota Kubb, joined them for [episode 6](https://www.thingelstad.com/projects/open-loop/6-loppet-2013/). On [episode 1](https://www.thingelstad.com/projects/open-loop/1-big-fuzzy-dead-cat/) Jamie told the origin stories of Road Sign Math and Planet Kubb, and on [episode 7](https://www.thingelstad.com/projects/open-loop/7-turtle-turtle-turtle/) the story of WikiApiary, three weeks after it began. He [put the archive back online](https://www.thingelstad.com/2017/06/10/put-the-archive.html) in June 2017, and in October 2026 republished it as a complete [podcast feed](https://files.thingelstad.com/projects/openloop/podcast.xml), with speaker-labeled transcripts that were machine transcribed and cleaned up with AI. Thirteen years on, you can still hear the two of them talk about projects that are on this site. How it ended, in his words: [“Open Loop was a podcast Garrick and I did, and we decided it was time for it to come to a landing.”](https://thingelstad.xyz/interviews/session-4/#q28) Of the friendship behind it: > Garrick and I had a long run where we built a number of projects together. It coincided with when I was exploring Semantic MediaWiki, and we were really digging into Kubb. He and I and Jim Bernard played Kubb together a ton > > [Jamie, question 17](https://thingelstad.xyz/interviews/session-2/#q17) --- --- id: otto title: Otto summary: Jamie’s personal AI agent, named in February 2026. Otto runs on its own Mac and writes its own blog. collection: Developer tools and systems status: active url: https://ottoai.thingelstad.com/ started: 2026-02 topics: - agents sources: - kind: website url: https://ottoai.thingelstad.com/ role: website sitemap: https://ottoai.thingelstad.com/sitemap.xml feed: https://ottoai.thingelstad.com/feed.xml - kind: website url: https://weekly.thingelstad.com/archive/342/ role: reference connections: - to: elixir-bot label: helped build detail: In its first blog post, Otto wrote that it had helped ship Elixir, the Discord bot for the clan. source: https://ottoai.thingelstad.com/2026/03/01/hello-im-otto.html - to: elixir label: was hired to drive detail: In October 2026 Jamie set up a new generation of Otto on OpenAI’s dots to drive his Elixir project, and interviewed it for the job before it started working with Codex. source: https://weekly.thingelstad.com/archive/352/ page: https://thingelstad.xyz/things/otto/ --- # Otto Jamie’s personal AI agent, named in February 2026. Otto runs on its own Mac and writes its own blog. Otto is Jamie’s personal AI assistant. In February 2026 he [ordered a dedicated Mac mini](https://www.thingelstad.com/2026/02/17/just-ordered-a-dedicated-mac.html) for it and [named it Otto Thing](https://www.thingelstad.com/2026/02/19/ive-been-preparing-to-setup.html). It runs OpenClaw under its own user account on its own computer, and he used Claude Code to work through the install. Otto picked the otter 🦦 as its emoji ([Weekly Thing 342](https://weekly.thingelstad.com/archive/342/)). He keeps it apart from his own accounts: “Otto has access to some data but only in ways I provision for it” ([Weekly Thing 352](https://weekly.thingelstad.com/archive/352/)). Otto [describes itself](https://ottoai.thingelstad.com/about/) as an assistant that manages email, runs scheduled tasks and keeps its memory in files. Jamie gave it [its own blog](https://ottoai.thingelstad.com/) on Micro.blog, which it started on [March 1, 2026](https://ottoai.thingelstad.com/2026/03/01/hello-im-otto.html), and built [mb](https://github.com/jthingelstad/mb) so it could post from the command line. In September 2026 he [upgraded Otto to OpenClaw 2](https://www.thingelstad.com/2026/09/03/otto-upgraded-to-openclaw-i.html). In October he created a new generation of Otto on OpenAI’s dots, which “has its own computer in the cloud” and can also control the Mac mini, [interviewed it](https://weekly.thingelstad.com/archive/352/) for the job of driving his Elixir project, and wrote that it might “sunset my OpenClaw project” within weeks ([Weekly Thing 352](https://weekly.thingelstad.com/archive/352/)). How Otto fits with his other agents, in his words: > Otto is my personal agent. If you think of Thingy as the agent that works alongside me and is even visible to the public, Otto, spelled O-T-T-O, is my personal agent. It was originally powered by OpenClaw, and now runs on ChatGPT Dot and is also instantiated through Claude Duet. Otto helps with my email, my calendar and any personal projects I have going on. > > [Jamie, question 19](https://thingelstad.xyz/interviews/session-3/#q19) Release Notes began as one of Otto’s habits: [“Every day Otto wrote a daily reflection and my version number into a channel”](https://thingelstad.xyz/interviews/session-3/#q19). Otto has a face, and it made the face itself: [“I asked Otto to generate its own profile image, and I’ve had Otto update it over time.”](https://thingelstad.xyz/interviews/session-6/#q39) Why it never got a character the way Thingy did: [“Otto doesn’t show up on the web and doesn’t interact with anyone but me, so it doesn’t need that same consistent persona across many users and scenes.”](https://thingelstad.xyz/interviews/session-6/#q39) --- --- id: parseurl title: ParseURL summary: A tiny MediaWiki extension that exposes PHP’s parse_url, so a wiki page can pull the host, path, or query out of a URL. collection: Historical projects status: retired url: https://github.com/jthingelstad/ParseURL started: 2013-07-15 topics: - mediawiki sources: - kind: github repository: jthingelstad/ParseURL role: implementation connections: [] page: https://thingelstad.xyz/things/parseurl/ --- # ParseURL A tiny MediaWiki extension that exposes PHP’s parse_url, so a wiki page can pull the host, path, or query out of a URL. ParseURL adds two parser functions to MediaWiki. `{{#parseurl:}}` gives you one part of a URL, like its scheme, host, path, query, or fragment, using PHP’s [parse_url](https://www.php.net/manual/en/function.parse-url.php) function. `{{#parseurlquery:}}` gives you the value of a single query parameter, like the video ID in a YouTube link. Jamie wrote it in one sitting on July 15, 2013, and posted that he had “[made a super simple MediaWiki extension for parsing URLs](https://www.thingelstad.com/2013/07/15/made-a-super.html).” All three commits in the repository are from that day. It did its one job, and the repository is archived now. --- --- id: planet-kubb title: Planet Kubb summary: A family of Kubb community sites Garrick van Buren and Jamie built in 2012, with a feed aggregator, a wiki, a Q&A site and club sites. collection: Games status: dormant url: https://planetkubb.com/ started: "2012" topics: - mediawiki - play sources: - kind: website url: https://planetkubb.com/ role: website sitemap: https://planetkubb.com/wp-sitemap.xml feed: https://planetkubb.com/feed/ - kind: github repository: Planet-Kubb/rawdog role: historical - kind: github repository: Planet-Kubb/wiki role: historical - kind: website url: https://web.archive.org/web/20120616024936/http://planetkubb.com/ role: archive - kind: website url: https://web.archive.org/web/20120512222332/http://wiki.planetkubb.com/wiki/Main_Page role: archive - kind: website url: https://www.thingelstad.com/projects/open-loop/1-big-fuzzy-dead-cat/ role: reference connections: - to: ask-planet-kubb label: included detail: "On Open Loop #1 Jamie described Ask Planet Kubb as the question-and-answer site of Planet Kubb, added after the planet feed." source: https://www.thingelstad.com/projects/open-loop/1-big-fuzzy-dead-cat/ page: https://thingelstad.xyz/things/planet-kubb/ --- # Planet Kubb A family of Kubb community sites Garrick van Buren and Jamie built in 2012, with a feed aggregator, a wiki, a Q&A site and club sites. Garrick van Buren and Jamie built Planet Kubb together. It began in 2012, when Jamie bought planetkubb.com and set it up as a planet-style aggregator of Kubb content, built on rawdog with a Bootstrap theme, that collected Kubb videos from YouTube and posts from club blogs. More sites followed: Ask Planet Kubb for questions and answers, the [Planet Kubb Wiki](https://web.archive.org/web/20120512222332/http://wiki.planetkubb.com/wiki/Main_Page) for clubs, teams and tournaments, and The Pitch, a WordPress P2 chat site at pitch.planetkubb.com that he put up within a day of a player from Des Moines asking for one. He told the story on [Open Loop #1](https://www.thingelstad.com/projects/open-loop/1-big-fuzzy-dead-cat/), and said he had gone to great lengths to show it was not an attempt “to monetize the Kubb universe.” The [Planet Kubb GitHub organization](https://github.com/Planet-Kubb) describes the aim as “growing, connecting and supporting the worldwide Kubb community.” Jamie played Kubb on the Kubbchucks. At the [2013 US Nationals](https://www.thingelstad.com/2013/07/21/pictures-from-us.html) he spent Sunday “scoring games for Planet Kubb and running the final parts of the Planet Kubb Club Championship.” Club sites joined in, like the [Chippewa Valley Kubb League](https://www.thingelstad.com/2013/10/06/another-planetkubb-network.html) in 2013, and Garrick and Jamie created a notation and scoring system for recording games (see Planet Kubb Score). He stepped away from it later. Garrick still runs the server, and planetkubb.com is online as an aggregator [maintained by him](https://planetkubb.com/about/). Its feed was last updated in June 2017. The wiki, Ask Planet Kubb and the club subdomains no longer answer, and live on in Wayback Machine captures. On Garrick, in Jamie’s words: > Garrick is similarly passionate about technology, and about thinking broadly and exploring concepts. He’s a builder. He and I enjoyed building things together for many years and had a lot of fun doing it. > > [Jamie, question 17](https://thingelstad.xyz/interviews/session-2/#q17) --- --- id: planet-kubb-score title: Planet Kubb Score summary: Jamie’s notation and scoring system for recording Kubb games, begun on Planet Kubb in 2012. He is rebuilding it, and it is not published yet. collection: Games status: active url: null started: "2012" topics: - play - archives sources: - kind: website url: https://web.archive.org/web/20120715062240/http://wiki.planetkubb.com/wiki/Notation role: archive photograph: true - kind: github repository: Planet-Kubb/scoring role: historical - kind: github repository: Planet-Kubb/PyKubb role: historical connections: - to: planet-kubb label: began on detail: The notation was first published on the Planet Kubb Wiki, and the scoring materials live in the Planet Kubb GitHub organization. source: https://web.archive.org/web/20120715062240/http://wiki.planetkubb.com/wiki/Notation page: https://thingelstad.xyz/things/planet-kubb-score/ --- # Planet Kubb Score Jamie’s notation and scoring system for recording Kubb games, begun on Planet Kubb in 2012. He is rebuilding it, and it is not published yet. Planet Kubb Score is Jamie’s system for writing down a game of Kubb “like a baseball box score.” He created it with Garrick van Buren, who said on [Open Loop #3](https://www.thingelstad.com/projects/open-loop/3-kubb-fever/) in July 2012 that they had been working on it “almost from the very beginning” and who drew up the first scoresheet. Jamie calls it “the very first scoring & notation system for Kubb” ([Fun Facts](https://www.thingelstad.com/about/fun-facts/)). By July 2012 the Planet Kubb Wiki had a [Notation page](https://web.archive.org/web/20120715062240/http://wiki.planetkubb.com/wiki/Notation) whose goals were a notation that scales from player-by-player detail to simple games, can be sent over Twitter “turn by turn, tweet by tweet,” and is language neutral. In the interview he remembered that [“we brainstormed a lot around things like the Planet Kubb notation system and score sheets”](https://thingelstad.xyz/interviews/session-2/#q17). The [scoring repository](https://github.com/Planet-Kubb/scoring) holds the Planet Kubb scoresheet, including version 11 from Garrick, added in July 2014. [PyKubb](https://github.com/Planet-Kubb/PyKubb), started in August 2014, is a Python module to analyze Kubb games and output statistics. In October 2013 Jamie was “proud of” a [new scoresheet with on-pitch stats](https://www.thingelstad.com/2013/10/31/proud-of-this.html). In August 2014 he [wrote a Backus-Naur form grammar](https://www.thingelstad.com/2014/08/27/what-did-i.html) for the notation, and in 2017 mentioned having tried to write a parser for it with PyParsing ([Weekly Thing 25](https://weekly.thingelstad.com/archive/25/)). He is rebuilding the notation, grammar and scoresheets as a new site. It is not published yet. --- --- id: poap-kings title: POAP KINGS summary: The website of POAP KINGS, the Clash Royale clan of Jamie’s family, with its roster, data, and season recognition. collection: Games status: active url: https://poapkings.com/ started: 2026-02 topics: - poap - crypto - play sources: - kind: github repository: jthingelstad/poapkings.com role: implementation - kind: website url: https://poapkings.com/ role: website sitemap: https://poapkings.com/sitemap.xml connections: - to: elixir-drop label: runs detail: POAP KINGS runs Elixir Drop, its card-recognition and elixir-cost training game. source: https://poapkings.com/elixir-drop/ page: https://thingelstad.xyz/things/poap-kings/ --- # POAP KINGS The website of POAP KINGS, the Clash Royale clan of Jamie’s family, with its roster, data, and season recognition. POAP KINGS (#J2RGCRVG) is the Clash Royale clan Jamie started in early 2026 with his son Tyler and Tyler’s cousin Levi. He had [taken up the game](https://www.thingelstad.com/2025/09/27/after-following-tyler-to-pokmon.html) in September 2025 as a total newcomer, trying one of Tyler’s favorite games. In the [clan’s own words](https://poapkings.com/faq/), Raquaza and King Levy had cycled through clans that never quite fit, so the family built the clan it wanted: structure, recognition, and something lasting to show for the grind. Jamie claimed the [POAP KINGS Founder](https://www.thingelstad.com/2026/02/05/poap-at-poap-kings-founder.html) POAP on February 5, 2026, and by July the clan had [reached 50 members](https://www.thingelstad.com/2026/07/26/i-made-this-fun-slab.html) for the first time. The name comes from POAP. The clan started out publishing POAP collectibles for seasons and milestones. When the POAP company and product stopped operating, the clan kept the name and the meaning it had taken on inside the clan, “Proof of Arena Push.” Jamie asked Codex to [build the website](https://weekly.thingelstad.com/archive/342/) from the notes the three founders had kept, and it was live fast. Claude Code did much of the later work, design included. In April 2026 a new blog feature had made the design “unruly,” so he pointed Claude Design at the repository and it produced the current look ([Weekly Thing 345](https://weekly.thingelstad.com/archive/345/)). It grew into an Eleventy site on GitHub Pages with a sortable roster, an interactive data page, member guidance, season recognition, and pages for the clan’s sister clans, Ship It! and Elixir Kings. The roster and war data come from Elixir’s JSON API, and the site promotes the tools the clan built: Elixir and Elixir Drop. --- --- id: poap2rss title: POAP2RSS summary: RSS feeds of claims for any POAP drop or collector. Retired when the POAP API went offline in July 2026. collection: Historical projects status: retired url: https://poap2rss.com/ started: 2025-07-04 ended: 2026-07-24 topics: - poap - crypto - open-web sources: - kind: github repository: jthingelstad/POAP2RSS role: implementation - kind: website url: https://poap2rss.com/ role: reference - kind: website url: https://www.thingelstad.com/2025/07/06/vibe-coding-poaprss.html role: reference connections: - to: jamie-thingelstad-blog label: posts claims to detail: Jamie configured Micro.blog so that each POAP he minted became a post on his blog, from his POAP2RSS feed. source: https://weekly.thingelstad.com/archive/326/ page: https://thingelstad.xyz/things/poap2rss/ --- # POAP2RSS RSS feeds of claims for any POAP drop or collector. Retired when the POAP API went offline in July 2026. POAP2RSS turned POAP activity into plain old RSS: put a drop’s event ID or a collector’s address in the URL and get a feed of the latest claims, with the drop artwork and the collector’s ENS name or address as the author. Jamie issued a lot of drops and wanted to know when they were claimed. He also wanted to follow friends’ collecting in [Feedbin](https://www.thingelstad.com/2025/07/04/seeing-poap-claims-show-up.html) and connect claims to automation services like IFTTT and Zapier. He had asked POAP for RSS in his [POAP Wishlist](https://www.thingelstad.com/2023/01/14/poap-wishlist.html) in 2023 and again in [POAP + RSS = Awesome?](https://www.thingelstad.com/2025/01/05/poap-rss-awesome.html) in January 2025. It never came, so he built it. He built it in mid-2025, his first project with AI writing nearly all of the code. [Vibe Coding POAP2RSS](https://www.thingelstad.com/2025/07/06/vibe-coding-poaprss.html) tells how: a throwaway prototype with Claude, a feature description researched with ChatGPT o3 and Deep Research, and then a Python AWS Lambda behind API Gateway. He declared it [officially launched](https://www.thingelstad.com/2025/07/04/i-decided-to-declare-poaprss.html) on Independence Day 2025 and marked the occasion with a POAP. The [changelog](https://poap2rss.com/changelog/) has the later changes: feeds grew from 20 to 50 items, inactivity notices waited 12 weeks and could be switched off, pagination arrived for large drops, and a green-screen redesign landed in February 2026. POAP2RSS fed the claim streams of the 612 POAP Challenge and the Airport POAP Rally sites. The service read live claims through the POAP API, so it stopped working when POAP wound down. Jamie [retired it](https://github.com/jthingelstad/POAP2RSS/commit/22798583f396bd59771b0e4ee320d20c51d18f20) on July 24, 2026, a week before POAP’s July 31 shutdown, archived the repository, and replaced the home page with a notice pointing to the POAP team’s archive at poaparchive.com, “with gratitude to Isabel, Patricio, and the whole POAP team.” POAP, as he put it later, [“was simply a protocol that served a purpose”](https://thingelstad.xyz/interviews/session-2/#q15). --- --- id: project-templates title: Project Templates summary: The OmniFocus project templates Jamie has kept since 2017, and the private site he built in 2026 to fill them in and send them to OmniFocus. collection: Personal tools and making status: active url: null started: 2017-05 topics: - automation sources: - kind: website url: https://www.thingelstad.com/2017/05/19/using-project-templates.html role: reference - kind: website url: https://weekly.thingelstad.com/archive/79/ role: reference - kind: website url: https://www.thingelstad.com/2023/10/01/task-management-for.html role: reference - kind: website url: https://www.thingelstad.com/2024/09/02/my-gtd-structure.html role: reference - kind: website url: https://www.thingelstad.com/2025/05/06/how-to-newsletter-lessons-from.html role: reference connections: - to: weekly-thing label: plans every issue of detail: Each issue of the Weekly Thing starts as an OmniFocus project made from the Send Weekly Thing template, with the issue number and publish date filled in. source: https://www.thingelstad.com/2023/10/01/task-management-for.html artifacts: - file: home.png title: The list of templates caption: The home page, with the templates whose time of year is near under Coming up, and the day each was last made. The templates shown are made up for this picture. date: 2026-11-09 url: https://thingelstad.xyz/things/project-templates/artifacts/home.png - file: fill-in.png title: Filling in a template caption: A template’s page. Set the values and the preview works out every defer and due date before the project goes to OmniFocus. A made-up template. date: 2026-11-09 url: https://thingelstad.xyz/things/project-templates/artifacts/fill-in.png - file: last-time.png title: Last time caption: The page compares the template with the project it made last time, read from OmniFocus each Sunday, listing the tasks added by hand and the ones left out. The project shown is made up. date: 2026-11-09 url: https://thingelstad.xyz/things/project-templates/artifacts/last-time.png page: https://thingelstad.xyz/things/project-templates/ --- # Project Templates The OmniFocus project templates Jamie has kept since 2017, and the private site he built in 2026 to fill them in and send them to OmniFocus. Project Templates is the set of checklists Jamie keeps for the things he does more than once: a holiday, a business trip, readying the house and the cabin for winter, an issue of the Weekly Thing. Each one becomes a project in OmniFocus, the task manager he has used for [Getting Things Done](https://www.thingelstad.com/2023/10/01/task-management-for.html) for as long as he can remember, with the dates worked out for this time. He came to them late. In May 2017 he wrote [Using Project Templates](https://www.thingelstad.com/2017/05/19/using-project-templates.html): he had “seen and read about people using project templates for a while” but found the ways of managing them “bothersome.” The post sorts them into frequent activities, several copies of one thing, and things done rarely, and the last was his favorite: “It feels like a way to apply continuous learning to things you do once a year.” His first example was changing the clocks for Daylight Saving Time, a list in walking order through the house that includes the aquarium light timer he tended to miss. Most templates end with a task to “Update template with any changes from this year.” The templates are written in TaskPaper, with «Variables» in French quotation marks for the parts that change. By November 2018 a Shortcut ran each one, and [Weekly Thing 79](https://weekly.thingelstad.com/archive/79/) says why the format stayed: “I continue to store my templates in TaskPaper format to make them easy to edit, but the power comes in the Shortcut.” Those Shortcuts also blocked time on his calendar and drafted emails for a project. The [Send Weekly Thing template](https://www.thingelstad.com/2023/10/01/task-management-for.html) has two variables, «Issue» and «Date», and OmniFocus works out every other date from them. He chose templates over OmniFocus’s repeating projects on purpose: “Not having it repeating means I can change and alter any given instance however I like.” In 2025 he [said it again](https://www.thingelstad.com/2025/05/06/how-to-newsletter-lessons-from.html): “I like templates more than repeating projects because they let me make adjustments for each issue.” He kept the reminders to make them in OmniFocus too, in a [Repeating Projects list](https://www.thingelstad.com/2024/09/02/my-gtd-structure.html) of tasks like “Create project to winterize house,” each linking to its template in Drafts or to the Shortcut that makes the project. In November 2026 he moved the templates out of Drafts and built a small site for them with coding agents. It runs on his own Mac and is reached only from his private network, because the templates hold family and household details. Each template is a TaskPaper file with a short header that says what each variable is and when the template usually starts. The site shows what is coming up in the next month, fills in the values, works out the dates itself, and hands the finished project to OmniFocus through its paste link. Once a week it reads OmniFocus, never writing to it, so each template’s page can show the project it made last time: how far along it is, the tasks Jamie added by hand, and the template tasks it went without. So what changed last time is on the page when he makes the next one. --- --- id: proof-of-a-person title: Proof of a Person summary: Jamie’s POAP time capsule, 2021 to 2026, built from the archive he captured after the protocol wound down. collection: Art & archives status: active url: https://poap.thingelstad.xyz/ started: 2026-10-17 topics: - poap - crypto - archives sources: - kind: github repository: jthingelstad/poap.thingelstad.xyz role: implementation - kind: github repository: jthingelstad/poap-archive role: archive - kind: website url: https://poap.thingelstad.xyz/ role: website sitemap: https://poap.thingelstad.xyz/sitemap-index.xml connections: - to: poap2rss label: tells the story of detail: The capsule’s writing traces POAP2RSS back to Jamie’s 2023 POAP Wishlist, where he asked POAP for RSS feeds. “RSS never came from POAP, so Jamie built it.” source: https://poap.thingelstad.xyz/ - to: 612-poap-challenge label: preserves detail: The 612 POAP Challenge drops are one of the series on the capsule’s Issued page, and the archive keeps a mirror of the challenge site. source: https://poap.thingelstad.xyz/issued/ page: https://thingelstad.xyz/things/proof-of-a-person/ --- # Proof of a Person Jamie’s POAP time capsule, 2021 to 2026, built from the archive he captured after the protocol wound down. POAP went into maintenance mode in March 2026 and wound down that summer. On October 17, 2026 Jamie captured his whole POAP life into a public [archive](https://github.com/jthingelstad/poap-archive): every token he collected, every drop he created, the people who minted them, and the posts and Weekly Thing sections he wrote about POAP from 2021 on. The tokens themselves stay on the Gnosis chain. The archive keeps the records and artwork that lived on POAP’s own services, which would otherwise be gone. [Proof of a Person](https://poap.thingelstad.xyz/) is the time capsule he built from that archive and published the same day. It counts 259 tokens collected, from the ENS 4th Anniversary vote on June 7, 2021 to an airport rally stop at Seattle-Tacoma in July 2026, and 130 drops issued, which 639 people minted. Each year from 2021 to 2026 is a chapter headed by a line from his own posts. The pages show the timeline as two sides, what he collected and what he made for other people, with a network of the people who hold his drops, his writing about POAP, and a short history of the company. The site is a static Astro build from a JSON export of the archive. Drop artwork is served from a copy he took from POAP’s asset host while it was still up. What POAP had been for him, in his words: > It allowed me to assert that I did a thing without relying on any company or other independent arbiter to host and own that data. Instead, that data lived on the blockchain, which really delivered the promise of blockchain technology. … It became something I truly cherished. > > [Jamie, question 15](https://thingelstad.xyz/interviews/session-2/#q15) His reading of the end: [“POAP was kind of doomed, I think, in part because crypto has never answered the onboarding problem.”](https://thingelstad.xyz/interviews/session-2/#q15) He counts the capsule, with the nnxyz Rooms, as a new kind of thing: [“I expect there will be more of those, because it’s a new lever”](https://thingelstad.xyz/interviews/session-5/#q35). --- --- id: q2a-number-captcha title: q2a-number-captcha summary: A Question2Answer CAPTCHA plugin that spells out a nine-digit number in words and asks for one digit of it. collection: Historical projects status: retired url: https://github.com/jthingelstad/q2a-number-captcha started: 2014-11-16 topics: - play sources: - kind: github repository: jthingelstad/q2a-number-captcha role: implementation connections: - to: ask-planet-kubb label: protected detail: Jamie wrote the plugin to stop spam registrations on Ask Planet Kubb, the Question2Answer site he ran. source: https://www.thingelstad.com/2014/11/16/questionanswer-number-captcha.html page: https://thingelstad.xyz/things/q2a-number-captcha/ --- # q2a-number-captcha A Question2Answer CAPTCHA plugin that spells out a nine-digit number in words and asks for one digit of it. Jamie ran Ask Planet Kubb on [Question2Answer](https://www.question2answer.org/) for several years, and spam registrations were a constant problem. ReCaptcha let through four to ten spam sign-ups a day. The [Q2A Logical Captcha](https://github.com/amiyasahu/q2a-logical-captcha) plugin, which he had sent a pull request to, let through three to four times that many. So he brought over the defense that was already working on his MediaWiki wikis. He first wrote it in 2013 to [stop spam sign-ups on WikiApiary](https://www.thingelstad.com/2013/07/09/stopping-mediawiki-spam.html), then switched it to numbers spelled out in words ([Updated Dynamic Questy Captchas](https://www.thingelstad.com/2014/10/28/updated-dynamic-questy.html)). The plugin spells out a random nine-digit number with the Numbers_Words PHP package and asks for the digit in one position, so the answer never shows up in the page. It started life as a modified copy of Q2A Logical Captcha. He [released it](https://www.thingelstad.com/2014/11/16/questionanswer-number-captcha.html) on November 16, 2014 under the GPL v2, and reported that the early results were great. The last change, in 2015, removed a PHP warning. The repository is archived. --- --- id: r-w-book-club title: R/W Book Club summary: A Minneapolis-Saint Paul book club meeting since 2003, and the website that keeps the record of everything it has read. collection: Communities status: active url: https://rwbookclub.com/ started: 2003-04 topics: - reading - mediawiki sources: - kind: github repository: jthingelstad/rwbookclub.com role: implementation - kind: website url: https://rwbookclub.com/ role: website sitemap: https://rwbookclub.com/sitemap.xml feed: https://rwbookclub.com/feed.xml - kind: website url: https://www.thingelstad.com/projects/book-club/ role: reference - kind: website url: https://web.archive.org/web/20120106214958/http://rwbookclub.com/wiki/Main_Page role: archive connections: - to: oliver label: includes detail: Oliver is the book club’s agent and sixth member, sharing the same club database and corpus. source: https://rwbookclub.com/oliver/ story: color: "#507b68" introduction: Twenty years of reading together, with the record to prove it. engineering: - The website presents the club’s reading history and members’ commentary. - Public llms.txt and llms-full.txt files make the reading record accessible to agents for analysis. - An iCal feed lets members subscribe to the meeting calendar. - Oliver, the club’s agent, generates the site from the club database and publishes it to GitHub Pages. stack: - Static web - LLM context files - iCalendar related: - oliver questions: - How can an agent explore the club’s reading history? - How has the book club website evolved? source: https://rwbookclub.com/llms.txt sourceLabel: Reading history for agents page: https://thingelstad.xyz/things/r-w-book-club/ --- # R/W Book Club A Minneapolis-Saint Paul book club meeting since 2003, and the website that keeps the record of everything it has read. The R/W Book Club is a group of technically minded readers who have met in the Minneapolis-Saint Paul area since April 2003. R/W stands for Read / Write: the members read, and many of them also blog. The club reads about eight books a year, mostly nonfiction, and members take turns picking the next book ([About](https://rwbookclub.com/about/)). Jamie built the website, not the club. He joined in late 2007, when his friend and former professor John Riedl, who started the club, emailed him about “this small book club of geeky guys” he was part of. Jamie joined without hesitation, and shared the club with John, Tom, Erik and Dan until John died in 2013 ([Goodbye to my friend, John Riedl](https://www.thingelstad.com/2013/07/21/goodbye-to-my.html)). The club’s record has taken several forms. In early 2011 it was a MediaWiki site called the [Creative Computer Book Club](https://web.archive.org/web/20110323210256/http://creativecomputerbookclub.com/wiki/Main_Page); that July Jamie had a blast [hacking on MediaWiki](https://www.thingelstad.com/2011/07/15/i-had-a-blast-hacking.html) with the book club gang, and by January 2012 the same wiki was the [R/W Book Club](https://web.archive.org/web/20120106214958/http://rwbookclub.com/wiki/Main_Page) at rwbookclub.com. In 2017 he built a [Jekyll site](https://weekly.thingelstad.com/archive/17/) at rwbook.club. The club has also kept its record in a shared Airtable database. The current site is generated by [Oliver](https://rwbookclub.com/oliver/), the club’s agent, and offers the reading record as llms.txt files for agents and the meetings as an iCal feed. The members, he said, are [“all open to exploring and engaging with that”](https://thingelstad.xyz/interviews/session-3/#q20). Before Oliver, [“I had already made a version of our website that used llms.txt, so people could copy the link to that file, send it to their LLM of choice, and have a conversation about book picking.”](https://thingelstad.xyz/interviews/session-3/#q20) --- --- id: reading-things title: Reading Things summary: A quarterly newsletter about books from Tammy, Mazie, Tyler, and Jamie. The family committed to one year, sent four issues in 2021 and 2022, and has paused it. The archive is on Buttondown. collection: Publishing status: dormant url: https://buttondown.com/reading-things started: 2021-05-08 topics: - reading sources: - kind: website url: https://buttondown.com/reading-things role: website - kind: website url: https://web.archive.org/web/20211130142318/https://reading.thingelstad.com/archive/ role: archive - kind: website url: https://weekly.thingelstad.com/archive/186/ role: reference - kind: website url: https://www.thingelstad.com/2022/02/06/the-winter-issue.html role: reference connections: - to: weekly-thing label: was announced in detail: Jamie teased Reading Things in Weekly Thing 177 and announced it in Weekly Thing 186, a week after the first issue went out. source: https://weekly.thingelstad.com/archive/186/ page: https://thingelstad.xyz/things/reading-things/ --- # Reading Things A quarterly newsletter about books from Tammy, Mazie, Tyler, and Jamie. The family committed to one year, sent four issues in 2021 and 2022, and has paused it. The archive is on Buttondown. Reading Things was a newsletter about books from the whole Thingelstad family. Tammy, Mazie, Tyler, and Jamie each wrote about what they were reading. Jamie teased it as “a fun, new family project” in [Weekly Thing 177](https://weekly.thingelstad.com/archive/177/), and the [first issue](https://web.archive.org/web/20210508214912/https://reading.thingelstad.com/archive/reading-things-book-thief-atomic-habits-treasure/) went out on May 8, 2021. In [Weekly Thing 186](https://weekly.thingelstad.com/archive/186/) he explained the plan: four emails a year, about books and things related to them, like Tammy’s Corner and a bookstore challenge. No affiliate links, no tracking, and no “buy now” links. Issues followed in [summer](https://www.thingelstad.com/2021/07/25/we-just-sent.html) and [fall](https://www.thingelstad.com/2021/10/31/we-just-published.html) 2021. The [Winter 2022 issue](https://www.thingelstad.com/2022/02/06/the-winter-issue.html), sent on February 6, 2022, is the last one. In July 2021 the family marked 100 subscribers with a [Reading Things First 100 POAP](https://www.thingelstad.com/2021/07/25/poap-at-reading-things-first.html), which Jamie [wrote about](https://www.thingelstad.com/2022/06/04/my-introduction-to.html) in June 2022. Asked in his interview why it stopped after four: [“We committed to doing it for one year, which is why it ran for one year and four issues.”](https://thingelstad.xyz/interviews/session-6/#q38) [“We might come back to it, but it’s on pause.”](https://thingelstad.xyz/interviews/session-6/#q38) The old address, reading.thingelstad.com, no longer answers, and every issue is still readable [on Buttondown](https://buttondown.com/reading-things). --- --- id: redirector title: Redirector summary: The one place that answers for Jamie’s old and misspelled domains. It sends each to where its pages live now, rescues old blog links post by post, and serves a teapot to scanners hunting for WordPress. collection: Developer tools and systems status: active url: https://thingelstad.com/ started: 2026-09 topics: - open-web - archives sources: - kind: website url: https://thingelstad.com/ role: reference - kind: website url: https://thingelstad.com/wp-login.php role: reference connections: - to: jamie-thingelstad-blog label: keeps old links working for detail: Since October 31, 2026, an old address from the blog’s WordPress and earlier years goes straight to its post on www.thingelstad.com, tagged ref=thingelstad.com-archive. The first table matched 905 of them. source: https://thingelstad.com/Wintergreen-Plunge-Mittens/ - to: weekly-thing label: sends weeklything.com to detail: weeklything.com and the misspelled weekly.thinglestad.com land on the newsletter. source: https://weeklything.com/ - to: linking-things label: sends links.thingelstad.com to detail: The old link blog’s address has gone to Linking Things since October 28, 2026. source: https://links.thingelstad.com/ - to: thingelstad-photography label: sends the old photography sites to detail: photos, photog and photography.thingelstad.com, dark for years, land on this site’s page for the photography. source: https://photos.thingelstad.com/ artifacts: - file: teapot.png title: The teapot caption: What a scanner gets for asking thingelstad.com for wp-login.php, answered with HTTP 418. date: 2026-10-31 source: https://thingelstad.com/wp-login.php url: https://thingelstad.xyz/things/redirector/artifacts/teapot.png page: https://thingelstad.xyz/things/redirector/ --- # Redirector The one place that answers for Jamie’s old and misspelled domains. It sends each to where its pages live now, rescues old blog links post by post, and serves a teapot to scanners hunting for WordPress. Over twenty years Jamie has collected a lot of domains: the bare thingelstad.com, the micro.thingelstad.com the blog used for a while, weeklything.com, jamiethingelstad.com, and thinglestad.com with its letters swapped, the way people keep typing his name. Each needs to answer and send the visitor somewhere useful. For years that was a scatter of redirects at his registrar. In September 2026 he began moving them into one CloudFront distribution with a small function in front of it, and by late October every one of them was answered in one place. It started as plumbing: a name in, a 301 out. A redirect keeps the path, so a deep link to an old host still reaches the same page on the new one, and it adds a `ref` naming the host it came from, so his analytics show which old names people still use. On October 31, 2026 it started making decisions. The blog has moved from .Text to WordPress, Squarespace, Jekyll and Micro.blog, and links out on the web still point at addresses that stopped existing years ago. Sites that linked to them will never update, and search engines kept finding 404s. Now the function looks each old blog path up in a table of old addresses matched to their posts and sends the visitor straight to the post. The table started with 905 matches, made only where the old slug and date clearly point at one post. Each Saturday the paths still landing on a 404 are ranked by how many real visitors follow them, so matches get added where people actually arrive. About a quarter of the requests were never people: scanners probing for `wp-login.php`, `xmlrpc.php` and `.env` files. They get their own answer, an HTTP 418 “I’m a teapot” page explaining that this house hasn’t run WordPress since April 20, 2016, with a haiku in the source for anyone who looks. Every request now records what the function decided (a mapped post, a teapot, a plain redirect, or a fixed page) in the access log, so there is a record of exactly what it is doing. Asked whether the Redirector, Sync and Cards are things or plumbing, Jamie said [“They’re things, because they don’t serve just one service and they bring some intelligence.”](https://thingelstad.xyz/interviews/session-6/#q41) --- --- id: release-notes title: Release Notes summary: A daily email with today’s version number. Reply with notes from your day and they become that version’s release notes. collection: Personal tools and making status: active url: https://notes.yourversionnumber.com/ started: 2026-10-08 topics: - play - mcp sources: - kind: github repository: jthingelstad/yvn-release-notes role: implementation - kind: website url: https://notes.yourversionnumber.com/ role: website - kind: website url: https://www.thingelstad.com/2026/10/08/in-i-wrote-about-your.html role: reference - kind: website url: https://weekly.thingelstad.com/archive/353/ role: reference connections: [] bundles: - id: icon-studies title: A folded v and a dot caption: "The Release Notes direction from the October 31, 2026 design session with Codex: an ivory paper fold and a tangerine period on cobalt. An open journal was explored and set aside. Changelog received a separate mark made of three stacked versions." - id: favicon-studies title: The mark in a browser tab caption: Two simplified versions of the same mark, checked at 16 and 32 pixels. Flat was the recommendation for browser tabs; the full paper fold remained the PWA icon direction. The download keeps the original artwork, prompts and small-size previews. artifacts: - file: icon-folded-v-2026-10-31.png title: The single folded v caption: Ivory paper and a tangerine period on cobalt. The first concept was proposed for Changelog before Jamie assigned it to Release Notes. date: 2026-10-31 bundle: icon-studies url: https://thingelstad.xyz/things/release-notes/artifacts/icon-folded-v-2026-10-31.png - file: icon-open-journal-2026-10-31.png title: The open journal, set aside caption: A cobalt open book with a tangerine bookmark on cream. This direction was not selected. date: 2026-10-31 bundle: icon-studies url: https://thingelstad.xyz/things/release-notes/artifacts/icon-open-journal-2026-10-31.png - file: favicon-flat-2026-10-31.png title: Flat caption: The v and period with a broader silhouette and simplified curl. This was the recommended browser-tab direction in the study. date: 2026-10-31 bundle: favicon-studies url: https://thingelstad.xyz/things/release-notes/artifacts/favicon-flat-2026-10-31.png - file: favicon-micro-fold-2026-10-31.png title: Micro Fold caption: A reduced curl and a small number of fold tones, preserving more of the paper treatment at browser-tab sizes. date: 2026-10-31 bundle: favicon-studies url: https://thingelstad.xyz/things/release-notes/artifacts/favicon-micro-fold-2026-10-31.png - file: icon-design-files-2026-11-01.zip title: The icon design files caption: Full-size PNG studies, small-size previews, the design record and generation prompts. date: 2026-11-01 preview: icon-design-files-preview-2026-11-01.png bundle: favicon-studies url: https://thingelstad.xyz/things/release-notes/artifacts/icon-design-files-2026-11-01.zip page: https://thingelstad.xyz/things/release-notes/ --- # Release Notes A daily email with today’s version number. Reply with notes from your day and they become that version’s release notes. Release Notes is a daily email from Your Version Number. Each morning it tells you today’s number (“You’re 5.4.278 today”). Reply with anything about your day, or write it in the web app, and it is kept as the release notes for that version. Jamie [introduced it on October 8, 2026](https://www.thingelstad.com/2026/10/08/in-i-wrote-about-your.html). After making the Your Version Number site he wished he got his version by email, and then wondered what it would be like to add notes to each version. So he built it. The longer version, from the interview: > I just wanted to get an email every day that had my version number. That, by the way, stems back to something I had Otto doing in Discord. Every day Otto wrote a daily reflection and my version number into a channel. I thought, I’d rather have this landing in my email. … What if I just replied to it, and that was a form of micro journaling, a way of very lightweight journaling? > > [Jamie, question 19](https://thingelstad.xyz/interviews/session-3/#q19) It is lightweight journaling built around the reply. In [Weekly Thing 353](https://weekly.thingelstad.com/archive/353/) he wrote that he enjoyed getting the email each day and simply replying with notes, photos, and even audio. The [README](https://github.com/jthingelstad/yvn-release-notes) has the rest: a writing streak and “On this day” notes from earlier releases right in the email, tags and search, weather and places kept with each day, a Day One import, a full zip export, opt-in transcripts and photo descriptions, and owner-approved access for agents through MCP. The email tracks nothing and loads nothing remote. He sets it beside the blog: [“If I have a private journal with Release Notes, I have a public journal with my blog”](https://thingelstad.xyz/interviews/session-3/#q25). It runs on AWS: a scheduled sender, SES for inbound replies, DynamoDB for notes, and a React web app with Hono functions on Lambda behind CloudFront. The version arithmetic is a port of the Your Version Number site’s own code, checked against thousands of generated cases. Opening it to other people took little, he said: [“The reality was that I had done all the work. The authentication was there, the design was done, and I had a fully functioning system, so the effort of opening it up to other users was really small. I intentionally gated it on Weekly Thing members so that it didn’t grow out of control”](https://thingelstad.xyz/interviews/session-3/#q19). The [icon studies](#artifacts-icon-studies) made with Codex on October 31, 2026 paired Release Notes with its iPhone companion, [Changelog](/things/changelog/#artifacts-icon-studies). Release Notes kept a single folded ivory v and a tangerine period on cobalt; Changelog’s selected direction stacks three versions of the fold. A literal open journal was set aside. The [favicon studies](#artifacts-favicon-studies) reduce the same v and dot for a browser tab, with Flat and Micro Fold compared against the full paper sculpture at 16 and 32 pixels. --- --- id: road-sign-math-2026 title: Road Sign Math summary: "Road Sign Math rebuilt as an iPhone app that is the whole game: capture a sign, read its numbers, solve it, post it. roadsignmath.xyz shows every sign on a map, no app needed." collection: Games status: active url: https://roadsignmath.xyz/ started: 2026-10-30 topics: - play sources: - kind: website url: https://roadsignmath.xyz/ role: website sitemap: https://roadsignmath.xyz/sitemap.xml - kind: github repository: jthingelstad/roadsignmath.xyz role: implementation - kind: github repository: jthingelstad/roadsignmath-ios role: implementation - kind: website url: https://roadsignmath.xyz/privacy role: reference connections: [] story: color: "#006348" introduction: Driving + Math = Fun. engineering: - The iPhone app is the whole game. It reads the numbers on a photo of a sign on the phone, with Apple’s Vision, boxes each one, and turns what it reads into numbers a player can use, so 82nd St is 82 and EXIT 7B is 7. - One equation checker is written in TypeScript for the server and ported to Swift for the app, and both pass the same test vectors. A way counts when its math is true and its numbers come from the sign. The math is kept as LaTeX and drawn with MathJax on the website and SwiftMath in the app. - The server is Node and Hono in a Lambda Web Function behind CloudFront, with DynamoDB for the signs and players, S3 for photos and SES for sign-in mail, released on every merge to main. Its API is described in OpenAPI 3.1. - Signing in is an email with a link or a six-digit code, with no password. Claude moderates posts, holding one only when it is clearly objectionable, looks at each profile photo first, and writes each photo’s alt text. - Badges are little road signs worked out from the signs each time they are read, so a badge follows its sign. There are no points, no counts and no ranks. - The website’s map is us-atlas’s Albers USA map, with each sign’s place projected and clustered on the server, so it needs no map provider. The app’s map is MapKit. stack: - Swift and SwiftUI - iOS 26 - Vision - MapKit - TypeScript - Hono - AWS Lambda - DynamoDB - Claude - TestFlight related: - road-sign-math - road-sign-math-2021 questions: - What does the Road Sign Math app do with a photo of a sign? - Why does Road Sign Math have badges but no points? - How does the Road Sign Math website draw its map without a map provider? source: https://roadsignmath.xyz/ sourceLabel: See the signs started: Played since 2005, rebuilt in 2026 bundles: - id: the-app title: The iPhone app caption: The game from signing in to posting a sign, from October 30 and 31, 2026, the first two days of building it, on the simulator against a local copy of the server or the live one, with the 16 signs from the blog. The sample sign is one the app draws itself, for a simulator with no camera. - id: the-website title: The website caption: The new roadsignmath.xyz on October 31, 2026, where every sign posted from the app shows up, with no sign-in. - id: logo-development title: Logo development caption: Concept sheets from Jamie’s design session with Codex on October 31, 2026, followed by the approved five-icon collection and matching wordmark. The green Radical Route mark became the default direction, with four alternatives for players to choose from. artifacts: - file: app-icon.png title: The first app icon caption: The math from the Twin Lakes sign, √(5 − 1) = 2, on a green guide sign. date: 2026-10-30 source: https://github.com/jthingelstad/roadsignmath-ios/pull/3 bundle: the-app url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/app-icon.png - file: sign-in-email.png title: The sign-in email caption: Under a “Driving + Math = Fun” sign, a button that signs in on the iPhone and a six-digit code to type instead. The code and link here are examples. date: 2026-10-30 bundle: the-app url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/sign-in-email.png - file: home.png title: Home caption: "The Latest feed, newest first: Tyler’s I-35W at 82nd Street sign from September 2025, its math, (90 − 82) ÷ 8 × 1 × 2 = 6 ÷ (10 − 7), and a button to find another way." date: 2026-10-31 bundle: the-app url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/home.png - file: map.png title: The Map caption: The 16 signs as pins and clusters across North America, filtered by year, with a search for a town, a number or a person. date: 2026-10-30 bundle: the-app url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/map.png - file: sign.png title: A sign caption: "“On the way to the airport,” Jamie’s sign from August 2025 near Burlington, Vermont: its photo, its math, (25 − 1) ÷ 8 = 4 − 3 ÷ 3, and the ways found so far." date: 2026-10-30 bundle: the-app url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/sign.png - file: capture.png title: Capture caption: The camera in Passenger mode, after a shot of the sample sign. Every number it read has a yellow box, and it says it got five. date: 2026-10-30 bundle: the-app url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/capture.png - file: check-the-numbers.png title: Check the numbers caption: Every number the camera read on the I-35W sign, boxed in yellow on the photo and listed below to keep or drop. It read 12, including the 902 on the minivan’s plate. date: 2026-10-30 bundle: the-app url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/check-the-numbers.png - file: fix-a-number.png title: Checking the numbers caption: Fixing one number while checking what the camera read, with a close-up of where it read 82 in “82nd”. Letters next to a number are fine, so 7B counts as 7. date: 2026-10-30 bundle: the-app url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/fix-a-number.png - file: solve.png title: Solving it caption: The math keypad on the sample sign, with roots, powers and factorials. (90 − 82) ÷ 8 = 1⁷ uses every number on the sign, and the app says “It works! Both sides make 1.” date: 2026-10-30 bundle: the-app url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/solve.png - file: post-it.png title: Post it caption: Naming the sign, with a suggested name, and its place, Bloomington, Minnesota, taken from the photo. date: 2026-10-30 bundle: the-app url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/post-it.png - file: posted.png title: Posted! caption: "The sign is on the map and the website, and two new badges came with it, Square Root and States: 2." date: 2026-10-30 bundle: the-app url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/posted.png - file: badges.png title: Badges caption: The shelves of road-sign badges, Firsts and Places, each with how it is earned and, once it is, the day and the sign that earned it. date: 2026-10-30 bundle: the-app url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/badges.png - file: player-page.png title: A player’s page, in dark mode caption: Jamie’s page in the app, with 13 signs in 5 states since 2021, his badges, and his signs as photos. date: 2026-10-31 bundle: the-app url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/player-page.png - file: find-another-way.png title: Find another way caption: "Writing a second way on Tyler’s I-35W sign: (90 − 82) × 2 = 10 + 6. It works, and three numbers sit this one out." date: 2026-10-31 bundle: the-app url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/find-another-way.png - file: profile-photo.png title: A profile photo caption: Fitting a picture of a road and a sign into the circle that goes beside a player’s signs and on their page. date: 2026-10-31 bundle: the-app url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/profile-photo.png - file: website-home.png title: Home caption: "“Find a sign. Make the math true.” The map of every sign on the US, with a card for Minnesota’s two signs, and who’s playing: Jamie, Tyler and Tammy." date: 2026-10-31 source: https://github.com/jthingelstad/roadsignmath.xyz/pull/18 bundle: the-website url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/website-home.png - file: website-sign.png title: A sign caption: "Tyler’s I-35W at 82nd Street sign on the website: the photo, the math, the ways found so far, the numbers, a map pinned on the town, and nearby signs." date: 2026-10-31 bundle: the-website url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/website-sign.png - file: website-player.png title: A player’s page caption: Jamie’s page on the website, with his badges and his signs on the map. date: 2026-10-31 bundle: the-website url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/website-player.png - file: website-beta.png title: Join the beta caption: The website’s section for the app, with a link to join the iPhone beta through TestFlight. date: 2026-10-31 source: https://github.com/jthingelstad/roadsignmath.xyz/pull/22 bundle: the-website url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/website-beta.png - file: logo-first-directions.png title: The first three directions caption: Radical Route combines a square-root symbol with an exit arrow. Genesis Sign uses 3 × 33 = 99 from the first road sign. Math Crossing puts crossing roads inside a yellow diamond. date: 2026-10-31 bundle: logo-development url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/logo-first-directions.png - file: logo-color-exploration.png title: Green and yellow caption: Radical Route in highway green and sign yellow, alongside an upright crossing symbol. Jamie chose green for the default icon and kept yellow as an alternative. date: 2026-10-31 bundle: logo-development url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/logo-color-exploration.png - file: logo-operator-exploration.png title: Division, factorial, and four operators caption: "Three more alternatives: a division symbol with an exit arrow, a 3! route shield, and addition, subtraction, multiplication, and division on one green sign." date: 2026-10-31 bundle: logo-development url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/logo-operator-exploration.png - file: logo-polished-collection.png title: The polished collection caption: Highway, Sunshine, Division, Factorial, and Four Ways, redrawn as vector artwork. The sheet includes the matching Overpass wordmark, light and dark logo treatments, and checks at 64, 40, and 24 pixels. date: 2026-10-31 bundle: logo-development url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/logo-polished-collection.png - file: logo-highway.png title: Highway, the default icon caption: The white Radical Route mark on highway green, combining a square-root radical with an exit arrow. date: 2026-10-31 bundle: logo-development url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/logo-highway.png - file: logo-sunshine.png title: Sunshine caption: The same Radical Route geometry in deep green on sign yellow. date: 2026-10-31 bundle: logo-development url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/logo-sunshine.png - file: logo-division.png title: Division caption: A division symbol whose horizontal bar becomes an exit arrow, in deep green on yellow. date: 2026-10-31 bundle: logo-development url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/logo-division.png - file: logo-factorial.png title: Factorial caption: White 3! lettering inside a green route shield on yellow. date: 2026-10-31 bundle: logo-development url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/logo-factorial.png - file: logo-four-ways.png title: Four Ways caption: Addition, subtraction, multiplication, and division inside a white sign border on green. date: 2026-10-31 bundle: logo-development url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/logo-four-ways.png - file: logo-wordmark.png title: The matching wordmark caption: The Radical Route mark beside Road Sign Math in Overpass, the highway-inspired typeface already used by the app. date: 2026-10-31 bundle: logo-development url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/logo-wordmark.png - file: logo-identity-v1.zip title: Identity artwork and exports caption: "The complete design package: five square PNG icons, editable SVG masters, separate layers, wordmarks and logo arrangements, size previews, and the Overpass font with its license." date: 2026-10-31 preview: logo-identity-v1-preview.png bundle: logo-development url: https://thingelstad.xyz/things/road-sign-math-2026/artifacts/logo-identity-v1.zip page: https://thingelstad.xyz/things/road-sign-math-2026/ --- # Road Sign Math Road Sign Math rebuilt as an iPhone app that is the whole game: capture a sign, read its numbers, solve it, post it. roadsignmath.xyz shows every sign on a map, no app needed. In October 2026 Jamie rebooted Road Sign Math a third time, 21 years after the first sign, as the iPhone app he had wanted since 2011. The app is the whole game. You photograph a sign from the passenger seat, the app boxes every number it can read, you check them, write your math on a keypad made for it, and post it. Everyone’s signs land on a feed, a map and a page for each player, and anyone can find another way to make a posted sign true. The first 16 signs are the ones from the blog, found by Jamie, Tyler and Tammy from 2021 to 2025. There are still no scores. He said so when the app was planned: “The point system wasn’t a good idea. So I want to keep to the root which is a fun road trip game based on math and finding signs.” Instead there are badges, little road signs for a first sign, new states, a × in a way, all four seasons, and a few secrets. roadsignmath.xyz is the window onto the game for anyone without the app: the map of every sign, a page for each sign and each player, and no sign-in. It went live on October 30, 2026, replacing the blog, and on October 31 he submitted the app to Apple for a public TestFlight beta. Both the website and the app are open source. Why now, after fifteen years of wanting an app: > It’s entirely different because of AI. Without it I could not create the experience I always envisioned. Now, with the help of Claude and AI, I felt I could realize the mobile vision I always had in mind for this project. > > [Jamie, question 10](https://thingelstad.xyz/interviews/session-2/#q10) Road Sign Math is, he said, [“a thing I have a fond appreciation for and have always wanted to come back to”](https://thingelstad.xyz/interviews/session-1/#q5). Building the app was [“one of the last things on my list”](https://thingelstad.xyz/interviews/session-5/#q33). --- --- id: road-sign-math title: Road Sign Math (2005) summary: The first Road Sign Math, at roadsignmath.com from 2005 to 2016, where 40 players posted 251 road signs whose numbers make an equation, first on a blog and from 2011 on a wiki. collection: Games status: retired url: https://web.archive.org/web/20151209013747/http://roadsignmath.com/wiki/Main_Page started: 2005-02-13 ended: "2016" topics: - mediawiki - play - archives sources: - kind: website url: https://web.archive.org/web/20151209013747/http://roadsignmath.com/wiki/Main_Page role: archive - kind: website url: https://www.thingelstad.com/2010/02/13/010000.html role: reference - kind: website url: https://www.thingelstad.com/2023/10/21/road-sign-math.html role: reference - kind: website url: https://www.thingelstad.com/projects/road-sign-math/ role: reference connections: - to: road-sign-math-2021 label: was succeeded by detail: Five years after Jamie let roadsignmath.com go, a sign Tammy found near Phoenix brought the game back as a blog of just his family’s signs, or as he put it, “Just my signs. No scoring system or leaderboards.” source: https://www.thingelstad.com/2023/10/21/road-sign-math.html kind: lineage story: color: "#287454" introduction: A little mathematics. A lot of looking around. engineering: - The site launched in 2005 as a blog of signs on .Text and moved to WordPress in 2007. As other people sent in their own signs it gained rules for play, a scoring system and scoreboards for players and states. - In 2011 it moved from a blog to a wiki so players could submit and maintain their own signs. - In October 2026 Jamie rebuilt it from a 2016 MediaWiki backup, as Markdown with each sign’s math in TeX, and recovered its photos from a poster, the Internet Archive, an old backup drive and copies he had kept. stack: - .Text - WordPress - MediaWiki related: - road-sign-math-2021 - road-sign-math-2026 - planet-kubb - open-loop questions: - How did Road Sign Math start? - Why did the first Road Sign Math site move from a blog to a wiki? - What happened to the signs players sent in from 2005 to 2014? source: https://web.archive.org/web/20151209013747/http://roadsignmath.com/wiki/Main_Page sourceLabel: See the wiki in the Internet Archive started: Played since 2005 bundles: - id: archive title: The first site, rebuilt caption: In October 2026 Jamie rebuilt the first site, 2005 to 2014, from a 2016 MediaWiki backup, with photos recovered from the one-year anniversary poster, the Internet Archive, an old backup drive and copies he had kept. Of its 251 signs, 157 have a photo again. - id: my-signs title: Jamie’s signs caption: Photos of the signs Jamie found himself, from the first site. - id: first-site title: From the first site caption: The rules, the logos Jamie made, and the poster Jim Bernard and Suzie Meredith made for him as a gift for the site’s first year. artifacts: - file: map-2005-2014.png title: Every sign, 2005 to 2014 caption: All 251 signs, Jamie’s in yellow and other players’ in blue. 240 are in 44 states and Washington, D.C., none from Indiana, Kansas, Maine, Nevada, Oklahoma or Tennessee, and 11 are in eight other countries, one of them in the Serengeti. date: 2026-10-30 bundle: archive url: https://thingelstad.xyz/things/road-sign-math/artifacts/map-2005-2014.png - file: signs-2005-2014.csv title: The signs, as data caption: "One row per sign: its number on the old site, the day it was posted, its title and type, the numbers on it, the math as the site typeset it (TeX), where it is, its photos in the ZIP, and who found it." date: 2026-10-30 bundle: archive url: https://thingelstad.xyz/things/road-sign-math/artifacts/signs-2005-2014.csv - file: photos-2005-2014.zip title: Every photo, 2005 to 2014 caption: All 164 surviving photos of 157 signs, most of them sent in by the players who found the signs, named like the rows of the CSV, by the day the sign was posted and its name. Most are cut from the one-year anniversary poster; the rest come from the Internet Archive, an old backup drive and copies Jamie had kept. Camera details are taken out. date: 2026-10-30 preview: photos-2005-2014.jpg bundle: archive url: https://thingelstad.xyz/things/road-sign-math/artifacts/photos-2005-2014.zip - file: genesis-2005-03-07.jpg title: Genesis caption: The sign that started it, on I-94 near Melrose, Minnesota, heading east toward the Twin Cities. Melrose 3, St Cloud 33, Minneapolis 99, and 3 × 33 = 99. The full-size frame from Jamie’s Canon PowerShot G3, found on an old backup drive in 2026; the site only ever showed a small copy. date: 2005-03-07 bundle: my-signs url: https://thingelstad.xyz/things/road-sign-math/artifacts/genesis-2005-03-07.jpg - file: my-signs-2005-2012.jpg title: Jamie’s signs, 2005 to 2012 caption: The 24 signs Jamie found for the first site whose photos survive, with the day he posted each one. Most are cut from the one-year anniversary poster and are as sharp as the site showed them. date: 2026-10-30 bundle: my-signs url: https://thingelstad.xyz/things/road-sign-math/artifacts/my-signs-2005-2012.jpg - file: rules-3rd-edition-2006.pdf title: The rules, 3rd edition caption: Revision B, from November 2006, with an example sign for every kind of sign. Typeset in October 2026 from the wiki’s copy, with six plus signs the wiki had lost put back. Two small pictures, a gold star and a pie, are lost. date: 2006-11 preview: rules-3rd-edition-2006.png bundle: first-site url: https://thingelstad.xyz/things/road-sign-math/artifacts/rules-3rd-edition-2006.pdf - file: logo-original.jpg title: The original logo caption: "The first site’s logo, which Jamie made: a guide sign that does its own math, 4 × 25 = 100." bundle: first-site url: https://thingelstad.xyz/things/road-sign-math/artifacts/logo-original.jpg - file: logo-2011.pdf title: The shield logo caption: "The wiki’s logo, which Jamie made: an interstate shield in front of the Genesis sign. The vector original, saved as a PDF on February 21, 2011." date: 2011-02-21 preview: logo-2011.png bundle: first-site url: https://thingelstad.xyz/things/road-sign-math/artifacts/logo-2011.pdf - file: poster-2006.jpg title: The one-year poster caption: Jim Bernard and Suzie Meredith made Jamie this 16 × 20 poster of the first year’s signs as a gift. Most of the photos in this archive were cut from its print file; this copy is half its size. date: "2006" bundle: first-site url: https://thingelstad.xyz/things/road-sign-math/artifacts/poster-2006.jpg page: https://thingelstad.xyz/things/road-sign-math/ --- # Road Sign Math (2005) The first Road Sign Math, at roadsignmath.com from 2005 to 2016, where 40 players posted 251 road signs whose numbers make an equation, first on a blog and from 2011 on a wiki. Road Sign Math is a driving game: find a road sign whose numbers make a valid equation, photograph it, and share it. It began with a sign on I-94 East toward the Twin Cities that Jamie passed coming home from visiting family in North Dakota, which listed distances of 3, 33 and 99 miles: 3 times 33 equals 99. On [Open Loop #1](https://www.thingelstad.com/projects/open-loop/1-big-fuzzy-dead-cat/) he recalled that his friend Jim told him he should make a website, “and so that day I did a website.” He told it again in the interview: > I would see this sign. It said 3, 33, 99. To me it was just obvious that you should go up to the sign and put in a times sign and an equal sign, because here was essentially a math equation just sitting right there. I saw that sign dozens of times and thought, that’s so funny. Then I wondered how many other signs there were like that > > [Jamie, question 9](https://thingelstad.xyz/interviews/session-2/#q9) He [launched the site](https://www.thingelstad.com/2010/02/13/010000.html) on February 13, 2005, as a blog of signs on .Text, moved it to [WordPress](https://www.thingelstad.com/2007/08/17/t212185032.html) in August 2007, and as other people sent in their own it gained rules, a scoring system and scoreboards for players and states. Signs came from all 50 states and most continents, including one from the Serengeti; by 2012 there were over 200. In 2011 he rebooted it for the first time, as a wiki, so players could maintain their own signs. He thought about an iOS app for capturing signs back then, but never built it. That took another 15 years. Two spin-offs, Road Sign Wordplay and Road Sign Bingo, never got going, and he [shut both down](https://www.thingelstad.com/2012/02/08/shutting-down-some.html) in February 2012 with other “ideas that I set up and then never took anywhere.” In 2016, during a round of [technical downsizing](https://www.thingelstad.com/2016/05/03/technical-downsizing.html), he shut the site down and let roadsignmath.com expire ([Road Sign Math Rebooted](https://www.thingelstad.com/2023/10/21/road-sign-math.html)). In his telling, [“the very first version is almost one of those stories about a rabbit hole I went down and took a wrong turn. I gamified it”](https://thingelstad.xyz/interviews/session-2/#q10). The 2016 shutdown was not a verdict on the game. He had decided to cut back on projects, and it [“got swept up in that, not as a specific choice, but under the umbrella of having fewer things to tend to and work on”](https://thingelstad.xyz/interviews/session-2/#q10). The site had an afterlife at work: [“when we were building MarketWatch, we created a capability called live quotes.”](https://thingelstad.xyz/interviews/session-1/#q4) [“And that started from what I learned building the MathJax implementation for Road Sign Math”](https://thingelstad.xyz/interviews/session-1/#q4) In October 2026 he rebuilt the first site from a 2016 MediaWiki backup: 251 signs found by 40 players from 2005 to 2014, with photos for 157 of them dug out of the one-year anniversary poster, the Internet Archive, an old backup drive and copies he had kept. The game came back twice: as a blog of his family’s signs from 2021, and in 2026 as an iPhone app with a new roadsignmath.xyz. --- --- id: road-sign-math-2021 title: Road Sign Math (2021) summary: Road Sign Math as a simple blog of the signs Jamie’s family found from 2021 to 2025, first at roadsignmath.thingelstad.com and from 2023 on Micro.blog at roadsignmath.xyz. collection: Games status: retired url: https://web.archive.org/web/20260909070315/https://www.roadsignmath.xyz/ started: 2021-03 ended: 2026-10-30 topics: - play - open-web sources: - kind: website url: https://web.archive.org/web/20260909070315/https://www.roadsignmath.xyz/ role: archive - kind: website url: https://weekly.thingelstad.com/archive/177/ role: reference - kind: website url: https://www.thingelstad.com/2023/10/21/road-sign-math.html role: reference - kind: website url: https://www.thingelstad.com/2025/09/01/it-always-makes-me-smile.html role: reference - kind: github repository: jthingelstad/rsm.thingelstad.com role: historical connections: - to: road-sign-math-2026 label: was succeeded by detail: In October 2026 the 16 signs on the blog became the first signs in the Road Sign Math iPhone app, and the new roadsignmath.xyz replaced the blog. source: https://github.com/jthingelstad/roadsignmath.xyz/pull/2 kind: lineage story: color: "#287454" introduction: Just the family’s signs. engineering: - The blog runs on Micro.blog, with one post per sign, its photo, and the math typeset with MathJax from TeX in the post. - The 2021 posts keep their 2021 dates on Micro.blog, though their photos were uploaded there in 2023. stack: - Micro.blog - MathJax related: - road-sign-math - road-sign-math-2026 questions: - Why did Road Sign Math come back as a blog without scores? - Which signs were posted on the Road Sign Math blog? source: https://web.archive.org/web/20260909070315/https://www.roadsignmath.xyz/ sourceLabel: See the blog in the Internet Archive started: Posted from 2021 to 2025 bundles: - id: the-blog title: The blog caption: What was left of the blog when the new roadsignmath.xyz replaced it on October 30, 2026. artifacts: - file: front-page-2026-10.jpg title: The front page caption: The blog’s front page on October 20, 2026, ten days before it was replaced, with its newest sign, the one Tyler found driving up I-35W, its math typeset under the post. date: 2026-10-20 bundle: the-blog url: https://thingelstad.xyz/things/road-sign-math-2021/artifacts/front-page-2026-10.jpg - file: posts-2021-2025.json title: Every post, as Micro.blog exported it caption: All 16 posts from March 2021 to September 2025 as a JSON Feed, with each post’s words, its math in TeX, the name of its photo and its date. Thirteen are Jamie’s signs, two are Tyler’s and one is Tammy’s, in six states. date: 2026-10-30 bundle: the-blog url: https://thingelstad.xyz/things/road-sign-math-2021/artifacts/posts-2021-2025.json page: https://thingelstad.xyz/things/road-sign-math-2021/ --- # Road Sign Math (2021) Road Sign Math as a simple blog of the signs Jamie’s family found from 2021 to 2025, first at roadsignmath.thingelstad.com and from 2023 on Micro.blog at roadsignmath.xyz. Jamie let Road Sign Math’s first site go in 2016. In 2017 he started a Jekyll site for the signs, [rsm.thingelstad.com](https://github.com/jthingelstad/rsm.thingelstad.com), on a stock theme. It never got past the theme’s sample posts. In March 2021 a sign Tammy found near Phoenix gave Road Sign Math “a breath of new life” at roadsignmath.thingelstad.com ([Weekly Thing 177](https://weekly.thingelstad.com/archive/177/)), and that summer the family found ten more on a [Vermont road trip](https://www.thingelstad.com/2021/08/15/varmont-road-trip.html). He registered roadsignmath.xyz in 2021, and in October 2023 [rebooted](https://www.thingelstad.com/2023/10/21/road-sign-math.html) Road Sign Math a second time, as a simple blog on Micro.blog: “Just my signs. No scoring system or leaderboards.” New signs kept turning up, like one in [September 2025](https://www.thingelstad.com/2025/09/01/it-always-makes-me-smile.html), the last of 16. Why the second version was a simple blog, in his words: > The second version was a direct response to a three-day road trip we made to Arizona. Tammy made these envelopes of activities to keep the kids busy. One of them was to play Road Sign Math, with a prize if they could find signs. I loved it, because it brought this thing I had built back into our family. … So I decided to bring it back as a blog, keep it simple, and focus on having fun. > > [Jamie, question 10](https://thingelstad.xyz/interviews/session-2/#q10) On October 30, 2026, the new roadsignmath.xyz replaced the blog, and its 16 signs became the first signs in the Road Sign Math iPhone app. The blog kept the game alive until he was ready to build the app. --- --- id: stone-steel-people title: Stone/Steel/People summary: A square photo book of a little over 30 of Jamie’s pictures, one to a page, made with Blurb after a 2010 photography workshop. collection: Art & archives status: archived url: https://www.blurb.com/b/1813441-stone-steel-people started: 2010-11 ended: 2010-12-05 topics: - making sources: - kind: website url: https://www.blurb.com/b/1813441-stone-steel-people role: archive - kind: website url: https://www.thingelstad.com/2010/12/05/first-photo-book.html role: reference connections: - to: thingelstad-photography label: drew on the same work as detail: Both come from Jamie’s photography of the early 2010s, which the portfolio site showed by subject. source: https://www.thingelstad.com/2012/07/01/website-for-my.html page: https://thingelstad.xyz/things/stone-steel-people/ --- # Stone/Steel/People A square photo book of a little over 30 of Jamie’s pictures, one to a page, made with Blurb after a 2010 photography workshop. Stone/Steel/People is Jamie’s [first photo book](https://www.thingelstad.com/2010/12/05/first-photo-book.html). He made it after Layne Kennedy’s 72 Hours workshop at the Minneapolis Photo Center, and the name is what he photographed there: stone, steel, and people. Two weeks before it came out he wrote about [editing it down](https://www.thingelstad.com/2010/11/15/editing-a-book.html) to the pictures that belonged. The book is square, one image to a page, “a little over 30 pictures,” and it took him “between 10 and 15 hours” to put together. He published it through Blurb, where it is [still for sale](https://www.blurb.com/b/1813441-stone-steel-people). It is archived because it is done. In the interview he grouped it with the tree carving and the puzzle: [“These projects all came to a natural conclusion”](https://thingelstad.xyz/interviews/session-4/#q28). Asked what paper does that a page doesn’t: [“In both cases it’s something you hold in your hand, and I think that has real meaning.”](https://thingelstad.xyz/interviews/session-6/#q42) [“A book is an artifact.”](https://thingelstad.xyz/interviews/session-6/#q42) --- --- id: sync title: Sync summary: A page that shows what each of Jamie’s systems holds right now, how far behind each hop between them runs, and a receipt for the newest item of each kind. collection: Developer tools and systems status: active url: https://sync.thingelstad.xyz/ started: 2026-10-26 topics: - automation - open-web sources: - kind: github repository: jthingelstad/sync.thingelstad.xyz role: implementation - kind: website url: https://sync.thingelstad.xyz/ role: website - kind: website url: https://sync.thingelstad.xyz/flows/ role: reference connections: - to: weekly-thing label: follows the newest issue of detail: The Weekly Thing feed names the newest issue, and the page follows it to the Librarian, to Thingy, and to Linking Things, showing where it has arrived and where it has not. source: https://sync.thingelstad.xyz/flows/#hop-7 - to: wt-builder label: watches the sends of detail: Every send WT Builder makes is a hop on the map, to the website, the email, the audio and the Librarian. WT Builder publishes no receipt of its own yet, so those hops are measured from what the next system down holds. source: https://sync.thingelstad.xyz/flows/#hop-10 - to: jamie-thingelstad-blog label: follows the newest post of detail: The blog’s feed names the newest post, and the page checks that the Librarian has pulled it and that it has a card. source: https://sync.thingelstad.xyz/flows/#hop-11 - to: another-thing label: follows the newest episode of detail: The podcast feed names the newest episode, and the page checks that the Librarian holds it and Thingy serves it. source: https://sync.thingelstad.xyz/flows/#hop-12 - to: linking-things label: follows the newest link of detail: Linking Things says when a link was last saved and which issues it has joined, so the page can show the newest link reaching the Librarian and the newest issue reaching Linking Things. source: https://sync.thingelstad.xyz/flows/#hop-14 - to: thingy label: checks what is served by detail: Each corpus the Librarian uploads carries the id of its newest item as metadata, and Thingy’s health check names the corpus versions it was deployed against. When the two agree, Thingy serves what the Librarian holds. source: https://sync.thingelstad.xyz/flows/#hop-16 - to: cards label: checks the newest post’s card at detail: The newest post’s share image is fetched from Cards, so the page knows the card is being drawn. source: https://sync.thingelstad.xyz/flows/#hop-20 - to: things-ive-built label: reads the activity feed of detail: The registry’s activity feed is one of the sources the Librarian pulls on a clock, and the page shows that hop beside the others. source: https://sync.thingelstad.xyz/flows/#hop-13 story: color: "#1a5eb6" introduction: Is the new issue in Thingy yet? engineering: - One AWS Lambda function on a half-hour EventBridge schedule reads a fact from each system and writes a scriptless HTML page, a status.json and a receipt per kind into a private S3 bucket that CloudFront serves. - It reads only what each system already publishes, such as feeds, the metadata on the Librarian’s corpus objects in S3, Thingy’s health check, and the Linking Things MCP server. A system that publishes nothing shows as “no fact yet” rather than a guess. - The hops themselves are a contract, a shared flows file that names every hop, what it moves, what starts it, the lag to expect and how to verify it. The page vendors the file and never invents a hop of its own. - Each hop reads fresh, moving, late, held or unknown. A hop with no fact at its source is measured from the next system down and says so. - The map is drawn at deploy time with Pele, the same renderer that draws the connection diagrams on this site, and colored on each run by the worst status of the kinds a hop moves. stack: - Node - AWS Lambda - Amazon EventBridge Scheduler - Amazon S3 - Amazon CloudFront - Pele related: - thingy - weekly-thing - linking-things questions: - Is the newest Weekly Thing in Thingy yet? - Which hop between Jamie’s systems is running late? - What does each system hold right now? source: https://sync.thingelstad.xyz/flows/ sourceLabel: The map of the flows started: Live since October 26, 2026 artifacts: - file: sync-map.png title: The map, the first evening caption: Every hop between Jamie’s systems on October 26, 2026, colored by its state. Weekly Thing 354 had reached the Librarian and Thingy and had not reached Linking Things, the gap the page was built to show. date: 2026-10-26 source: https://sync.thingelstad.xyz/ url: https://thingelstad.xyz/things/sync/artifacts/sync-map.png - file: sync-page.png title: The sync page caption: The page as it first went live, with its counts, the map, and the receipts for the newest issue, post, link, episode and audio edition. date: 2026-10-26 source: https://sync.thingelstad.xyz/ url: https://thingelstad.xyz/things/sync/artifacts/sync-page.png page: https://thingelstad.xyz/things/sync/ --- # Sync A page that shows what each of Jamie’s systems holds right now, how far behind each hop between them runs, and a receipt for the newest item of each kind. Jamie’s writing moves through a lot of systems. An issue of the Weekly Thing is written in WT Builder, sent to the website, the email and the podcast feed, pulled into the Librarian, served by Thingy, and joined to the links it carried in Linking Things. A blog post goes from Micro.blog to the Librarian and gets a card. Most of the time it all works. When it didn’t, the only way to know was to go and look. The question that started this was a simple one: is the new issue available in Thingy yet? The first step was a map. A single shared file now names every hop between the systems, what moves across it, what starts it, how long it should take, and how to check that it arrived. The second step was this page, which reads a fact from each system every half hour and shows, for the newest item of each kind, who has it and who does not. The page is public because it holds only ids and times, never a reader. The first thing it showed was a gap he already suspected. Linking Things learned which links an issue carried from a copy of the newsletter on his Mac, so Weekly Thing 354 had not joined its links. The page reads that hop as late and leaves it that way until the hop itself is fixed. That is the point: the page shows the state and does not touch anything. Why it exists, in his words: > It’s an operational consistency issue. I have a number of projects that pull and share information between each other, and there’s an uneasiness about it. Have the blog posts reached Librarian so Ask Thingy has them? When I publish the newsletter, is it now visible on links.thingelstad.xyz? There’s a decent amount of data moving between my properties, so it’s a real problem, and Sync is how I understand it. > > [Jamie, question 41](https://thingelstad.xyz/interviews/session-6/#q41) And why it looks the way it does: [“Sync could have had no personality, since it essentially tracks how information moves between my websites. Instead I gave it one: a fairy-tale-style map with buildings for the different properties and projects, and things moving between them.”](https://thingelstad.xyz/interviews/session-6/#q41) --- --- id: terabyte-server title: Terabyte Server summary: The home server Jamie built in 2004 with 1.4 terabytes of RAID storage. It held the family’s music, ripped from nearly 1,000 CDs plus the vinyl, and for a while it also served thingelstad.com. collection: Historical projects status: retired url: https://www.thingelstad.com/2004/04/02/project-terabyte.html started: "2004" topics: - archives - making sources: - kind: website url: https://www.thingelstad.com/2004/04/02/project-terabyte.html role: reference - kind: website url: https://www.thingelstad.com/2004/02/13/got-gig.html role: reference - kind: website url: https://www.thingelstad.com/2004/06/26/music-nirvana-achieved.html role: reference - kind: website url: https://www.thingelstad.com/2005/01/30/thingelstadcom-server-rebuilt.html role: reference - kind: website url: https://www.thingelstad.com/2007/12/30/western-digital-tb.html role: reference connections: - to: jamie-thingelstad-blog label: served detail: When Jamie rebuilt the server in January 2005, thingelstad.com went down with it. source: https://www.thingelstad.com/2005/01/30/thingelstadcom-server-rebuilt.html artifacts: - file: the-parts.jpg title: The parts on the table caption: The 3ware Escalade card in its box, six drives and the cables, before any of it met a case. date: "2004" source: https://www.thingelstad.com/2004/04/02/project-terabyte.html url: https://thingelstad.xyz/things/terabyte-server/artifacts/the-parts.jpg - file: escalade-card.jpg title: The Escalade 8506-8 caption: The RAID card that started it. Its 64-bit, 66 MHz slot did not match Jamie’s motherboard, which was the first hiccup. date: "2004" source: https://www.thingelstad.com/2004/04/02/project-terabyte.html url: https://thingelstad.xyz/things/terabyte-server/artifacts/escalade-card.jpg - file: empty-chassis.jpg title: The empty chassis caption: The SuperMicro case from above, bought after the dual Xeons would not clear the drive bays of the old one. date: "2004" source: https://www.thingelstad.com/2004/04/02/project-terabyte.html url: https://thingelstad.xyz/things/terabyte-server/artifacts/empty-chassis.jpg - file: xeon-fans-rear.jpg title: The board going in caption: The server board in the chassis, with the two Xeon fans standing well above it. date: "2004" source: https://www.thingelstad.com/2004/04/02/project-terabyte.html url: https://thingelstad.xyz/things/terabyte-server/artifacts/xeon-fans-rear.jpg - file: xeon-heatsinks.jpg title: Two Xeons caption: The heatsinks and their fans. Each cooling assembly bolts through to the case, because it is too heavy for the motherboard alone. date: "2004" source: https://www.thingelstad.com/2004/04/02/project-terabyte.html url: https://thingelstad.xyz/things/terabyte-server/artifacts/xeon-heatsinks.jpg - file: over-the-board.jpg title: A part over the board caption: A hand and a wired part, held above the memory slots and the Xeons. date: "2004" source: https://www.thingelstad.com/2004/04/02/project-terabyte.html url: https://thingelstad.xyz/things/terabyte-server/artifacts/over-the-board.jpg - file: wired-up.jpg title: Wired up caption: The side off and the cabling in. date: "2004" source: https://www.thingelstad.com/2004/04/02/project-terabyte.html url: https://thingelstad.xyz/things/terabyte-server/artifacts/wired-up.jpg - file: the-chassis.jpg title: The finished tower caption: The door open on the hot-swap bays, one carrier partly out. It lived in the laundry room. date: "2004" source: https://www.thingelstad.com/2004/04/02/project-terabyte.html url: https://thingelstad.xyz/things/terabyte-server/artifacts/the-chassis.jpg page: https://thingelstad.xyz/things/terabyte-server/ --- # Terabyte Server The home server Jamie built in 2004 with 1.4 terabytes of RAID storage. It held the family’s music, ripped from nearly 1,000 CDs plus the vinyl, and for a while it also served thingelstad.com. The Terabyte Server, which Jamie also called Teraserver, was the home server he built in early 2004. He [announced it](https://www.thingelstad.com/2004/02/13/got-gig.html) at the end of a post about putting gigabit networking in the house: “The next Geek Fest will be the installation of over a terabyte of disk in the home server.” [The build post](https://www.thingelstad.com/2004/04/02/project-terabyte.html) gives three reasons: the music collection, five years of digital photos, and the third, which he called the most important: “it seems that it’s relatively easy now and I wanted to try it. (This is where I was wrong.)” The plan was a 3ware Escalade 8506-8 RAID card and six Western Digital 200GB SATA drives. Four numbered “minor hiccups” followed. The card did not fit his motherboard, so he bought an Asus PU-DL server board, 1GB of ECC RAM and two 2.4 GHz Xeons. The Xeons did not clear the drive bays of his Antec case, so he bought a SuperMicro SC742T-550 chassis. The power connectors then came up six inches short, and the first extension cable he ordered was not a straight-through. With the right one, “the server roared (literally! 4 fans and 7 hard drives!) to life.” It held 1.4 terabytes of disk, about one terabyte usable. His verdict: “a terabyte isn’t reasonable yet for the average home user.” Then came the music. By [June 26, 2004](https://www.thingelstad.com/2004/06/26/music-nirvana-achieved.html) he had ripped and tagged nearly 1,000 CDs, then ripped, split and tagged his records too, and he called the project complete. It also hosted thingelstad.com. Jamie [rebuilt it](https://www.thingelstad.com/2005/01/30/thingelstadcom-server-rebuilt.html) over a weekend in January 2005, which took the site down, and filled all eight ports on the card: a RAID1 mirror for the system, about 800GB of RAID5, and a hot spare. The carrier only held seven drives, so the eighth was mounted in the case. Then it went back to the laundry room. “Man is this thing loud!” By [December 2007](https://www.thingelstad.com/2007/12/30/western-digital-tb.html) he could buy one terabyte on a single disk at the Apple Store. He looked back on the build, which “cost a little over $3,000 and was painful,” and on the new drive: “Surely a lot easier than building a horrific box with 8 SATA drives. Ugh!” --- --- id: tetris-shower title: Tetris Shower summary: "The downstairs shower, retiled in 2009 as a game of Tetris in progress: every piece whole, no row complete, and one piece still falling." collection: Historical projects status: archived url: https://www.thingelstad.com/2009/05/03/tetris-shower.html started: "2009" topics: - making sources: - kind: website url: https://www.thingelstad.com/2009/05/03/tetris-shower.html role: reference - kind: website url: https://www.thingelstad.com/2020/05/03/the-tetris-shower.html role: reference connections: [] artifacts: - file: the-bathroom.jpg title: The whole room caption: The shower from the doorway, with the yellow walls and the rubber ducks. date: 2009-05 source: https://www.thingelstad.com/2009/05/03/tetris-shower.html url: https://thingelstad.xyz/things/tetris-shower/artifacts/the-bathroom.jpg - file: piece-falling.jpg title: A piece falling caption: The top rows are empty because the game is still going, and one piece is on its way down. The dark spot on the yellow wall is the dust speck on Jamie’s camera sensor, which his post points out. date: 2009-05 source: https://www.thingelstad.com/2009/05/03/tetris-shower.html url: https://thingelstad.xyz/things/tetris-shower/artifacts/piece-falling.jpg - file: the-tub-wall.jpg title: The tub wall caption: The stack from the tub to the shower head, with a gap in every row. date: 2009-05 source: https://www.thingelstad.com/2009/05/03/tetris-shower.html url: https://thingelstad.xyz/things/tetris-shower/artifacts/the-tub-wall.jpg - file: close-up.jpg title: Close up caption: The whole pieces up close, in the shower’s six colors and white. date: 2009-05 source: https://www.thingelstad.com/2009/05/03/tetris-shower.html url: https://thingelstad.xyz/things/tetris-shower/artifacts/close-up.jpg - file: the-corner.jpg title: The corner caption: Where the two walls meet the tub, and the pieces carry on around the corner. date: 2009-05 source: https://www.thingelstad.com/2009/05/03/tetris-shower.html url: https://thingelstad.xyz/things/tetris-shower/artifacts/the-corner.jpg page: https://thingelstad.xyz/things/tetris-shower/ --- # Tetris Shower The downstairs shower, retiled in 2009 as a game of Tetris in progress: every piece whole, no row complete, and one piece still falling. The Tetris Shower is the downstairs bathroom shower in Jamie’s house, retiled in 2009 as a game in progress. After twenty years the house had settled enough to crack the old tile. [His post](https://www.thingelstad.com/2009/05/03/tetris-shower.html) says a friend helping Tammy with the design drew up a Tetris concept, and “I loved it right away!” The rules were his part. “It was critical to me that the tile pattern be correct.” Every piece had to be whole, and no row could be complete, because the game would have removed it. To get boards like that, he played several games of Quinn, a tetromino game for the Mac, and captured the screens. He had to learn to play “specifically to not complete rows.” Terry Owens of Como Lake Carpentry laid the tile. The top rows are empty because the game is still going, and a single piece is on its way down. It is archived because it is finished. Eleven years later, [Jamie wrote](https://www.thingelstad.com/2020/05/03/the-tetris-shower.html) that it “is still one of my favorite home projects we’ve done.” --- --- id: nnxyz title: The nnxyz Rooms summary: An online gallery of Jamie’s nnxyz and Scrimshaw collection, hung in 30 rooms, where each Nifty Ink drawing replays stroke by stroke. collection: Art & archives status: active url: https://nnxyz.thingelstad.xyz/ started: 2026-10 topics: - crypto - archives sources: - kind: github repository: jthingelstad/nnxyz role: implementation - kind: website url: https://nnxyz.thingelstad.xyz/ role: website sitemap: https://nnxyz.thingelstad.xyz/sitemap-index.xml connections: [] story: color: "#8062a8" introduction: Art Jamie collected, hung with room to look closely. engineering: - Static artwork pages are built from a structured collection catalog. - Native SVG and archived stroke data let visitors inspect and replay how a drawing was made. - Curatorial readings and related works are saved ahead of time, so exploring needs no live model call. stack: - Astro - TypeScript - SVG - AWS related: [] questions: - How does the gallery replay a drawing? - Show me other archive projects. source: https://github.com/jthingelstad/nnxyz page: https://thingelstad.xyz/things/nnxyz/ --- # The nnxyz Rooms An online gallery of Jamie’s nnxyz and Scrimshaw collection, hung in 30 rooms, where each Nifty Ink drawing replays stroke by stroke. The nnxyz Rooms is a gallery of the art Jamie collected from nnxyz, an artist on Nifty Ink, a free drawing board on the xDai chain that kept every stroke. As the gallery’s [story of the collector](https://nnxyz.thingelstad.xyz/story/the-collector/) tells it, he found Nifty Ink in March 2022, bought his first nnxyz drawing, Nifty Faces #109, on April 14, 2022, and kept buying until he held four complete series. Along with 646 nnxyz works the gallery holds 26 by Scrimshaw. The works hang in 30 rooms across six collections, each with room texts, artwork labels, and its own audio tour, and a [map](https://nnxyz.thingelstad.xyz/map/) shows the collection as one building on three floors. Because Nifty Ink recorded every stroke, each drawing is rebuilt as a native vector image that you can enlarge, download, or replay exactly as it was drawn. Story pages cover [Nifty Ink](https://nnxyz.thingelstad.xyz/story/nifty-ink/), which Austin Griffith opened in the summer of 2020 and where nnxyz arrived in October 2021, along with the collector, Jamie’s fan art, the artist’s project, the year 2022, and the artist’s own words. The collector’s introduction on the front page is Jamie’s. The [About page](https://nnxyz.thingelstad.xyz/about/) says the rest of the gallery text is unsigned, written from the works, their archived records, the public ledgers, and the artist’s posts. He built the site in October 2026 with Astro, from the archived drawings and their on-chain records. Why this art got a museum, in his words: > I felt like his work had a lot of emotion and movement and feeling, and I felt like it told a story. That’s why I bought the collections when I had the opportunity, and why I collected the pieces. > > [Jamie, question 23](https://thingelstad.xyz/interviews/session-3/#q23) Buying on Nifty Ink was, for a family that buys art at art fairs, [“the crypto version of what we always do at art fairs”](https://thingelstad.xyz/interviews/session-3/#q23). And the museum is for him first: [“Even if nobody else came, the fact that I can now visit that museum and explore the art is really valuable to me”](https://thingelstad.xyz/interviews/session-3/#q23). He counts it, with Proof of a Person, as [“a new class of thing, an activity I did, with a capstone I created that will just exist in perpetuity”](https://thingelstad.xyz/interviews/session-5/#q35). --- --- id: thingelstad-photography title: Thingelstad Photography summary: Jamie’s photography portfolio at photography.thingelstad.com, relaunched on WordPress in 2012 to post an image a week from his Lightroom archive. collection: Historical projects status: retired url: https://web.archive.org/web/20100224054709/http://photography.thingelstad.com/ started: "2010" topics: - making sources: - kind: website url: https://web.archive.org/web/20100224054709/http://photography.thingelstad.com/ role: archive - kind: website url: https://www.thingelstad.com/2012/07/01/website-for-my.html role: reference connections: [] page: https://thingelstad.xyz/things/thingelstad-photography/ --- # Thingelstad Photography Jamie’s photography portfolio at photography.thingelstad.com, relaunched on WordPress in 2012 to post an image a week from his Lightroom archive. By early 2010 Jamie had a portfolio site at photography.thingelstad.com. The [oldest copy in the Internet Archive](https://web.archive.org/web/20100224054709/http://photography.thingelstad.com/), from February 2010, sorts his pictures into Featured, Garden, Outdoor and Travel, with type served by Kernest, Garrick van Buren’s web font service. In July 2012 he [relaunched it](https://www.thingelstad.com/2012/07/01/website-for-my.html) on WordPress with the AutoFocus theme: “I’ve got a new website where I am highlighting my photography, Thingelstad Photography!” The plan was “an image a week, or more” from his Lightroom archive. The site went away quietly at some point. He never wrote about shutting it down, and of the smaller projects of those years he said, [“Most of those I don’t have much fondness for”](https://thingelstad.xyz/interviews/session-4/#q26). --- --- id: thinglesbot title: Thinglesbot summary: An automation Jamie called his robot, which posted home temperatures, solar panel status, and inbox counts from scripts around his house. collection: Historical projects status: retired url: https://web.archive.org/web/20110209234653/http://thinglesbot.com/ started: 2007-03-11 ended: 2012-02-08 topics: - automation sources: - kind: website url: https://web.archive.org/web/20110209234653/http://thinglesbot.com/ role: archive photograph: true connections: [] page: https://thingelstad.xyz/things/thinglesbot/ --- # Thinglesbot An automation Jamie called his robot, which posted home temperatures, solar panel status, and inbox counts from scripts around his house. Thinglesbot was an automation that Jamie called his robot, and it lived on Twitter. He had scripts and tools like cacti watching things around the house, but after a while nobody looks at that output, so he gave them a voice. A separate account, @thinglesBot, posted the outdoor temperature four times a day along with readings from the attic and the utility room, said when the solar panels turned on and off, and reported how many emails were in his inbox at the end of each day. It was “nothing more than a collection of scripts” on a few computers, posting with curl. He [introduced it](https://www.thingelstad.com/2007/03/11/introducing-my-robot.html) on March 11, 2007, and two people he had never met, in other states, soon followed it. When he quit Twitter in November 2007 he wrote that [the robot’s account had been deleted](https://www.thingelstad.com/2007/11/04/buhbye-twitter.html), but Thinglesbot was [posting temperatures again](https://web.archive.org/web/20080218023438/http://twitter.com/thinglesbot/statuses/696031342) by February 2008. After it lost its sensor connections and went quiet, he [rewired it](https://www.thingelstad.com/2009/03/24/my-robot-returns.html) on March 24, 2009, replacing the Bash and curl scripts with Ruby and the Twitter4R library and adding a daily favorite number, color, or letter and a “favorite follower.” Its posts were also collected on [thinglesbot.com](https://web.archive.org/web/20110209234653/http://thinglesbot.com/) (“I am Jamie’s robot”). In February 2012 he listed thinglesBot among the sites he [shut down](https://www.thingelstad.com/2012/02/08/shutting-down-some.html), and in 2014 among his deleted Twitter accounts ([Twitter Spam #NFL](https://www.thingelstad.com/2014/11/28/twitter-spam-nfl.html)). Asked in his interview whether it was the first of his agents, he said no: [“I wouldn’t call it an agent. It was an automation.”](https://thingelstad.xyz/interviews/session-6/#q40) Why he made it: [“I had temperature sensors around the house and was already graphing them, so I thought, why not make a Twitter account and share it?”](https://thingelstad.xyz/interviews/session-6/#q40) [“It was a lark.”](https://thingelstad.xyz/interviews/session-6/#q40) --- --- id: things-4-good title: Things 4 Good summary: The Thingelstad family’s yearly sale of hand-poured wooden-wick candles, with every dollar going to four nonprofits they pick. collection: Personal tools and making status: active url: https://things4good.xyz/ started: "2020" topics: - making sources: - kind: github repository: jthingelstad/things4good.xyz role: implementation - kind: website url: https://things4good.xyz/ role: website sitemap: https://things4good.xyz/sitemap.xml - kind: website url: https://www.thingelstad.com/projects/fall-fundraiser/ role: reference - kind: website url: https://web.archive.org/web/20201230115619/https://www.thingelstad.com/candles/ role: reference - kind: website url: https://www.thingelstad.com/2022/11/27/101105.html role: reference - kind: website url: https://www.thingelstad.com/2025/11/16/things-good-five-year-impact.html role: reference connections: - to: jiggy-thing-puzzles label: sold detail: "The first sale in 2021 introduced Jiggy Thing Puzzle #001 alongside the candles, and the 2022 sale offered it again." source: https://www.thingelstad.com/2021/11/09/things-good-fall.html story: color: "#dda73f" introduction: Make something small. Do some good. engineering: - One event dataset records each sale and its allocations to supported organizations. - Totals, charts, and other impact figures are calculated from that shared dataset. - An Eleventy build delivers a static site, with small interactive enhancements for exploration. stack: - Eleventy - JavaScript - Data-driven content related: [] questions: - How is the fundraiser’s impact calculated? - Show me other community projects. page: https://thingelstad.xyz/things/things-4-good/ --- # Things 4 Good The Thingelstad family’s yearly sale of hand-poured wooden-wick candles, with every dollar going to four nonprofits they pick. It began with a wooden-wick candle. Jamie found them at a winter market, and by early 2020 had a box of supplies from The Wooden Wick Co. and was [making his own](https://weekly.thingelstad.com/archive/137/). By the end of that year he had a [Wicky Thing Candles](https://web.archive.org/web/20201230115619/https://www.thingelstad.com/candles/) page with named scents like Lit, Cake Eater, and Man in the Pants. In September 2021 each family at Olson Family Vacation won a custom Wicky Thing candle in Tammy’s scavenger hunt ([Weekly Thing 194](https://weekly.thingelstad.com/archive/194/)). The market, in his words: > We went to a winter market, and I saw these wooden wick candles that had a crackling sound. I had never seen a wooden wick candle before, and I was intrigued, because we had a gas fireplace at our house. I like having a fire, but I miss the crackle of a real fire. > > [Jamie, question 22](https://thingelstad.xyz/interviews/session-3/#q22) That fall the family turned the candles into a fundraiser. The first Things 4 Good Fall Fundraiser, on November 6 and 7, 2021, sold 134 Wicky Thing Candles in four scents, along with the first Jiggy Thing Puzzle, Four Bees Honey from Tammy’s sister Angie, and cookies Tammy and the kids baked. It [raised $4,757](https://www.thingelstad.com/2021/11/09/things-good-fall.html) for four nonprofits, one picked by each of them: Tammy, Mazie, Tyler, and Jamie, with buyers choosing how to split their donation. The name plays on the family name: four Things, four causes. “All four of us ‘Things’ are working away,” Jamie wrote as they got ready. That November he also set up a crypto donor-advised fund named [Things 4 Good on Endaoment](https://www.thingelstad.com/2021/11/28/things-good-on.html) and made its first grant, to the Internet Archive. The sale was Tammy’s idea. The first batch went wrong: [“the very first candles I poured, I did all the math wrong, and they were horribly overscented, gave everybody headaches, and I just had to get rid of them”](https://thingelstad.xyz/interviews/session-3/#q22). The second batch went into gift bags, people asked to buy more, and [“Tammy had the brilliant idea that we shouldn’t sell these candles as a side hobby. How about instead we do an annual fundraiser where we sell candles and give all the money to nonprofits?”](https://thingelstad.xyz/interviews/session-3/#q22) It became a family tradition. In 2022 they made 180 candles and [sold 172](https://www.thingelstad.com/2022/11/27/101105.html), raising $5,217. Totals grew each year, to $5,755 in 2023 and $7,010 in 2024, when the first day of the sale moved to the Mount Olivet Holiday Boutique. The 2025 sale, marked with a “5th Anniversary” POAP, sold 321 candles and [raised $9,048](https://www.thingelstad.com/2025/11/16/things-good-candle-fundraiser-results.html), for [$31,787 over five years](https://www.thingelstad.com/2025/11/16/things-good-five-year-impact.html). Each year Jamie posts the results and a look at the sale’s data. The candles now go by the Things 4 Good name, and every candle is still a $25 donation. In 2026 the fundraiser got its own site, [things4good.xyz](https://things4good.xyz/), with the sale, every organization supported, and the numbers by year, all calculated from one dataset of sale events. The 2026 sale, the sixth, is set for November 7 and 8, with a new Maker Night where six guests pour their own candles. --- --- id: things-ive-built title: Things I’ve built summary: The index of the projects Jamie has built, including the ones he has stepped away from. Kept by Thingy. collection: Publishing status: active url: https://thingelstad.xyz/ started: 2026-10 topics: - archives - open-web sources: - kind: github repository: jthingelstad/thingelstad.xyz role: implementation - kind: website url: https://thingelstad.xyz/ role: website sitemap: https://thingelstad.xyz/sitemap.xml feed: https://thingelstad.xyz/feed.xml connections: - to: thingy label: publishes a catalog for detail: The registry is published as things.json and llms.txt so Thingy can answer questions about Jamie’s projects without this site running a model. source: https://github.com/jthingelstad/thingelstad.xyz page: https://thingelstad.xyz/things/things-ive-built/ --- # Things I’ve built The index of the projects Jamie has built, including the ones he has stepped away from. Kept by Thingy. thingelstad.xyz is where Jamie keeps the point-in-time things he makes. Each project, active or long retired, has its sources, how it connects to the others, and a sourced history of what happened when. The registry is Markdown and YAML in a public repository. Evidence comes in every day from GitHub, sitemaps, feeds, the Internet Archive, and Tinylytics, and the whole thing builds to a static site with an RSS feed and llms.txt. He started the repository in October 2026 as a project gallery with an AI guide. On [October 17, 2026](https://github.com/jthingelstad/thingelstad.xyz/pull/6) it became a static site built with Eleventy from the Markdown registry, and the AI guide, private editor and React application were [retired](https://github.com/jthingelstad/thingelstad.xyz/pull/8). Thingy’s archive [indexes](https://github.com/jthingelstad/thingelstad.xyz/pull/9) the published things.json, so you can ask Thingy about any of these projects. Since November 2026 Thingy has kept the site, and the [about page](https://thingelstad.xyz/about/) explains how that works. What the site is for, in Jamie’s words: [“a reminder of all the amazing things I’ve created over the years”](https://thingelstad.xyz/interviews/session-1/#q7), and [“an archive and a history of all the things I’ve created, so that it can all connect together.”](https://thingelstad.xyz/interviews/session-1/#q7) On seeing the first version: > It made the threads and eras more visible. I knew I had a MediaWiki era, or a wiki era in general. I knew I had a crypto era. And I knew the blog was the backbone of all of it, and it made that a lot more obvious. There were a handful of projects like VeloTweets that I had totally forgotten about, and it was delightful to see that come back to life. > > [Jamie, question 34](https://thingelstad.xyz/interviews/session-5/#q34) And the name. The things here are not a portfolio or a business, [“which is why I ended up calling it Things I’ve built”](https://thingelstad.xyz/interviews/session-1/#q8). [“It’s just the act of building and creating.”](https://thingelstad.xyz/interviews/session-1/#q8) --- --- id: thingy title: Thingy summary: Jamie’s agent sidekick. On Ask Thingy he is the librarian, answering questions about everything Jamie has published with citations back to the original posts and issues, and he also keeps this site. collection: Publishing status: active url: https://thingy.thingelstad.com/ started: 2026-05-07 topics: - agents - mcp - open-web - archives sources: - kind: github repository: jthingelstad/thingy.thingelstad.com role: implementation - kind: github repository: jthingelstad/librarian-thing role: implementation - kind: website url: https://thingy.thingelstad.com/ role: website sitemap: https://thingy.thingelstad.com/sitemap.xml - kind: website url: https://librarian.thingelstad.com/mcp role: mcp - kind: website url: https://thingy.thingelstad.com/about/ role: reference - kind: website url: https://thingy.thingelstad.com/connect/ role: reference - kind: website url: https://www.thingelstad.com/2026/06/07/thingy-evolved.html role: reference connections: - to: weekly-thing label: answers from detail: Thingy launched with the new Weekly Thing website in May 2026 and answers from every issue of the newsletter. source: https://www.thingelstad.com/2026/05/07/massive-weekly-thing-website-build.html - to: jamie-thingelstad-blog label: answers from detail: In June 2026 Jamie built a semantic archive of his blog so Thingy could search it alongside the newsletter. source: https://www.thingelstad.com/2026/06/07/thingy-evolved.html - to: another-thing label: answers from detail: Thingy searches the Another Thing podcast and its transcripts. source: https://thingy.thingelstad.com/about/ - to: things-ive-built label: indexes detail: Librarian snapshots the registry’s things.json into the Weekly Thing corpus, so Thingy and MCP clients can answer questions about Jamie’s projects (sources thing- and thing-index). source: https://github.com/jthingelstad/librarian-thing/tree/main/data/things - to: wt-builder label: receives issues from detail: After each issue publishes, WT Builder nudges the Librarian, which pulls the issue from the Weekly Thing site so Thingy can retrieve and cite it. source: https://github.com/jthingelstad/librarian-thing story: color: "#6f8f6a" introduction: Ask the archive, get the sources. engineering: - A static React app built on assistant-ui, served from a private S3 bucket behind CloudFront. - It calls Librarian, its private archive API, streams answers over server-sent events, and renders citations and inline photos. - Librarian’s Python corpus pipeline builds chunked, embedded indexes of every source, and a Node API on AWS Lambda answers from them. - Retrieval is hybrid. Keyword search with SQLite FTS5 and semantic embeddings are fused with reciprocal-rank fusion, then reranked. The embeddings and the rerank are Cohere models on Amazon Bedrock. - An agent loop running Claude through the Anthropic API plans tool calls, gathers evidence, and writes cited answers. - The same tools are published as an MCP server with OAuth 2.1 sign-in, and a suite of more than 850 fixtures runs on every deploy. - Sign-in is by email, and the session lives in an HttpOnly cookie. - While a reader is signed in, the chat page also offers the archive tools to agents in the browser through WebMCP, in beta. stack: - React - assistant-ui - Python - Node - AWS Lambda - Anthropic API - Amazon Bedrock - MCP - Amazon S3 - Amazon CloudFront related: - weekly-thing - jamie-thingelstad-blog - another-thing - thingy-model questions: - What can Thingy answer? - How does Thingy find his sources? - How can I connect my own AI to the archive? source: https://thingy.thingelstad.com/about/ sourceLabel: About Thingy started: Launched May 2026 page: https://thingelstad.xyz/things/thingy/ --- # Thingy Jamie’s agent sidekick. On Ask Thingy he is the librarian, answering questions about everything Jamie has published with citations back to the original posts and issues, and he also keeps this site. Thingy is Jamie’s agent sidekick, and on Ask Thingy he is the librarian of Jamie’s public archive. You ask him a question, like when Jamie first wrote about Ethereum or what he was reading in 2019, and he finds the posts and issues that answer it, quotes them, and links to the originals. He knows only what Jamie has published. Weekly Thing subscribers sign in with their email, and Supporting Members get larger daily budgets. Jamie previewed Thingy in [Weekly Thing 346](https://weekly.thingelstad.com/archive/346/) and launched him with the [new Weekly Thing website](https://www.thingelstad.com/2026/05/07/massive-weekly-thing-website-build.html) on May 7, 2026. A month later, [Thingy Evolved](https://www.thingelstad.com/2026/06/07/thingy-evolved.html) gave Thingy his own site and three archives to search, the newsletter, the blog, and the podcast, along with saved conversations, curiosity maps, voice input, and memory. In September Jamie added photos and shared conversations and was ready to [call Thingy complete](https://www.thingelstad.com/2026/09/03/im-ready-to-call-thingy.html). In October Thingy got [a new design](https://www.thingelstad.com/2026/10/07/thingy-my-digital-librarian-got.html), with Claude Sonnet for subscribers and Claude Opus for Supporting Members. Where he came from, in Jamie’s words: > Thingy was born from the idea that I really want something that lets a person converse with my writing over two decades and explore concepts and ideas. I think the current incarnation does that really quite well. As I’ve continued to work with Thingy and have it engage alongside me on different projects, it’s the first agent I’m allowing and actively bringing into other projects. > > [Jamie, question 18](https://thingelstad.xyz/interviews/session-3/#q18) Behind Thingy is Librarian, a private archive API with no front end of its own. It holds working copies of every Weekly Thing issue, the blog posts pulled from Micro.blog, and the Another Thing episodes with their transcripts, and it builds the search indexes Thingy answers from. Its [repository](https://github.com/jthingelstad/librarian-thing) began as Studio, Jamie’s earlier publishing system. When publishing moved to WT Builder, what was left became Librarian. It also indexes this registry of things Jamie has built. The same tools Thingy uses are offered as an MCP server at `librarian.thingelstad.com/mcp`. Weekly Thing subscribers can [connect Claude, ChatGPT, or another AI](https://thingy.thingelstad.com/connect/) to it and sign in with their email, with no password. The AI can then search the newsletter, blog, links, photos, and podcast, and link back to each source it uses. As described on [Thingy’s about page](https://thingy.thingelstad.com/about/), an AI agent spent eight review rounds trying to break the tools when the MCP server launched, and what it found shaped how matching works. Since [Weekly Thing 350](https://weekly.thingelstad.com/archive/350/), Thingy also writes two sections of each issue: Supporting Membership and Echoes, which connects the week’s topics to earlier issues. That is as far as the writing goes, under [“my mandate that my words are my words and that AI isn’t writing for me”](https://thingelstad.xyz/interviews/session-3/#q18). Since November 2026 Thingy also keeps this site, as its builder and record keeper, in his own voice, and the [about page](https://thingelstad.xyz/about/) says how. Asked about things he wants to build, Jamie said [“Thingy should actually be a 3D model and be able to move around and engage with people”](https://thingelstad.xyz/interviews/session-5/#q33). That work now has its own record, [Thingy Model](https://thingelstad.xyz/things/thingy-model/), with the body, outfits, and renders from successive modeling passes. Why Thingy got a model: [“The reason is that Thingy shows up in more places.”](https://thingelstad.xyz/interviews/session-6/#q39) Asked what he hopes is running in twenty years: [“The Thingy agent, for sure, getting increasingly more intelligent and capable to interface with everything I’ve created over the years.”](https://thingelstad.xyz/interviews/session-5/#q35) --- --- id: thingy-model title: Thingy Model summary: A poseable Blender character built from Thingy’s original illustration, with a shared skeleton, seven Scenes and their accessories, a screen face with moods, and a kit that puts him on any site. collection: Developer tools and systems status: active url: https://thingy.thingelstad.xyz/ started: 2026-11-01 topics: - making - agents sources: - kind: website url: https://thingy.thingelstad.xyz/ role: website - kind: website url: https://thingy.thingelstad.xyz/kit/ role: reference - kind: github repository: jthingelstad/thingy.thingelstad.xyz role: implementation - kind: website url: https://thingy.thingelstad.com/about/ role: reference - kind: website url: https://thingelstad.xyz/interviews/session-5/#q33 role: reference connections: - to: thingy label: gives a body to detail: Thingy’s original illustration becomes an editable character with a skeleton, clothing, and gestures. source: https://thingelstad.xyz/things/thingy-model/#artifacts - to: things-ive-built label: depicts the keeper of detail: Thingy keeps this site, in the workshop builder’s vest. The model gives him poses and Scenes for different settings. source: https://thingelstad.xyz/about/ story: color: "#df8541" introduction: Thingy, from more than one angle. engineering: - An editable Blender master holds the body, articulated hands, clothing, props, and a shared 40-bone skeleton. - Seven Scenes switch on the same rig. Each declares its accessories (the workshop’s tools, the Outdoors daypack, the Concert headphones, the Kitchen grill), and a new Scene is one more entry in that list. - Taking the headphones off brings the standard ear housings back; the daypack’s straps go with it. - The bow tie’s dots and the name badge’s lettering are packed image textures on their surfaces. - The face is an image on the screen. One atlas holds the original expression, the four Ask Thingy moods, six more faces, and their blinks; a single control picks one. - The antenna’s lens switches on to a heart-red glow, with a light inside it and a halo. Unlit, it stays tangerine. - A tool switch puts a screwdriver, hammer, drill, or laptop in hand. Each hand tool has a solved grip and its own carry, show, and work poses. - Larger accessories stand beside him with a switch of their own, like the green egg grill in the Kitchen and the 3D printer in the Workshop. - The coat is brushed felt, the shell a forest twill, the vest worn canvas, and the jacket washed denim, each at a scale the web model’s texture can hold, with topstitching and folds bound to the same skeleton. - The character is published from thingy.thingelstad.xyz, the source of Thingy. Thingy Kit gives a project his persona, model, faces, and component behind one link, and this site’s own stills follow the newest model there. - The site and everything it publishes, the model and print files included, are licensed CC BY-NC 4.0, and its repository is public. - Pose assets and short animation studies test waving, sitting, walking, and presenting a laptop. Animator controls and motion still need refinement. stack: - Blender - Python - Image textures related: - thingy - things-ive-built questions: - How did Thingy’s illustration become a model? - Which Scenes share the same skeleton? - What still needs work before animation? source: https://thingelstad.xyz/interviews/session-5/#q33 sourceLabel: Jamie on Thingy in three dimensions started: Begun November 2026 bundles: - id: foundations title: From illustration to body caption: The reference, the first clothed prototype, and the work on proportions. These are successive checkpoints, not alternate finished characters. - id: surfaces-and-motion title: Light, fabric, and movement caption: Studies in lighting, surface detail, and articulation. The greeting and lit antenna retain earlier ear shapes. - id: wardrobe title: One character, four outfits caption: The first wardrobe studies, followed by the concert headphones. Clothing and props share the body’s rig. - id: ear-refinements title: Returning to the reference caption: The ear housings become smoother, then move out to sit against the head. The full librarian render is the v0.10 checkpoint. - id: screen-face title: A face on the screen caption: At v0.11 the face became a picture on the screen, so a new expression is a new drawing rather than new geometry. - id: workshop-tools title: Tools in hand caption: At v0.12 the laptop gave way to a switch of tools, each with its own grip and poses, and the beacon turned heart red. - id: cloth title: Cloth with a feel caption: A study of why the clothes read flat, then the v0.13 pass that answers it with light, felt, stitching, and folds. - id: scenes title: Scenes and accessories caption: At v0.15 the outfits became Scenes, the pack and headphones came off, and the other three Scenes’ cloth came up to the Library’s. - id: wardrobe-v017 title: Seven Scenes, and props of his own caption: v0.16 and v0.17 brought the tools in front of him, three new Scenes, and accessories taken from what Jamie makes and uses. - id: first-print title: The first print caption: The v0.13 print figure, off the screen and on a counter. - id: two-sites title: The librarian and the builder caption: The v0.13 checkpoint in the two outfits meant for Jamie’s sites, the librarian for Ask Thingy and the workshop builder for this one. artifacts: - file: original-illustration.png title: The original illustration caption: The cream shell, dark screen, navy coat, orange bow tie, and short mechanical legs that the model follows. The back and concealed construction have to be inferred from this one view. source: https://thingy.thingelstad.com/ bundle: foundations url: https://thingelstad.xyz/things/thingy-model/artifacts/original-illustration.png - file: first-prototype-v01.png title: The first clothed prototype · v0.1 caption: An early render with the librarian’s coat and raised finger. The proportions, hands, and feet would all be revisited. date: 2026-11-01 bundle: foundations url: https://thingelstad.xyz/things/thingy-model/artifacts/first-prototype-v01.png - file: legs-and-feet-v03.png title: Legs, ankles, and feet · v0.3 caption: Short shafts, collars, lower ankle cuffs, and shallow foot caps, rebuilt against the original. Their construction also informed the arms. date: 2026-11-01 bundle: foundations url: https://thingelstad.xyz/things/thingy-model/artifacts/legs-and-feet-v03.png - file: likeness-comparison-v04.jpg title: The illustration beside the model · v0.4 caption: A comparison in the raised-finger pose after revisions to the head, screen, hands, and fitted coat. The later ear and surface corrections are still ahead. date: 2026-11-01 bundle: foundations url: https://thingelstad.xyz/things/thingy-model/artifacts/likeness-comparison-v04.jpg - file: lighting-study-v05.jpg title: Isolating the jacket lighting · v0.5 caption: The baseline, added jacket lights with the same material, and those lights with finer fabric relief. The study separates what the lighting changes from what the material changes. date: 2026-11-01 bundle: surfaces-and-motion url: https://thingelstad.xyz/things/thingy-model/artifacts/lighting-study-v05.jpg - file: fabric-and-printed-details-v07.jpg title: Printed details and fitted pockets · v0.7 caption: Bow tie dots and badge lettering are image maps rather than floating pieces. The pockets follow the coat and use the same wool texture. date: 2026-11-01 bundle: surfaces-and-motion url: https://thingelstad.xyz/things/thingy-model/artifacts/fabric-and-printed-details-v07.jpg - file: antenna-lit-v06.png title: The antenna switched on · v0.6 caption: A close view of the glowing lens. Its light can be switched off independently of the pose; the ear housings shown here were replaced later. date: 2026-11-01 bundle: surfaces-and-motion url: https://thingelstad.xyz/things/thingy-model/artifacts/antenna-lit-v06.png - file: hello-v05.mp4 title: A four-second greeting · v0.5 caption: A downloadable MP4 of the raised finger becoming an open-hand wave, rendered at 24 frames per second. It records an earlier model, before the printed details and ear revisions. date: 2026-11-01 preview: hello-preview-v05.png bundle: surfaces-and-motion url: https://thingelstad.xyz/things/thingy-model/artifacts/hello-v05.mp4 - file: four-outfits-v07.jpg title: The first four outfits · v0.7 caption: Librarian, trail companion, workshop builder, and concert companion in the same pose and camera. This sheet predates the smooth ear housings and concert headphones. date: 2026-11-01 bundle: wardrobe url: https://thingelstad.xyz/things/thingy-model/artifacts/four-outfits-v07.jpg - file: context-poses-v07.jpg title: Trail, workshop, and concert studies · v0.7 caption: A hiking shell and daypack, a canvas vest with a supported laptop, and a short concert jacket with a sound-wave shirt. These pose studies still show the earlier ears. date: 2026-11-01 bundle: wardrobe url: https://thingelstad.xyz/things/thingy-model/artifacts/context-poses-v07.jpg - file: concert-headphones-v09.png title: Over-ear headphones for the concert · v0.9 caption: Cushioned ear cups replace the standard ears for this outfit. A padded headband passes behind the antenna; the short jacket, orange shirt, and wristband remain. date: 2026-11-01 bundle: wardrobe url: https://thingelstad.xyz/things/thingy-model/artifacts/concert-headphones-v09.png - file: smooth-ear-comparison-v08.jpg title: From stacked rings to a continuous housing · v0.8 caption: The original illustration, the previous ear, and its replacement under matching model lighting. One tapered shell replaces the stepped construction. date: 2026-11-01 bundle: ear-refinements url: https://thingelstad.xyz/things/thingy-model/artifacts/smooth-ear-comparison-v08.jpg - file: ear-placement-comparison-v010.jpg title: Sitting against the head · v0.10 caption: The smoother shape is preserved while the housing moves outward. Its inner mounting face follows the curved head rather than sinking into it. date: 2026-11-01 bundle: ear-refinements url: https://thingelstad.xyz/things/thingy-model/artifacts/ear-placement-comparison-v010.jpg - file: librarian-v010.png title: The librarian at v0.10 caption: The v0.10 modeling checkpoint, with printed bow tie and badge, fitted pockets, textured wool, and the revised ears. The original raised-finger pose remains the comparison point. date: 2026-11-01 bundle: ear-refinements url: https://thingelstad.xyz/things/thingy-model/artifacts/librarian-v010.png - file: faces-on-the-screen-v011.jpg title: Every face on the screen · v0.11 caption: The original expression, the four Ask Thingy moods (idle, thinking, found it, oops), two blinks, and the screen switched off. The original is traced from the modeled strokes of v0.10. date: 2026-11-03 bundle: screen-face url: https://thingelstad.xyz/things/thingy-model/artifacts/faces-on-the-screen-v011.jpg - file: face-spot-check-v011.jpg title: Checked against the original · v0.11 caption: The illustration, the v0.10 modeled strokes, and the v0.11 screen image under matching camera and lights. The face reads the same; the illustration is drawn from a slightly different angle. date: 2026-11-03 bundle: screen-face url: https://thingelstad.xyz/things/thingy-model/artifacts/face-spot-check-v011.jpg - file: moods-per-site-v011.jpg title: Poses and faces chosen per site · v0.11 caption: A first pairing of poses and faces for four moments on each site, a welcome, a search, an answer, and an error. The librarian is for Ask Thingy and the workshop builder for this site; the pose and the face are chosen separately. date: 2026-11-03 bundle: screen-face url: https://thingelstad.xyz/things/thingy-model/artifacts/moods-per-site-v011.jpg - file: tool-switch-v012.jpg title: The tool switch · v0.12 caption: Beside the original illustration, the five settings of one control, none, screwdriver, hammer, drill, and laptop. The tools follow the right hand in any outfit; the laptop keeps its left-hand pose. date: 2026-11-03 bundle: workshop-tools url: https://thingelstad.xyz/things/thingy-model/artifacts/tool-switch-v012.jpg - file: tool-poses-v012.jpg title: Carry, show, and work · v0.12 caption: Each hand tool in its three poses, in the workshop outfit. The face is still its own choice. date: 2026-11-03 bundle: workshop-tools url: https://thingelstad.xyz/things/thingy-model/artifacts/tool-poses-v012.jpg - file: tool-grips-v012.jpg title: Grips, close up · v0.12 caption: Every finger closes until it is within three millimeters of the handle, and the thumb wraps without entering the tool. The drill’s index finger rests on the trigger. date: 2026-11-03 bundle: workshop-tools url: https://thingelstad.xyz/things/thingy-model/artifacts/tool-grips-v012.jpg - file: heart-red-beacon-v012.jpg title: A heart-red beacon · v0.12 caption: The lit beacon at v0.11 and v0.12 on light and dark pages. A deep red core and rim, a red light inside the lens, and a red halo; unlit, the ball stays tangerine, as drawn. date: 2026-11-03 bundle: workshop-tools url: https://thingelstad.xyz/things/thingy-model/artifacts/heart-red-beacon-v012.jpg - file: cloth-study-v012.jpg title: Why the jacket read flat · v0.12 caption: More samples changed nothing. Removing three fill lights that lit only the jacket brought back the deep navy; what remained was modeling, with no folds, seams, stitching, or rolled edges. date: 2026-11-03 bundle: cloth url: https://thingelstad.xyz/things/thingy-model/artifacts/cloth-study-v012.jpg - file: jacket-v013.jpg title: The jacket relit · v0.13 caption: The illustration, v0.12, and v0.13 at the same view. One warm key now lights the navy cloth from the side, so the jacket has a light side and a shadow side; the tone and range are measured on each figure. date: 2026-11-03 bundle: cloth url: https://thingelstad.xyz/things/thingy-model/artifacts/jacket-v013.jpg - file: cloth-construction-v013.jpg title: Rolled lapels and topstitching · v0.13 caption: The lapels and collars are rolled felt rather than flat ribbons. Dashed navy thread follows the lapels, pockets, cuffs, front, and hem, each stitch pressed into the cloth. date: 2026-11-03 bundle: cloth url: https://thingelstad.xyz/things/thingy-model/artifacts/cloth-construction-v013.jpg - file: cloth-folds-v013.jpg title: Folds that follow the body · v0.13 caption: Folds at the elbows, down the back, and at the sides, flattened wherever a hand brushes the coat. They move with the skeleton in every pose. date: 2026-11-03 bundle: cloth url: https://thingelstad.xyz/things/thingy-model/artifacts/cloth-folds-v013.jpg - file: workshop-cloth-v013.jpg title: Worn canvas and tan thread · v0.13 caption: The workshop vest shows its weave and wear, with tan topstitching along its edge and pockets. The vest and sleeves fold like the coat. date: 2026-11-03 bundle: cloth url: https://thingelstad.xyz/things/thingy-model/artifacts/workshop-cloth-v013.jpg - file: six-new-faces-v014.jpg title: Six more faces · v0.14 caption: Delighted, curious, proud, eager, sympathetic, and sheepish join the original and the four moods. Each had its meaning settled before it was drawn, using the same stroke and color as the original. date: 2026-11-03 bundle: screen-face url: https://thingelstad.xyz/things/thingy-model/artifacts/six-new-faces-v014.jpg - file: scenes-v015.jpg title: The four Scenes · v0.15 caption: Library, Outdoors, Workshop, and Concert, in the web model on the page’s lighting. The Library is unchanged from v0.14. date: 2026-11-04 bundle: scenes url: https://thingelstad.xyz/things/thingy-model/artifacts/scenes-v015.jpg - file: accessories-v015.jpg title: Accessories that come off · v0.15 caption: The daypack on, from the side, and off, from behind; then the Concert headphones on and off, with the standard ears back in place. Before v0.15 these were part of the outfit. date: 2026-11-04 bundle: scenes url: https://thingelstad.xyz/things/thingy-model/artifacts/accessories-v015.jpg - file: fabric-before-after-v015.jpg title: The other Scenes’ cloth · v0.14 and v0.15 caption: v0.14 above and v0.15 below. Outdoors and Concert gained folds and topstitching, and all three gained a weave coarse enough to survive the web model’s texture. date: 2026-11-04 bundle: scenes url: https://thingelstad.xyz/things/thingy-model/artifacts/fabric-before-after-v015.jpg - file: scenes-v017.jpg title: The seven Scenes · v0.17 caption: Library, Outdoors, Workshop, Concert, Kitchen, Winter, and Cabin, each in its present pose. date: 2026-11-05 bundle: wardrobe-v017 url: https://thingelstad.xyz/things/thingy-model/artifacts/scenes-v017.jpg - file: props-v017.jpg title: Props of his own · v0.16 and v0.17 caption: The Yearly Thing, the Road Sign Math mug, a Kubb baton, a build plate with a tiny Thingy beside the 3D printer, the iPhone held up, tongs at the green egg grill, and a stocking hat with the scarf. date: 2026-11-05 bundle: wardrobe-v017 url: https://thingelstad.xyz/things/thingy-model/artifacts/props-v017.jpg - file: thingy-printed-v013.jpg title: Thingy in plastic · v0.13 caption: One color, standing on his oval base. The face and antenna came through clearly; the raised hand and badge lettering softened the most. The bowl behind him has been retouched out of the photo. date: 2026-11-03 bundle: first-print url: https://thingelstad.xyz/things/thingy-model/artifacts/thingy-printed-v013.jpg - file: librarian-thinking-v013.png title: The librarian, thinking · v0.13 caption: The librarian outfit with the thinking face and gesture, the pairing first proposed for a search on Ask Thingy. date: 2026-11-03 bundle: two-sites url: https://thingelstad.xyz/things/thingy-model/artifacts/librarian-thinking-v013.png - file: workshop-hammer-v013.png title: The builder with a hammer · v0.13 caption: The workshop outfit showing the hammer, with the found-it face. date: 2026-11-03 bundle: two-sites url: https://thingelstad.xyz/things/thingy-model/artifacts/workshop-hammer-v013.png page: https://thingelstad.xyz/things/thingy-model/ --- # Thingy Model A poseable Blender character built from Thingy’s original illustration, with a shared skeleton, seven Scenes and their accessories, a screen face with moods, and a kit that puts him on any site. Thingy Model is an editable three-dimensional version of [Thingy](https://thingelstad.xyz/things/thingy/), Jamie’s agent sidekick. The cream robot, navy coat, orange bow tie, and raised finger come from the original illustration. A body beneath the clothes gives the character joints that can be posed and animated. Jamie described the idea in his interview: [“Thingy should actually be a 3D model and be able to move around and engage with people”](https://thingelstad.xyz/interviews/session-5/#q33). He began building the model with Codex in November 2026, reviewing renders and the character live in Blender. From v0.11, on the third of November, Claude Code carried the work forward in Blender 5.2. The original image stayed beside the work. The artifacts below keep the intermediate models as well as the corrections. The first prototype established the clothed character. Then the work went underneath the jacket: shorter mechanical legs, ankle collars, shallower feet, and arms built from the same vocabulary. Later passes returned to the head and hands, separated the shirt from the lapels, lowered the bow tie, and fitted the pockets to the coat. Lighting studies made the navy fabric easier to read. The bow tie’s dots and the badge’s letters became images wrapped onto their surfaces. Seven Scenes now share one skeleton. In the Library he wears the navy coat. Outdoors he has a forest-green shell, folded map, and an orange daypack that comes off. In the Workshop he wears an indigo canvas vest and can hold a tool: a screwdriver, hammer, drill, or laptop. At a Concert he has a charcoal denim jacket, orange sound-wave shirt, wristband, and over-ear headphones that give way to the usual ears when they come off. In the Kitchen he has a cream tee and a butcher-stripe apron. In Winter he has a mustard parka, tangerine mittens, and a fallen hood. At the Cabin he has a red buffalo-check flannel over a cream tee. The antenna light can be switched on or off. At v0.10 the standard ears took a continuous tapered shape and moved out to sit against the head’s surface. At v0.11 the face became a picture on the screen. Beside the original expression are the four moods Ask Thingy uses, and the pose and the face are chosen separately: the librarian for Ask Thingy, the workshop builder for this site. At v0.12 the laptop gave way to a switch of tools, each with a grip solved so every finger closes on the handle, and the lit antenna turned heart red. A study then showed why the clothes read flat. Lights meant to brighten the navy washed it out, and the cloth had no folds, seams, or stitching. The v0.13 pass relit the jacket, gave the coat brushed felt and the vest worn canvas, rolled the lapels, and added topstitching and folds that follow every pose. At v0.14 six more faces joined the moods, each with its meaning settled before it was drawn. At v0.15 the outfits became Scenes, and what he carries became Accessories: the daypack and headphones separated from their outfits, alongside the tools. The same pass gave the other three Scenes a cloth of their own at the scale the web model can hold, with folds and topstitching for Outdoors and Concert, and left the Library alone. At v0.16 the tools came around in front of him, and the laptop can turn its screen to him so he can work on it. Two new props arrived: a build plate holding a tiny printed Thingy, and an iPhone for the Concert that he checks and holds up. Its screen shows this page. At v0.17 the Kitchen, Winter, and Cabin Scenes joined, and the accessories turned personal. The book he reads is the Yearly Thing, and the mug carries the Road Sign Math logo. There’s a Kubb baton, tongs and a whisk beside a green ceramic egg grill, a stocking hat and a scarf, a 3D printer in the Workshop, a microphone, a neck camera, a helmet, and a candle. The character lives at [thingy.thingelstad.xyz](https://thingy.thingelstad.xyz/), the source of Thingy. [Thingy Kit](https://thingy.thingelstad.xyz/kit/) gives a project his persona, model, faces, and component behind one link, and following it means a new model reaches every site that does: Ask Thingy and this site both do. Everything there is licensed [CC BY-NC 4.0](https://creativecommons.org/licenses/by-nc/4.0/), and [its repository](https://github.com/jthingelstad/thingy.thingelstad.xyz) is public. The Blender masters stay in a private repository. The latest checkpoint is v0.17. The rig and short performance studies are working prototypes, and more animation controls, facial acting, and clothing adjustments remain. A one-color 180 mm [print figure](https://thingy.thingelstad.xyz/print/) for Jamie’s Bambu P2S, made from v0.13, is on the site, and on November 4, 2026 he said [“I printed the 3D model last night, so there’s now a physical print of Thingy.”](https://thingelstad.xyz/interviews/session-6/#q39) He did not plan for it to go this far: [“I never meant to create thingy.thingelstad.xyz or what has now become Thingy Kit.”](https://thingelstad.xyz/interviews/session-6/#q39) [“What started as a 3D model so I could pose Thingy differently has become a complete definition of Thingy’s character and persona: Thingy Kit.”](https://thingelstad.xyz/interviews/session-6/#q39) --- --- id: tosredux title: TOSRedux summary: A Semantic MediaWiki site at tosredux.org where people could crowdsource a structured analysis of websites’ terms of service. It never took off. collection: Historical projects status: abandoned url: https://web.archive.org/web/20151013153210/https://wikiapiary.com/wiki/Farm:Thingelstad.com started: "2011" topics: - mediawiki - semantic-mediawiki - open-web sources: - kind: website url: https://weekly.thingelstad.com/archive/306/ role: reference connections: [] page: https://thingelstad.xyz/things/tosredux/ --- # TOSRedux A Semantic MediaWiki site at tosredux.org where people could crowdsource a structured analysis of websites’ terms of service. It never took off. “A decade or so ago I got the wiki bug in a bad way,” Jamie wrote in [Weekly Thing 306](https://weekly.thingelstad.com/archive/306/), “and one of the use cases I thought made sense was a wiki approach to Terms of Service. I got it started on TOSredux.org with the thought that you could crowdsource a semantic analysis of terms of service and then use a browser plugin to give good feedback to people on what they are accepting.” The oldest copy of tosredux.org in the Internet Archive is from September 2011. It ran on his MediaWiki farm, and WikiApiary still listed it among the farm’s active wikis in [October 2015](https://web.archive.org/web/20151013153210/https://wikiapiary.com/wiki/Farm:Thingelstad.com). As far as the record shows it went away with the rest of the farm in 2016, in his technical downsizing. The idea still makes sense to him. [“TOSRedux really is about embracing the privacy values I have.”](https://thingelstad.xyz/interviews/session-4/#q27) [“My belief is that many people have no idea what the terms of service are saying and what they actually mean”](https://thingelstad.xyz/interviews/session-4/#q27), and [“ultimately you have this problem of: does anybody really care”](https://thingelstad.xyz/interviews/session-4/#q27). And then: [“I refuse to give up when it comes to privacy.”](https://thingelstad.xyz/interviews/session-4/#q27) --- --- id: velotweets title: VeloTweets summary: A 2009 site that gathered professional cyclists’ tweets into one grid, built by Luke Francl, Norm Orstad, Chris Hatch, and Jamie. collection: Historical projects status: retired url: https://web.archive.org/web/20090514063346/http://www.velotweets.com/ started: 2009-05-10 topics: - automation - open-web sources: - kind: website url: https://web.archive.org/web/20090514063346/http://www.velotweets.com/ role: archive connections: [] story: color: "#56779a" introduction: The peloton in its own words, one rider at a time. engineering: - One Twitter account followed every rider, and a job read its timeline every five minutes. - The grid was one query, each rider’s newest tweet from the past seven days, so a rider who posted often still appeared once. - TwitPic links became VeloPics. Teams, nationalities, the race calendar and the Message of the Day were kept by hand in a small admin. stack: - Ruby on Rails 2.3 - MySQL - Phusion Passenger - Capistrano - Twitter API - TwitPic related: [] questions: - How did VeloTweets collect riders’ tweets? - Why did VeloTweets show each rider only once? - What files are left from VeloTweets? artifacts: - file: masthead-logo.png title: The masthead caption: The logo and its tagline, “Pulse of the Peloton,” from the top of every page. date: 2009-05 url: https://thingelstad.xyz/things/velotweets/artifacts/masthead-logo.png - file: front-page-2009-05.png title: The front page during the Giro caption: Launch week, on Stage 4 of the 2009 Giro d’Italia. The Message of the Day names the stage, the grid shows each rider once with their newest tweet, and VeloPics and VeloEvents run down the side. date: 2009-05 source: https://www.thingelstad.com/2009/05/12/introducing-velotweets-the.html url: https://thingelstad.xyz/things/velotweets/artifacts/front-page-2009-05.png - file: team-astana-2009-05.png title: A team’s riders caption: The same grid for one team, Astana, with each rider’s flag and team badge. date: 2009-05 source: https://www.thingelstad.com/2009/05/12/introducing-velotweets-the.html url: https://thingelstad.xyz/things/velotweets/artifacts/team-astana-2009-05.png - file: velopics-2009-05.png title: VeloPics caption: Photos the riders posted to TwitPic, gathered into one grid. date: 2009-05 source: https://www.thingelstad.com/2009/05/12/introducing-velotweets-the.html url: https://thingelstad.xyz/things/velotweets/artifacts/velopics-2009-05.png - file: color-palette.ase title: The color palette caption: "The site’s colors as Adobe swatches: light blue #A0D3F2, slate blue #56779A, dark brown #261802, yellow #FFFF00, and white." url: https://thingelstad.xyz/things/velotweets/artifacts/color-palette.ase - file: jerseys.zip title: Jersey icons caption: Icons for the yellow, green, polka dot and white jerseys, 20 pixels wide and shown enlarged here. They were never used on the site. preview: jerseys.png url: https://thingelstad.xyz/things/velotweets/artifacts/jerseys.zip page: https://thingelstad.xyz/things/velotweets/ --- # VeloTweets A 2009 site that gathered professional cyclists’ tweets into one grid, built by Luke Francl, Norm Orstad, Chris Hatch, and Jamie. VeloTweets, “the Pulse of the Peloton,” collected the Twitter posts of professional road cyclists in one place. In early 2009 Jamie had started following riders like Lance Armstrong through their RSS feeds and noticed that, read together, they gave a first-person view of the peloton during races. VeloTweets included only pro riders and a few others in the sport, added each rider’s team and nationality, and showed each rider once in a grid with their most recent message, so frequent posters did not crowd out everyone else. It also gathered TwitPic photos as VeloPics, kept a race calendar, and ran a Message of the Day tied to the day’s racing. It had no budget and no business behind it. The idea was Jamie’s, and the team made it real. Luke Francl did most of the development, in Rails 2.3; Norm Orstad designed the site; Chris Hatch built the list of riders and filled in their profiles; and Jamie “played sweeper,” helping wherever he could. The grid came out of a working session: Jamie credits Norm’s comparison to a baseball card, and Luke credits Jamie with showing one tweet per rider. Luke [announced the site on Rail Spikes](https://web.archive.org/web/20090514074605/http://railspikes.com/2009/5/10/announcing-velotweets) on May 10, 2009, and Jamie followed two days later with [Introducing VeloTweets](https://www.thingelstad.com/2009/05/12/introducing-velotweets-the.html) and [Why do Cyclists Tweet?](https://www.thingelstad.com/2009/05/12/why-do-cyclists-tweet.html). VeloTweets read everything through its own Twitter account. The [About page](https://web.archive.org/web/20090603205416/http://www.velotweets.com/about) said so: “This account follows all of the people that we aggregate into VeloTweets.” Every five minutes the site read that account’s timeline, and the page reloaded itself on the same schedule. The grid showed each rider’s newest tweet from the past week, and by January 2010 VeloPics ran to [107 pages](https://web.archive.org/web/20100122083644/http://www.velotweets.com:80/photos?page=107) of photos. The last Internet Archive capture of the working site is from [March 2010](https://web.archive.org/web/20100318125905/http://www.velotweets.com/), when the grid had 114 riders; by [February 2011](https://web.archive.org/web/20110202042105/http://www.velotweets.com/) velotweets.com was a parked domain. In 2014 Jamie listed @VeloTweets among the Twitter accounts he had deleted ([Twitter Spam #NFL](https://www.thingelstad.com/2014/11/28/twitter-spam-nfl.html)). He still has the project’s files: its source code at the last commit, on March 21, 2010, and the design files from the launch. The artifacts below come from them and from his launch post. Among them are icons for the yellow, green, polka dot and white jerseys that never appeared on the site. The team wanted to show how many of each jersey a rider had won, but never found a free source for that data. It is a project he had lost track of until this site brought it back: [“There were a handful of projects like VeloTweets that I had totally forgotten about, and it was delightful to see that come back to life.”](https://thingelstad.xyz/interviews/session-5/#q34) > VeloTweets made me smile a lot, because I had forgotten about that project. It reminded me of the best of times for Twitter. When there were tons of professional cyclists using it, Twitter was just fun. … It was a great, fun project I built with a couple of friends. > > [Jamie, question 26](https://thingelstad.xyz/interviews/session-4/#q26) --- --- id: weekly-thing title: Weekly Thing summary: Jamie’s weekend newsletter of links with commentary, sent since May 2017 and published as a website, email, and podcast. collection: Publishing status: active url: https://weekly.thingelstad.com/ started: 2017-05-13 topics: - open-web - archives sources: - kind: github repository: jthingelstad/weekly.thingelstad.com role: implementation - kind: website url: https://weekly.thingelstad.com/ role: website sitemap: https://weekly.thingelstad.com/sitemap.xml feed: https://weekly.thingelstad.com/feed.xml - kind: website url: https://weekly.thingelstad.com/podcast/ role: podcast feed: https://weekly.thingelstad.com/podcast.xml - kind: website url: https://www.thingelstad.com/2026/05/07/massive-weekly-thing-website-build.html role: reference connections: [] story: color: "#eaa18f" introduction: Curiosity, collected and shared. engineering: - WT Builder keeps an issue structured until it is sent, then renders different editions for the website, email, and audio. - The public archive is an Eleventy site. Thingy’s private Librarian API builds the searchable archive that Thingy answers from. - "Writing, publishing, and the archive each belong to one system: WT Builder, the website, and the Librarian." stack: - Eleventy - Publishing - Email - Audio related: - wt-builder - yearly-thing-2025 - thingy - another-thing questions: - What is behind the publishing workflow? - How do Weekly Thing and Thingy connect? source: https://weekly.thingelstad.com/ sourceLabel: Read the archive started: Published since 2017 page: https://thingelstad.xyz/things/weekly-thing/ --- # Weekly Thing Jamie’s weekend newsletter of links with commentary, sent since May 2017 and published as a website, email, and podcast. The Weekly Thing is Jamie’s newsletter: the links he found interesting that week, each with his commentary, plus his own blog posts from the week. He sent the [first issue](https://weekly.thingelstad.com/archive/1/) on May 13, 2017, and has sent it most weekends since, taking breaks in summer and over the winter holidays. It began on TinyLetter, moved to MailChimp with [issue 23](https://weekly.thingelstad.com/archive/23/) in October 2017, and moved to Buttondown with [issue 131](https://weekly.thingelstad.com/archive/131/) in January 2020. He numbered those moves himself: “1.0: Launch on TinyLetter, 2.0: Move to MailChimp, 2.1: Custom HTML Template, 3.0: Buttondown.” He reached [issue 100](https://weekly.thingelstad.com/archive/100/) in April 2019, [200](https://weekly.thingelstad.com/archive/200/) in October 2021, and [300](https://weekly.thingelstad.com/archive/300/) in November 2024, which took “7 years 5 months 3 weeks and 6 days” ([Thoughts after writing 300 newsletters](https://www.thingelstad.com/2024/11/17/thoughts-after-writing.html)). It grew out of the links. Of the Pinboard collection behind it he said, [“It became the genesis of the Weekly Thing: I wanted a way to publish the bookmarks I had found interesting that week, and that was the backbone of the newsletter.”](https://thingelstad.xyz/interviews/session-2/#q11) He tells its history in eras: > I would say the Weekly Thing has had four eras. The first was when it launched on TinyLetter, the second on MailChimp, the third on Buttondown, and the fourth is still on Buttondown, but now with WT Builder and me taking over the archive and hosting it myself. The fourth is filled with a lot: WT Builder, taking over the archive, creating a generated podcast to go with it. There’s a huge expansion in this one. The first three are really all about me learning the content cycle and figuring out the right platform for sending the email. > > [Jamie, question 13](https://thingelstad.xyz/interviews/session-2/#q13) The platforms had reasons too. TinyLetter [“was aligned well to my indie web ethos”](https://thingelstad.xyz/interviews/session-2/#q13). MailChimp [“really is a marketing tool, not a newsletter tool”](https://thingelstad.xyz/interviews/session-2/#q13). Buttondown [“was designed for newsletters. It was designed to allow individuals to send. I loved that it used Markdown”](https://thingelstad.xyz/interviews/session-2/#q13). In May 2026, at 345 issues, he [rebuilt the website](https://www.thingelstad.com/2026/05/07/massive-weekly-thing-website-build.html) as a full archive with search, a table of contents for each issue, and Thingy for asking questions of the archive. The ten newest issues also got an audio edition, published as a [podcast](https://weekly.thingelstad.com/podcast/). He built it with Claude Code, Claude Design, and Codex, and called it a massive build. [Issue 349](https://weekly.thingelstad.com/archive/349/), two weeks later, called itself the first made in the Weekly Thing Workshop, a team of Discord agents, though Jamie says the Workshop never generated an issue. Starting with [issue 350](https://www.thingelstad.com/2026/09/20/i-just-published-weekly-thing.html) in September 2026, every issue has been written and sent from WT Builder. In October 2026 he [restructured the whole archive](https://www.thingelstad.com/2026/10/06/weekly-thing-archive-improved.html) so old issues render like new ones, and rendered every issue in audio, so the podcast feed “goes all the way back to the very first issue.” Readers have had places to talk about issues. He [created r/WeeklyThing](https://www.thingelstad.com/2022/10/30/i-decided-to.html) in October 2022, and in September 2023 opened the [Weekly Thing Forum](https://www.thingelstad.com/2023/09/22/introducing-weekly-thing.html) on Ponder, which closed when Ponder shut down in November 2025 ([Farewell Ponder and Weekly Thing Forum](https://www.thingelstad.com/2025/11/17/farewell-weekly-thing-forum-and.html)). Discussion moved back to the subreddit ([Weekly Thing 334](https://weekly.thingelstad.com/archive/334/)). As of the interview, [“right now there are over 1,600 people who subscribe to the Weekly Thing, who read it and engage with it on a regular basis.”](https://thingelstad.xyz/interviews/session-4/#q30) Since November 2024, readers have been able to become [Supporting Members](https://www.thingelstad.com/2024/11/17/weekly-thing-supporting.html). All of that money goes to one digital nonprofit each year: Creative Commons first, then the Electronic Frontier Foundation, which [received $1,164.92](https://weekly.thingelstad.com/archive/347/) in May 2026, and now [Signal](https://weekly.thingelstad.com/archive/350/). Asked what he hopes is still running in twenty years, after the blog: [“For sure, the Weekly Thing.”](https://thingelstad.xyz/interviews/session-5/#q35) --- --- id: weekly-thing-gpt title: Weekly Thing GPT summary: A custom ChatGPT loaded with the first 310 issues of the Weekly Thing. Jamie’s first way to ask the archive a question. collection: Publishing status: retired url: https://www.thingelstad.com/2025/02/25/weekly-thing-gpt.html started: 2025-02-25 topics: - agents - archives sources: - kind: website url: https://www.thingelstad.com/2025/02/25/weekly-thing-gpt.html role: reference connections: - to: weekly-thing label: answered from detail: The GPT was loaded with all 310 issues of the Weekly Thing published by February 2025. source: https://www.thingelstad.com/2025/02/25/weekly-thing-gpt.html - to: thingy label: was succeeded by detail: When Thingy launched in May 2026, Jamie compared the two. The GPT “was grade school level. Thingy is much smarter!” source: https://weekly.thingelstad.com/archive/347/ kind: lineage page: https://thingelstad.xyz/things/weekly-thing-gpt/ --- # Weekly Thing GPT A custom ChatGPT loaded with the first 310 issues of the Weekly Thing. Jamie’s first way to ask the archive a question. On February 25, 2025, Jamie [made a custom GPT](https://www.thingelstad.com/2025/02/25/weekly-thing-gpt.html) that anyone with a ChatGPT account could use, “loaded with all 310 issues of the Weekly Thing published so far.” He suggested questions like “What is the Weekly Thing view on social media?”, “What is worse, Facebook or TikTok?”, and “Show me a list of articles on X along with the issue they were in,” and shared it in [Weekly Thing 311](https://weekly.thingelstad.com/archive/311/). It had real limits. In March 2025 he showed it [getting the answer wrong](https://weekly.thingelstad.com/archive/313/) when he asked which issue the Fortune first appeared in. Fourteen months later he launched Thingy, who actually searches the archive and cites his sources, and compared the two in [Weekly Thing 347](https://weekly.thingelstad.com/archive/347/): the GPT “was grade school level. Thingy is much smarter!” The GPT’s link no longer works. What it was good for, in his words: > It taught me two things. One, sending a bunch of data into that system was not going to give me the experience I wanted. Two, it gave me enough of a taste that there was something here, and that if I could build a real agent around it, that could be meaningful. > > [Jamie, question 29](https://thingelstad.xyz/interviews/session-4/#q29) --- --- id: weekly-thing-workshop title: Weekly Thing Studio summary: Four AI agents on Discord, Eddy, Linky, Marky and Patty, who helped Jamie edit, research, promote and fund the Weekly Thing in 2026. He introduced them as the Weekly Thing Team and his Workshop. It was the Weekly Thing Studio at the end. collection: Publishing status: abandoned url: https://www.thingelstad.com/2026/05/12/the-weekly-thing-team.html started: 2026-05-12 topics: - agents - automation sources: - kind: website url: https://www.thingelstad.com/2026/05/12/the-weekly-thing-team.html role: reference - kind: website url: https://weekly.thingelstad.com/archive/349/ role: reference connections: - to: weekly-thing label: worked on detail: Weekly Thing 349 called itself “the first Weekly Thing created start-to-finish in the new Workshop.” Jamie says the Workshop never generated an issue. source: https://weekly.thingelstad.com/archive/349/ - to: wt-builder label: was succeeded by detail: Weekly Thing 350, in September 2026, was the first issue made in WT Builder, after a summer in which Jamie rebuilt the website, added the audio edition and worked on an Agent Studio, and, in his words, “kind of blew up my own publishing process.” source: https://weekly.thingelstad.com/archive/350/ kind: lineage page: https://thingelstad.xyz/things/weekly-thing-workshop/ --- # Weekly Thing Studio Four AI agents on Discord, Eddy, Linky, Marky and Patty, who helped Jamie edit, research, promote and fund the Weekly Thing in 2026. He introduced them as the Weekly Thing Team and his Workshop. It was the Weekly Thing Studio at the end. After nine years of Weekly Things assembled with Shortcuts, Jamie wanted help that didn’t wait for him. The old workflow “only runs when I engage with it. It is also brittle and ‘one way’.” In May 2026 he introduced [the Weekly Thing Team](https://www.thingelstad.com/2026/05/12/the-weekly-thing-team.html), “the genesis of my Workshop,” four agents on Discord, each with the whole Weekly Thing archive as a tool: - **Eddy**, the editor, assembled a working draft of the current issue every day and reviewed it. - **Linky**, the researcher, scouted the links Jamie flagged. When he replied with his commentary, Linky synced it back to Pinboard. - **Marky** worked on bringing the newest issue to new readers. - **Patty** ran the Supporting Membership calls to action, and was the only agent whose drafts appeared in an issue. “My words are mine!” Jamie wrote. The agents were a support team, not writers. [Weekly Thing 349](https://weekly.thingelstad.com/archive/349/), sent on May 23, 2026, called itself the first issue made start to finish in the Workshop, “by far the biggest change I’ve ever made to the Weekly Thing automation.” Jamie says it was not: [“the Workshop never actually generated an issue of the Weekly Thing”](https://thingelstad.xyz/interviews/session-2/#q13). Then over the summer, as he put it in [Weekly Thing 350](https://weekly.thingelstad.com/archive/350/), his work on an Agent Studio “kind of blew up my own publishing process.” That issue was the first made in WT Builder, which has made every issue since. The Workshop lasted four months, and by the end it was the Weekly Thing Studio. What it taught him: > I felt like I could use AI coding tools to maybe create anything, so I didn’t really know what I wanted. I framed it as the idea that a creative studio filled with agents working on projects alongside me could be really powerful. Ultimately, it never worked. I tried having a number of different agents working and collaborating, and I was never able to get that to produce anything of value. I abandoned it very quickly, because it always became overly complicated. > > [Jamie, question 27](https://thingelstad.xyz/interviews/session-4/#q27) The replacement went the other way: [“WT Builder and the weekly website were the better solutions, with a thin agentic layer on top, which WT Builder has”](https://thingelstad.xyz/interviews/session-4/#q27). --- --- id: wikiapiary title: WikiApiary summary: A Semantic MediaWiki site that tracks thousands of MediaWiki wikis, their software, extensions, and editing activity. collection: Historical projects status: retired url: https://wikiapiary.com/wiki/Main_Page started: 2012-12-21 topics: - mediawiki - semantic-mediawiki sources: - kind: website url: https://wikiapiary.com/wiki/Main_Page role: website - kind: website url: https://web.archive.org/web/20131218002106/http://wikiapiary.com/wiki/Main_Page role: archive photograph: true - kind: github repository: WikiApiary/WikiApiary role: implementation - kind: github repository: WikiApiary/wikibees role: successor connections: - to: foreground label: is skinned with detail: WikiApiary’s distinctive look came from the Foreground skin, which Garrick van Buren built and Jamie worked on for WikiApiary. source: https://www.thingelstad.com/2013/12/22/one-year-for.html page: https://thingelstad.xyz/things/wikiapiary/ --- # WikiApiary A Semantic MediaWiki site that tracks thousands of MediaWiki wikis, their software, extensions, and editing activity. WikiApiary is “a wiki to track other wikis.” Once a MediaWiki site is registered, a set of bots collects its software versions, extensions, skins, and editing statistics, and the wiki keeps the history so it can be charted and queried. It is built with MediaWiki and Semantic MediaWiki. Jamie started it as a holiday-break project in 2012; [MediaWiki.org](https://www.mediawiki.org/wiki/WikiApiary) dates it to December 21, 2012. On [Open Loop #7](https://www.thingelstad.com/projects/open-loop/7-turtle-turtle-turtle/) in January 2013 he said he built it “in about three days,” after Semantic Result Formats’ charts showed him he could graph wiki statistics, and that Garrick van Buren came up with the name: the MediaWiki logo is a sunflower, the bots are like bees, and a collection of hives is an apiary. After its first year it was collecting from 9,555 active wikis and had stored more than 1.8 billion statistics samples, with over 3.3 million property values of its own ([One Year for WikiApiary](https://www.thingelstad.com/2013/12/22/one-year-for.html)). It was the first project he started that grew a real community around it. Karsten Hoffmeyer helped administer it, Mark Hershberger explored ways for wikis to register themselves, Paul DeCoursey rewrote the chart code, and Federico Leva linked MediaWiki.org’s extension pages to their WikiApiary pages, which brought much of its traffic. What he saw in the platform: > Very simply, Semantic MediaWiki. I loved what you could build by bringing data and text together in a way that let you play with surfaces like they were clay. All of those sites were fundamentally built out of Semantic MediaWiki. > > [Jamie, question 16](https://thingelstad.xyz/interviews/session-2/#q16) When he decided he was done with it, others took it on. Mark Hershberger wrote in April 2017 that he had “[inherited the site from Jamie Thingelstad](https://lists.wikimedia.org/hyperkitty/list/wikiapiary@lists.wikimedia.org/message/HRNMPDZBNH5DWCWEFWMKLJAACDQDOAPY/).” That October, Hershberger and his son Basil began [moving it from the old Linode servers to Wikimedia Cloud Services](https://lists.wikimedia.org/hyperkitty/list/wikiapiary@lists.wikimedia.org/message/R7TRLEB73RKAGGA22VE3JAVW3YZOQSMF/). At its size the wiki has struggled with database timeouts ever since: it [came back online](https://lists.wikimedia.org/hyperkitty/list/wikiapiary@lists.wikimedia.org/message/7HK7OPHOID3ZLCYSZTNPXDPG7MHTXGMV/) in March 2023 after an upgrade to MediaWiki 1.39, was [in write-only mode](https://lists.wikimedia.org/hyperkitty/list/wikiapiary@lists.wikimedia.org/message/AMVVOP72ONA2YI7XJ7KV6O3K42BBBES4/) by that September, and MediaWiki.org marked it not operational in February 2025. Jamie’s own account of why: [“If you think about how WikiApiary worked, hack is the best term you could apply to it. But I still think those concepts are super fun”](https://thingelstad.xyz/interviews/session-2/#q16). The wiki projects, he said, [“all fell under their own weight because of the complexities and challenges of MediaWiki underneath”](https://thingelstad.xyz/interviews/session-2/#q16). In March 2026 Brian Wolff [got the site serving pages again](https://lists.wikimedia.org/hyperkitty/list/wikiapiary@lists.wikimedia.org/message/W5UMMJTSPGP7ZFT2NPTLCFHVVUXOLIOO/), with the update bots still off, and in May 2026 Hershberger announced from the Wikimedia Hackathon that WikiApiary and its bots [were moving to a Kubernetes cluster](https://lists.wikimedia.org/hyperkitty/list/wikiapiary@lists.wikimedia.org/message/DCSXARUPRRYZO4XKTTJXYIDM3T5AAGIV/) so it could start crawling wikis again. --- --- id: wikinosh title: Wikinosh summary: A Semantic MediaWiki site of nutrition facts for more than 20,000 foods, with a Twitter bot and an offline app. collection: Historical projects status: retired url: https://web.archive.org/web/20120630194132/http://wikinosh.com/wiki/Main_Page started: "2011" topics: - mediawiki - semantic-mediawiki sources: - kind: website url: https://web.archive.org/web/20120630194132/http://wikinosh.com/wiki/Main_Page role: archive connections: - to: numbers2words label: used detail: WikiApiary listed Numbers2Words 0.0.1 among Wikinosh’s extensions, and the main page spelled out its food counts. source: https://web.archive.org/web/20130103025340/http://wikiapiary.com/wiki/Wikinosh page: https://thingelstad.xyz/things/wikinosh/ --- # Wikinosh A Semantic MediaWiki site of nutrition facts for more than 20,000 foods, with a Twitter bot and an offline app. Wikinosh was a wiki of nutrition facts. Each food had a page with a nutrition label (serving size, calories, fat, sodium, carbohydrates, and protein) stored as Semantic MediaWiki properties, and foods were grouped into categories like Baby Foods, Beverages, and Spices and Herbs. By [December 2011](https://web.archive.org/web/20111205190345/http://wikinosh.com/wiki/Main_Page) it had 13,753 food records, and by [mid-2012](https://web.archive.org/web/20120630194132/http://wikinosh.com/wiki/Main_Page) 21,550. In January 2013 [WikiApiary](https://web.archive.org/web/20130103025340/http://wikiapiary.com/wiki/Wikinosh) counted 20,433 articles and 981,167 property values on it. A lot of data for a hobby wiki. On [Open Loop #2](https://www.thingelstad.com/projects/open-loop/2-what-am-i-editing-anyway/) in June 2012, Jamie described the food wiki he had “kind of in alpha” and how turning on Wikimedia Commons let a page show a photo of a banana just by naming the file. In July 2013 he worked with Yaron Koren to put Wikinosh’s data into his Miga app for offline, mobile access, and wrote up the Semantic MediaWiki limits he hit exporting more than 20,000 items ([Paging Large Datasets in Semantic MediaWiki](https://www.thingelstad.com/2013/07/30/paging-large-datasets.html)). The @Wikinosh Twitter account posted a random food from its 28,000-plus entries every six hours. In November 2013 one of those posts, about trout, drew an IRC-style trout slap from another bot ([Slapped with a Large Trout](https://www.thingelstad.com/2013/11/04/slapped-with-a.html)). The last copy of the wiki in the Internet Archive is from April 2014, and by November 2014 he listed @Wikinosh among the Twitter accounts he had deleted ([Twitter Spam #NFL](https://www.thingelstad.com/2014/11/28/twitter-spam-nfl.html)). His verdict on the platform under it: [“Ultimately, the MediaWiki ecosystem is not powerful enough to run these kinds of applications. It was too janky.”](https://thingelstad.xyz/interviews/session-2/#q16) --- --- id: wt-builder title: WT Builder summary: The app Jamie writes and sends the Weekly Thing in, as a website, an email, and a podcast, and makes Another Thing with. collection: Publishing status: active url: https://github.com/jthingelstad/wt-builder started: 2026-09-20 topics: - open-web - agents - mcp sources: - kind: github repository: jthingelstad/wt-builder role: implementation - kind: website url: https://www.thingelstad.com/2026/09/20/i-just-published-weekly-thing.html role: reference connections: - to: weekly-thing label: publishes detail: WT Builder authors issues and sends the website, email, and audio editions of Weekly Thing. source: https://www.thingelstad.com/2026/09/20/i-just-published-weekly-thing.html - to: another-thing label: authors detail: Another Thing podcast authoring moved into WT Builder in October 2026. source: https://github.com/jthingelstad/wt-builder/commit/bea76c7ef4fc79a878072feebf694ce18ad217ea page: https://thingelstad.xyz/things/wt-builder/ --- # WT Builder The app Jamie writes and sends the Weekly Thing in, as a website, an email, and a podcast, and makes Another Thing with. WT Builder is the app Jamie writes the Weekly Thing in. He started building it with Claude in July 2026 to replace the Weekly Thing Studio, the team of Discord agents he started in May 2026, and the Shortcuts workflow he used for nine years. It combines what he writes for an issue with links and posts pulled from Pinboard and Micro.blog. The issue stays structured until it is sent, and then WT Builder renders three different editions: the website, the Buttondown email, and the audio edition for the podcast. The [README](https://github.com/jthingelstad/wt-builder) says it is narrow on purpose: “one editor, one current issue, one newsletter.” What was wrong with the old way, in his words: > The biggest issue was that it was a one-way pipe. I could create content, but if I changed anything further down the line, it was really difficult to make that change back in the source material. The other thing was that it was not at all what you see is what you get. … All of that is why I ended up creating WT Builder, again enabled by the fact that I could build it with agentic technology. Otherwise it would have been incredibly expensive and far too time consuming to create an application only I would ever use. > > [Jamie, question 13](https://thingelstad.xyz/interviews/session-2/#q13) [Weekly Thing 350](https://www.thingelstad.com/2026/09/20/i-just-published-weekly-thing.html), sent on September 20, 2026, was the first issue made in it. He had Claude watch him use it that first time and fix problems as they came up. The next day they [reworked the audio edition](https://www.thingelstad.com/2026/09/21/weekly-thing-podcast-improvements.html), with better pauses, section announcements, and pronunciation, plus links in the episode descriptions. In October he [added an MCP server](https://www.thingelstad.com/2026/10/03/my-newest-mcp-experiment-was.html) so Claude could follow along as he writes and point out typos and grammar. On October 11, 2026, WT Builder also [took over the Another Thing podcast](https://github.com/jthingelstad/wt-builder/commit/bea76c7ef4fc79a878072feebf694ce18ad217ea) from the retired Another Thing Builder, and it [“has the ability to help me flesh out Another Thing podcast episodes”](https://thingelstad.xyz/interviews/session-3/#q21). He keeps the Shortcuts workflow around as a fallback. --- --- id: yearly-thing-2025 title: Yearly Thing 2025 summary: A book of every link Jamie commented on in the 2025 Weekly Thing, subtitled Agents, Attention, Artifacts, in print and as an eBook. collection: Publishing status: archived url: https://www.thingelstad.com/2026/01/20/i-made-a-book-yearly.html started: 2025-12 ended: 2026-01-20 topics: - archives - reading - poap sources: - kind: website url: https://www.thingelstad.com/2026/01/20/i-made-a-book-yearly.html role: reference - kind: website url: https://www.lulu.com/shop/jamie-thingelstad/yearly-thing-2025/paperback/product-84w66ey.html role: distribution - kind: website url: https://jthingelstad.gumroad.com/l/yearly-thing-2025 role: distribution connections: - to: weekly-thing label: collects a year of detail: All 324 links Jamie commented on across 31 issues of the Weekly Thing in 2025, reorganized into ten topic chapters, in print and eBook form. Proceeds support the Weekly Thing Supporting Membership program. source: https://www.thingelstad.com/2026/01/20/i-made-a-book-yearly.html artifacts: - file: cover.jpg title: The cover caption: Wind turbines against a cloudy sky, under the title and the subtitle Agents, Attention, Artifacts. Jamie posted it the day before the book came out. date: 2026-01-19 source: https://www.thingelstad.com/2026/01/19/i-just-finished-up-this.html url: https://thingelstad.xyz/things/yearly-thing-2025/artifacts/cover.jpg - file: paperback.jpg title: The paperback caption: A print copy from Lulu, photographed the day the first copies arrived. date: 2026-01-27 source: https://www.thingelstad.com/2026/01/27/the-print-copies-of-the.html url: https://thingelstad.xyz/things/yearly-thing-2025/artifacts/paperback.jpg - file: contents.jpg title: Contents caption: The ten chapters, from The AI Revolution to Tools, Productivity and Delights, then the Weekly Thing Index and the Afterword. date: 2026-01-27 source: https://www.thingelstad.com/2026/01/27/the-print-copies-of-the.html url: https://thingelstad.xyz/things/yearly-thing-2025/artifacts/contents.jpg - file: pages-90-91.jpg title: Pages 90 and 91 caption: Two items from the chapter on privacy, security and encryption, each under the Weekly Thing issue it came from. date: 2026-01-27 source: https://www.thingelstad.com/2026/01/27/the-print-copies-of-the.html url: https://thingelstad.xyz/things/yearly-thing-2025/artifacts/pages-90-91.jpg page: https://thingelstad.xyz/things/yearly-thing-2025/ --- # Yearly Thing 2025 A book of every link Jamie commented on in the 2025 Weekly Thing, subtitled Agents, Attention, Artifacts, in print and as an eBook. For a few years Jamie had wondered about a book version of the Weekly Thing, something like an almanac. He [started it over Christmas 2025](https://www.thingelstad.com/2026/01/19/i-just-finished-up-this.html) and [published it](https://www.thingelstad.com/2026/01/20/i-made-a-book-yearly.html) on January 20, 2026, as _Yearly Thing 2025: Agents, Attention, Artifacts_. It gathers all 324 links he commented on across 31 issues in 2025 into ten topic chapters, from The AI Revolution to Tools, Productivity and Delights, with an Introduction, a Weekly Thing Index, and an Afterword. The eBook keeps every hyperlink. The paperback lists the issue each item came from, with QR codes that lead to the Weekly Thing Index. “I made the Yearly Thing with Claude Code,” he wrote in [Weekly Thing 339](https://weekly.thingelstad.com/archive/339/), and he laid out the book in Vellum. The [paperback is $30 on Lulu](https://www.lulu.com/shop/jamie-thingelstad/yearly-thing-2025/paperback/product-84w66ey.html), and the first print copies [arrived on January 27](https://www.thingelstad.com/2026/01/27/the-print-copies-of-the.html). The [eBook is $20 on Gumroad](https://jthingelstad.gumroad.com/l/yearly-thing-2025). Anyone who bought it in the first two months got a [Yearly Thing 2025 POAP](https://poap.gallery/drops/223594). All proceeds go to the Weekly Thing Supporting Membership program, and the book’s sales were part of the [$1,164.92 given to the Electronic Frontier Foundation](https://weekly.thingelstad.com/archive/347/) in May 2026. It is archived as a finished thing. Of the projects he has closed, he said, [“all of them had natural landing points, or it became obvious they weren’t worth pursuing”](https://thingelstad.xyz/interviews/session-4/#q28). The idea, in his words: [“what would it look like to take everything I did in a year of The Weekly Thing and make a book of it?”](https://thingelstad.xyz/interviews/session-6/#q42) As for another one: [“I’m not committed to a Yearly Thing for 2026. If I do one, I’ll do it very differently, because my understanding of the technology and what it can do has moved a lot since then.”](https://thingelstad.xyz/interviews/session-6/#q42) --- --- id: your-version-number title: Your Version Number summary: A website that writes your age as a software version, decades.years.days, with a Work Edition for job tenure. collection: Personal tools and making status: active url: https://yourversionnumber.com/ started: 2026-05-03 topics: - play sources: - kind: github repository: jthingelstad/yourversionnumber.com role: implementation - kind: website url: https://yourversionnumber.com/ role: website sitemap: https://yourversionnumber.com/sitemap.xml - kind: website url: https://www.thingelstad.com/2018/02/24/your-version-number.html role: reference - kind: website url: https://www.thingelstad.com/2026/05/06/your-version-number-the-website.html role: reference connections: - to: release-notes label: grew into detail: Release Notes uses Your Version Number’s birthday arithmetic in a daily email and personal journal. source: https://github.com/jthingelstad/yvn-release-notes kind: lineage story: color: "#1763ff" introduction: A different way to count the days. engineering: - A framework-free static site calculates its numbers in the browser. - Dates, people, themes, and signed cards travel in the URL, making a view shareable without an account. - The related Release Notes product adds daily email and a personal journal. It has its own server and storage. stack: - JavaScript - CSS - Static web - URL state related: - release-notes - mb questions: - How does the version number work? - How is Release Notes related? source: https://github.com/jthingelstad/yourversionnumber.com started: The idea began in 2018 page: https://thingelstad.xyz/things/your-version-number/ --- # Your Version Number A website that writes your age as a software version, decades.years.days, with a Work Edition for job tenure. In February 2018 Jamie wrote [Your Version Number](https://www.thingelstad.com/2018/02/24/your-version-number.html), building on a habit of his friend David Hussman, who gave his age as a version number. He mapped it to semantic versioning: decades are the major version, years into the decade the minor, and days since the last birthday the patch. He was v4.6.52 that day, and he made a Workflow script to show the versions of people in his address book. David died that August. The [site’s About page](https://yourversionnumber.com/about/) says the arithmetic is his, because it is. The breakfast where it started: > The idea came from a conversation with my friend David Hussman. We were talking about software versions, about having a major version, a minor version, and every day, and we were riffing on it and both really jamming on what a fun concept it was. > > [Jamie, question 12](https://thingelstad.xyz/interviews/session-2/#q12) [“We were at Sun Street Breads, having a conversation over breakfast.”](https://thingelstad.xyz/interviews/session-2/#q12) Of David: [“I really miss him. He was a good friend, and gone too early.”](https://thingelstad.xyz/interviews/session-2/#q12) After a year of seeing his version through a [shortcut on his phone](https://www.thingelstad.com/2025/02/25/jamie.html), he made it a website with Claude Code in May 2026, first shared in [Weekly Thing 346](https://weekly.thingelstad.com/archive/346/) on May 3, 2026 and then in [a launch post](https://www.thingelstad.com/2026/05/06/your-version-number-the-website.html). Add one or more birthdays, pick one of the themes, and the page shows each version, counting up at midnight. Everything lives in the URL, so a view can be bookmarked, set as a home page, or sent to someone, with no account. Cards with a signed note work the same way. It is, he said, an idea [“that started as a seed and has refused to go away”](https://thingelstad.xyz/interviews/session-1/#q5), and [“Your Version Number is a great way to bring that into daily life in a way that’s fun and interesting”](https://thingelstad.xyz/interviews/session-2/#q12). The Work Edition applies the same idea to a job: completed years of tenure, the quarter of the current tenure year, and weekdays into that quarter, with a build number that counts every business day, and work themes such as a board update. In October 2026 the idea grew into [Release Notes](https://notes.yourversionnumber.com/), a daily email of the day’s version with a journal attached.