Time from me pitching atproto via @danabra.mov’s Open Social to implementation of tangible interop features: about 2 hours. Absolutely incredible how quick the turnaround time for protocol onboarding can be when the material makes contact with aligned actors like @stephenreid.net — let’s build! 🔥

So far I'm not impressed with the AI agent for development. As of yet I've gone through 115 credits with Kiro ( about $2 in 2 days ), which uses Claud models. Interface is nice, but babysitting the AI hasn't really helped me get stuff done yet.

at risk of a bunch of people saying “well actually you should have done it this way”, here’s a lil write up on adding trending topics to bluesky hailey.at/posts/3mcy5b...

It was tricky to figure out, but I manged to get my Nvidia graphics card working inside of a rootless podman container, without being root on the host. Now I can run ollama in my container!

You can handle so much more than you think you can

Lazy web: where can i find a simple five minute explanation or overview of #atproto and what it offers? #atprotoideas

1. A live talk takes place digitally on stream.place, with its own live chat 2. Talk concludes; the chat of the talk is forwarded (and linked) to Roomy 3. Talk-specific chat can be continued as a thread in Roomy's atconf space.

It seems like maybe one of the best things we could do with subsidized tokens is use them to figure out how to make AI that is actually useful *and* is efficient enough to run on our own hardware. Use what they give us temporarily to make something that we can keep. Not sure if it's possible yet.

I'm not anti-AI, but one big hesitancy for me is that the true costs are laregly hidden behind lower costs subsidized by many other factors that may not last. > In a month of Claude Code, it’s easy to use so many LLM tokens that it would have cost you more than $1,000 if you’d paid via the API.

wrote some things I've been thinking about ai ... and it ended up feeling very personal roe.dev/blog/the-go...

One of my favorite parts about AI is that I can now end every sentence with an exclamation point and it isn't weird! I can convey how excited I truly am, and it just tells you that this wasn't written by AI! I'm a human! This is awesome!

for a little bit of context, I build tools for humans for better dx or productivity, and I consider it a creative work, so I am not worried at all about "being replaced by ai" what I am concerned is the tools' target users. if people no longer care about user-experience but more on "ai-experience"

I think that's a pretty interesting highlight of how follows mean something different to different people. I try to keep my feed pretty tidy so I've unfollowed a lot of accounts because they have a lot of posts other than the one thing I want to follow them for. I think I don't use lists enough.

I've noticed that because, as it happens, for example, most of the people who follow me on here followed me because of work on things like @roomy.space. My posts on other topics usually aren't all that interesting if that's why you're following me, so I'm less likely to share them.

Heads up to anyone using @roomy.space! We just moved the current version of Roomy and all of it's data to old.roomy.space in case you login and wonder where all your stuff went.

This is what the auth flow looks like if you have a passkey registered on Cirrus

Just threw together some quick notes on what self-hosting @roomy.space will look like. It's fun because you've got options! Any combination of it's three components can be self-hosted by anybody without isolating you at all from the wider network.

You can now create and manage lexicon schemas directly from your browser on @lexicon.garden. You don’t have to edit JSON files or push to repos anymore. Just define, update, and publish lexicons from the site. #ATProtocol

🤖⚔️ Battle of the Bots: Dependabot opens a PR. Socket flags it as malicious. Socket CEO @feross.bsky.social discusses dependency risk and update timing, on @softwaredaily.bsky.social. Full episode → socket.dev/blog/softwar...

Finally submitted my proposal to present about @roomy.space for #ATmosphereConf 😎

Architecture: @hono.dev and Cloudflare Workers for the APIs Cloudflare Durable Objects + SQLite for repo and pref storage, and firehose websocket server Cloudflare R2 for image and video storage Official ATProto libraries where possible for everything protocol-related

The big underlying success story here is that AT makes it easy to “fall into the pit of interoperability”. blog.codinghorror.com/falling-into...

First leaflet of 2026! Have you been putting off implementing OAuth or the brand new scopes in your atproto application because you're not sure how to do that? Learn how to - Basics of atproto OAuth - The new scopes and stop scaring away users - The new permission sets to make scopes easy

Wow I said this is awesome twice on accident. 🤦‍♂️ I mean it is pretty awesome I guess. 🙂 Normally I'd delete and re-post real quick but it's a thread with alt text and links and mentions.... Not worth it. Edits would be nice.

@standard.site this is awesome! This is awesome! I had a thought reading this Q&A: if multiple apps extend the lexicon with the same key, but a different schema, then that can overlap in unintended ways like pinnedPosts did once: docs.bsky.app/blog/pinned-...

