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.
me, my atproto backend in a bottle and i | flo-bit | Offprint
i really love building things for atproto and one of the things i like most about it, is that I can basically ignore a lot of the stuff i don't want to have to deal with, like user management and...
Two Types of Interoperability Without Sharing Lexicons - Wesley's notes
Sharing lexicons is not the only way to leverage atproto’s interoperability
Two Types of Interoperability Without Sharing Lexicons - Wesley's notes
Sharing lexicons is not the only way to leverage atproto’s interoperability
ATProtocol Dev
Interviews, news, and other updates about projects powered by ATProtocol
while the permissionlessness vector of atproto will certainly enable new things we can't imagine the pattern of "____ but on atproto" is key for taking our daily lives back. a framing i prefer is "i can now do {boringDailyLifeThing} without {shittyExtractiveApp}"
dame
i would like to see more atproto apps that aren’t just “already popular app, but on atproto”
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...?
The fundamental strength of ATProto — and why I think it'll last — is that it is designed first and foremost to be built upon, by anyone, for any reason, rather than locking into one specific paradigm of its maintainers' choosing. Also tbh sex workers are the social media Mandate of Heaven, so.
♍ Bee 🐝
3000 commits later babesky.app
Read through atproto proposal-0016 and took some notes on important points that I think are worth sharing and talking about.
Reading Proposal 0016: What atproto’s “Permissioned Data” Actually Does
ngerakines.leaflet.pubA while ago, I came up with the term Interoperable Serendipity. I was thinking of Solid at the time, but it totally applies to ATProto as well, and I'd love to see it embraced there! I just opened a discussion in the community forum to talk about it: discourse.atmosphere.community/t/interoperable-serendipity/1…
Interoperable Serendipity
discourse.atmosphere.communityHot take but I think it’s problematic for atproto that lots of developers i see talking about making stuff focus mostly on things absolutely no end user gives a shit about to fuel their protocols and architecture fetish, and it’s a failure there isn’t another app with like 100k+ users active even.
