Public NOW archive for August 5, 2026.
Visualize (and edit) your Atmosphere account's stored data.
Introducing Latch, an idiomatic elixir atproto OAuth library and client, built for flexibility and correctness.
I thought I knew what AT Protocol was about. It was for Bluesky and Bluesky-like sites and maybe auth. I wasn't entirely wrong but I was also way off the mark.
Public NOW archive for August 4, 2026.
Public NOW archive for August 3, 2026.
The best algorithm on Bluesky runs off somebody's gaming PC.
The best algorithm on Bluesky runs off somebody's gaming PC.
Public NOW archive for August 2, 2026.
Introducing my new website and its atproto-centric approach.
Public NOW archive for August 1, 2026.
Over the past couple of years, I have undertaken an exercise of sorts to reduce my dependence on American tech giants. Inspired by others, I thought I'd pen a short post on what services I've moved and where.
This post originally appeared on The Fulcrum. Welcome to this week's The Programmer's Fulcrum. It's your weekly curation of the essential news in the Open Media Network and Open Social development communities with a focus on devastating big tech via Techno Anarchism. As usual, we aim to provide actionable content you can use to destroy...
Public NOW archive for July 31, 2026.
Tangled's diskless, API-only AppView
The beauty of AT Protocol is that all of your data from different apps is available on your PDS, your own folder on the internet containing your stuff as JSON. This means that you can switch which app you use to view that data, without losing anything. It also makes it very easy to make...
A very non-technical post on why I am really into atproto.
Blogging used to be fun. Then it became energy-consuming. AT Proto brings the best part of the past and, hopefully, will renew my blogging.
I've been playing around with AT Protocol. The posts on this site are now published to standard.site, and I've written a (very basic) WordPress plugin to display posts from my PDS on the Now page of this site. As a developer, I've spent a good chunk of my working life building apps that stored things...
Marking a piece of feedback 'planned' kicks off an autonomous coding agent that implements it and opens a draft PR. Built with userinput.app, airglow, and GitHub Actions, without touching the app.
wolfram added a per-request repo/blob resolver for multi-tenant PDS use, moved storage ownership to MetalBear, hardened did:plc against the real PLC directory, and cross-compiles its XRPC server for Wii U.
I keep convincing myself the ATmosphere is separate from Bluesky, then un-convincing myself. So, to decide (mostly for future me), I went through every layer: handle, DID, PDS, relay, appviews, lexicons.
Tightening up the ship After a year of publishing The Fulcrum, I (as publisher) now know the topics, tools, and techniques I want to focus The Programmer's Fulcrum coverage on. And maybe it will have the side benefit of shorter TPF posts. We'll see if I can tighten up my discipline as well. ;) That...
Two ways to collect feedback in your Atmosphere apps — bug reports and feature requests via userinput.app, and reviews via atstore.fyi — using progressive scoping to request permissions on demand without overwhelming users.
Board-card URLs, avatar/banner URLs, and PDS-resolver endpoints were previously rendered or used with no validation at all. All three are now checked before use, alongside a broken-metadata fix and a broken install.
Redirect targets sourced from remote blue.linkat.board records were never validated. They're now checked before use, alongside a broken install, a favicon that never resolved, and a run of accessibility fixes.
A new hash-seeded generator variant joins the original as a selectable rendition, verified collector discovery surfaces who else collected a specimen, and a SEO/accessibility pass closes out the window.
MetalBear rebuilt its account model twice, migrated storage off wolfram, validated records against the lexicon corpus, and is now crawled by Bluesky's relays and indexed by the AppView. 0.2.0 to 0.7.0.
A quick step-by-step guide on migrating a repository from GitHub to Tangled
A Rust LLM training toolkit on Candle with hardware-aware auto-tuning, AT Protocol data sources, and a memory governor that throttles training rather than let the OS dip into swap.
croft-click now aggregates toolkit usage across the whole network instead of trusting client-side writes from each tool, and pds-landing's components resolve their hostname at runtime instead of assuming one domain.