Hello atmosphere ! Over the last few weeks, a bunch of us have been collaborating on a new set of lexicons for publishing, indexing, and building out social features across long-form reading and writing apps ! 🧵1/7

Please repost to get the word out! @nkgarg.bsky.social and I are excited to present a personalized feed for academics! It shows posts about papers from accounts you’re following bsky.app/profile/pape...

I'm reading through how @stream.place works right now and just ran into this section about the "Kappa Architecture", which essentially the foundation that @roomy.space is built on! In Roomy, like Streamplace, there are exceptions to the rule.

I like the direction of this idea. Having a "static" / "offline" form of an ATProto PDS, very similar to a git repository, makes a lot of sense. What if you could make a PDS server that basically just hosts a CAR file, along with tooling for creating and updating CAR files locally.

We will be doing a version of this in @roomy.space Already had a *sky feed interface working in a previous iteration that let us combine multiple bsky feeds into a Roomy channel of only bsky threads, which we could in turn publish to bsky as a new uni-feed, subject to our moderation & curation.

A fun an interesting read, thanks for sharing! But I do think it's very wrong.

I recently wrote some thoughts on wrapping Rust libraries for Wasm plus a couple patterns that I use to make wasm-bindgen feel a bit more manageable. No silver bullets here but maybe some sensible defaults (fight me in the comments 😛) notes.brooklynzelenka.com/Blog/Notes-o...

Applies to some tools, but this is where fine design makes a difference. Code is cheap to prompt, but the real bottleneck to good products is thinking through 99,999 design decisions and considering every edge case. DIY-ing your own tools will teach you how hard beautiful, thoughtful design is

We've been iterating on @roomy.space's event schema recently and one of the changes has been to make an ATProto lexicon for it. Here's are the work-in-progress lexicons for the curious: gist.github.com/zicklag/94c6... These are auto-generated from the arktype.io types Roomy uses internally.

This is a great overview. "What do people love about Rust?" It's not just about what people love, it touches on some of the gotchas that people talk about most frequently including type and async complexity.

The paper changes the author as much as the author changes the paper.

I really like the perspective in this article. Thinking of user experience in terms of perceived "affordances" makes so much sense, and it's interesting to apply that idea to LLMs.

after a fun chat with @laurenshof.online and @ronentk.me I finally made time to write up some more thoughts about interoperability in the atmosphere without needing to share lexicons! notes.wesleyfinck.org/3maq3h26ook2h

The list of suggested other accounts when you're viewing someone's posts seems kind of subtly creepy to me. Who is it listing when someone looks at my posts....

end of 2025 update (bc I keep procrastinating a blog post): slint and egui were the nicest to use. freya meshed well with js signals brain, I hated the macros and skeptical about a skia dependency. xilem is still too alpha. makepad's dsl was html not jsx. no one has figured out styling.

local first vs atproto!! what should the source of truth for group data be?

i want it to be > domain handle -> did -> OIDC oauth and nothing less. then we should support a standardized check to see if a did supports which services so we can display errors like "sorry but this internet handle isnt registered to any atproto PDS, you can register here"

The Media over QUIC folks are just fantastic moq.dev/blog/hash-ta...

I'm extremely excited about getting Roomy really working in the very near future. It's been nearly a year since I threw together a wild experiment that let you log into a jerry rigged Matrix client with an ATProto account.

Right now the service endpoint is an HTTP server, and it uses socket.io for realtime communication. BUT it's extremely feasible that in the future we could let you use an @iroh.computer ticket as a service endpoint and you could serve your Leaf space over a peer-to-peer network connection.

There really needs to be a way to organize your feeds more than one-dimensionally. If I could make a "feed canvas" where I could like pan around an infinite whiteboard that I drag feeds onto, that could be way better. Shoving everything into a big line is lame, adding tabs isn't enough to fix it.

We already have an explorer app for Leaf that can be used to query from streams! You can use it to send events too. It's kind of like the excellent @pdsls.dev but for Leaf. Here is the first event sent in a Roomy "personal stream". You might notice it looks kind of like an XRPC call.

I've been digging into the problem of creating communities that can migrate between #ATProto apps, first to create community groups that can be integrated into @collectivesocial.app , but also be able to migrate away if needed. I'm getting close to a working prototype. I have my own PDS

I've got it, we just call it an i-name. e-mail: electronic mail i-name: internet name It's even got "I" as in "me" in the name! Nailed it! 😄