PART TWO: All the other reasons i don't like CARs for atproto repo exports! In this one: ambiguities and inefficiencies. (the biggest problem is already hopefully getting fixed in the IETF draft though, yay!)
War on CARs: the rest of it
data-service-diaries.pckt.blogSep 23, 2026 at 3:10 PM
Bringing back at://
I’d also like to voice a strong dissenting opinion: a separate URI scheme follows long-standing precedent, reduces cognitive overhead and software complexity by making the transport distinction explicit, and has less ambiguous error handling. I think this direction trades short-term convenience for long-term ambiguity. The transport models are incompatible, not variants of each other Public atproto records flow through a well-understood pipeline: repos export as CAR files, relays consume fireh...
Research Project for ATProto Ecosystem Brand and User Experience Needs
Hello atproto builders — I’m a long time lurker and first time forum poster. I met some of you at Atmosphere conf in March, but for the most part have been thinking and talking about how I might get involved and support what’s happening here, rather than diving in. It’s been deeply heartening over the last couple years to see this community emerge and all the work so many of you have put in to make Atmosphere conf and all the other great atproto meetups and conferences—and community contribution...
Things we shouldn't say in polite company - Sherif's blog
you know, the stuff that makes sense when you work on ATProto but makes zero sense for everyone else
ATProto Isn't What You Think
This post takes a look at ATProto from a different angle, and explores the value of some possibly less-noticed pieces of it.
There's lots I haven't yet understood about atproto, but I simply won't do the standard.site thing whilst it offers a worse UX than… not doing it.
Guido X Jansen
It keeps confusing me that the main call to action in these cards (the button) does NOT go to the article but to the main website Is it just me that finds this weird...? The main visual CTA for a card about an article should go to that article no...?
Interesting conversation exploring the future of atproto sustainability!
JP
I want people to be comfortable paying for an atproto account (ie. space on a PDS) It’s the bedrock of everything we’re building; if it’s not funded it’ll get squeezed in ways that are bad for users (hi Gmail) We should normalise having (very cheap) paid-tier PDS accounts on the services we build
Who else is using @roost.tools’ Osprey for moderation on ATProto? Would there be interest in some sort of shared repo for UDFs and Plugins?
the point of atproto is to make locked-open apps. apps which are constrained such that they cannot be e.g. bought by billionaires and ruined. yes, doing non-atproto things "enables app developers to do more". yes, non-atproto is "more intuitive" and "it sucks" when you hit atproto's limits.
I'm going to "lets build: substack clone on atproto".
lets build: substack clone on atproto
atmo.rsvp
