One of the huge perks of working at a software company is, when there's something about the product that bothers you personally, you can get your hands dirty and find out why it's basically impossible to get fixed

GraphQL error handling sucks. There, I said it. Null checks everywhere, and ambiguity: error, or true null? We've all been there. In this talk, Benjie Gillam shows how to fix GraphQL's biggest mistake in 512 bytes. 👇 youtu.be/odwQUAkmW44

There were only about 50 skins which were not already in our collection. Further confirmation that the museum's >101,000 skins represent the vast majority of all skins ever created.

I’ve been made aware of a 2013 “panic download” archive of downloads.nullsoft.com containing ~60k Winamp skins. Downloaded and hashing all the files to find any which are not already in the Winamp Skin Museum.

Exciting progress today! Called with @capt.dev about the React "concurrent stores" prototype, and we brainstormed potential Redux integration issues. I then whipped up a prototype branch that reworks `useSelector` to use the prototype, and _most_ tests pass! github.com/reduxjs/reac...

LuigiHann designed this around 2018 to celebrate the @archive.org integrating Webamp and adding a dedicated collection of Winamp skins.

📣THREAD: It’s surprising to me that so many people were surprised to learn that Signal runs partly on AWS (something we can do because we use encryption to make sure no one but you–not AWS, not Signal, not anyone–can access your comms). It’s also concerning. 1/

somehow @capt.dev revived this Winamp 5 skin I made 21 years ago

OpenAI's CISO Dane Stuckey posted an essay (on Twitter) about how their new ChatGPT Atlas browser attempts to deal with the risk of prompt injection attacks, I ended up writing a point-by-point commentary on my blog: simonwillison.net/2025/Oct/22/...

Works especially well with SQLite’s full text search. Been building a little search DSL for my site which compiles to SQLite’s FTS+structured search/sort conditions. github.com/captbaritone...

Markdown+metadata is such a good format for blog posts. But deploy-to-publish feels heavyweight, and I often want to publish from my phone. Current setup: Author in Notion and pull from Notion API to Markdown in SQLite DB. Site renders from SQLite.

Minting admin API keys with an unauth POST request is a wild bug to have zeropath.com/blog/breakin...

Winamp skins are (literally) zip files. And sometimes there’s weird stuff inside them. jordaneldredge.com/notes/corrup...

Been using this repo to iterate on API ideas for a concurrent compatible store for React. Still exploratory but excited that we’re very close to something that we can start trying out with existing data stores and start an iteration cycle based on what we learn.

The 3 worst GraphQL myths: ❌ Everything is POST ❌ All URLs are /graphql ❌ Anyone can query anything One solution destroys all three: Persisted Operations/Trusted documents www.jovidecroock.com/blog/graphql...

The bot it alive!

New post jordaneldredge.com/notes/physic...

I just brought my Winamp Skin bot to Bluesky @webamp.org

Working on a Bluesky Winamp Skins bot…

“Unleash the Thong Song” may be the greatest text ever rendered in a button

Shipped Grats v0.0.34 🚀

Got into a conversation with a friend last night about implementing permissions in GraphQL/Grats. Inspired me to write a guide for the Grats docs outlining three strategies that work well. One that I think is particularly elegant is Permission Tokens leveraging Grats' Derived Contexts.

I built Grats' Derived Contexts on a whim, but it ended up being a simple yet powerful compile-time dependency injection engine. A field just defines its dependencies via typed arguments and Grats ensures it gets passed a value at runtime.

Introducing the React Foundation

As an example: My personal blog (Next.js/RSC) also exposes a GraphQL server: jordaneldredge.com/api/graphql/ I just sprinkled some (68 according to grep) `@gql*` docblock tags around and got it for free by running `npx grats`.

Joshua Rogers, using AI tooling responsibly and professionally, reported 22+ genuine issues in curl that are now being addressed Especially notable because curl had problems with floods of garbage slop AI "security issues" in the past that were nothing of the sort simonwillison.net/2025/Oct/2/c...

I designed Grats' around "error driven development": each error provides specific guidance on how to fix it. This has proved a good fit for AI agents. I asked Claude to find an interesting SQLite DB on my computer and build an API using Grats and it did without any help!

An interesting aspect of AI for software library maintainers, is that it's now possible to have a fast feedback cycle on API design and documentation. 1. Design/document and API 2. Have AI try to use that API with docs 3. See how it fails 4. Improve API/docs 5. GOTO 2

The @archive.org got in touch about adding Milkdrop (Butterchurn) to their Webamp integration. This lead me to: 1. Build a new entrypoint includes Milkdrop by default 2. Writing a detailed, long-overdue docs site docs.webamp.org Very cool to see Milkdrop visualizer presets alive and accessible!

Blog post: A Mental Model for Data in UI Applications jordaneldredge.com/notes/ui-data/

Prototyping a version of the Grats playground where you can actually execute your schema right in your browser (in a worker).

React server components are great if your backend is Node and your rendering for the web. But what about native clients? Grats is great for this: Define your data using models for RSC, then simply annotate those same models so that your native clients can consume the same data via GraphQL.

🌟 Shoutout to @capt.dev, Relay maintainer and nullability champion! From shaping the “true nullability schema” to sharing critical insights, your impact on GraphQL is huge 🙌 #GraphQLStar

Got a perf benchmark and profiling working for Grats. Next release should be about 25% faster for large schemas!

Relay and GraphQL go hand-in-hand at Meta 🤝 At GraphQLConf @capt.dev‬ will share the Big Ideas in Relay that we should be using to make our own GraphQL usage that much better - whether we use Relay or not! graphql.org/conf/2025/s...

Webamp, the NPM library, now has a proper docs site. If you've ever wanted to add a Webamp player to your site, now might be the time: docs.webamp.org

React <ViewTransition /> is pretty good

Perfect. I can bind the “action” button on my phone to “buy a new phone”.

Nice little addition to the footer of my site

My old websites jordaneldredge.com/notes/old-we...

Teenagers are making Winamp skins in 2025 jordaneldredge.com/notes/hack-c...

I've been very happy with Grats' testing strategy: * Hundreds of fixture unit tests * Dozens of fixture runtime integration tests * All doc snippets compiled/validated at build time * Example projects act as test suites I wrote a docs page explaining how it works: grats.capt.dev/docs/faq/tes...

New blog post: Thinking about React as a state machine can help us reason about async state updates and React’s concurrent ceatures: {transitions} = f(state) jordaneldredge.com/blog/transit...

I wrote about the main feature of @typescriptlang.org enums that I'm going to miss: TSDoc support on enum members. I hope the TypeScript team can port this over to union members as more folks migrate towards string unions instead of enums. blog.disintegrator.dev/posts/ode-to...

Did you know you can change the Archive.Org music player into "webamp?"

Over the last 10 years, four kids have recorded versions of a ukulele arrangement I wrote back in 2011 jordaneldredge.com/notes/kids-p...