Posts stopped going out to some Mastodon instances I was testing with, and search wouldn't work. But now they do. The clanker is bad at fixing bugs with ActivityPub, like humans are.
Last night I slopcoded on my phone, from the bar. I have no idea what the stupid robot wrote, but it's live now!
I’m back from ATmosphereConf in Vancouver, and I'm processing what I saw and heard. The atproto developer community could not have been nicer and more welcoming. Here are some takeaways. The Atmosphere is bigger than social media I've been to a lot of developer conferences over the years, and what struck me most about this...
Another week of winter’s hold lies before us. Daytime temperatures will climb above freezing, yet still sit below what April usually promises. On Tuesday, much like last week, expect another round of snow, about an inch and a half in town, with greater amounts inland. Even so, the brown seams of earth are beginning to show through the thinning snowpack. I am told that mud season is nearly upon us and that a northern Minnesota mud season is something a man ought to experience at least once before calling himself a man. My own forecast is that the ice will go out on Lake Superior by tomorrow.
User intent declarations can be viewed as propositional attitudes (permission, prohibition, desire, intention, belief, etc.) over structured descriptions of data use. Treating them that way gives you composable building blocks from existing theory and lens-based translations between community vocabularies that make explicit what each translation cannot carry through.
A response to Bluesky's User Intents proposal: instead of prescribing a fixed set of intent categories, treat them as living data and use panproto lenses to map between the vocabularies that different communities will inevitably create.
In my last post I detailed the reasons for why I wanted to achieve a distributed PDS, or at least explore if it was possible. I also explained how I managed to achieve getting the database part of the PDS to be held on a server other than the PDS and then managed to run 2 PDS instances side by side, semi successfully.
Anthropic's new model is game-changing. At least, that's what they say in their advertisement designed to make money. Claude Mythos has apparently found hundreds of vulnerabilities in every major browser and operating system, including a remote code execution in FreeBSD and an out-of-bounds write in FFmpeg. They outline this in their now-public system card, which I’d be tempted to trust if AI companies hadn’t been saying this for years now. Remember when GPT-2 was “too dangerous to release”, but then turned out to be a worthless slop factory? Anthropic’s recent behaviour seems suspiciously similar, and I’m hesitant to believe in a product which literally has “myth” in the name.
Atproto users need a way to express granular AI preferences and carve out exceptions for specific entities or content types. This post introduces community.lexicon.preference.ai, a lexicon schema that decomposes AI usage into distinct categories and adds a scoped override mechanism built on top of Bluesky's User Intents proposal.
What else does a social app need? Ah, mentions of course! So you can talk to people! Why didn't I think of that!? I was actually reading something else and it occurred to me.
New editor blocks, smarter image handling, and important security and reliability fixes across the platform.
Anthropic's Mythos makes autonomous vulnerability chaining across devices a sudden reality, so I've been thinking about how digital 'antibotty' inoculation networks may be needed far sooner than I expected.
t ATmosphereConf 2026, Victoria Machado de Oliveira (@vicwalker.dev.br) presented on how to attract non-English-speaking users. Her talk was structured around three pillars: onboarding, communication, and translation. A practitioner's field report.
We’ve just celebrated reaching 3,000 stars, made a number of major releases, and the team gave a really great presentation at atmosphereconf... But it seems I still hadn’t actually answered so many questions - just teased at the end of the previous article. I think it’s time to formulate the answers and finally gather them all in one place.
Bravo to @bmann.ca and @knowtheory.net for an amazing four days of open social web conversations in Vancouver! How many tech conferences present brilliant talks that feature the kelp forest and artisanal cheese as metaphors for a community of developers? Thank you @kissane.myatproto.social and @blaine.bsky.social for rooting us in such powerful narratives and images.
UCAN's struggle: Revocation requires a centralized revocation list that every verifier must check. This reintroduces a centralized dependency into a decentralized system. If the revocation list is unavailable, revocation fails. Worse, offline verification succeeds even for revoked capabilities because the self-contained token can't be checked against an unavailable list. UCAN fails dangerously when offline.