That should be the guiding principle for all atproto "alternatives"

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}"

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}"

Can everyone building on atproto please answer this question? 😇

Lexidraw proves it. Atproto does not exist to build something unprecedented out of nothing: it exists to fuse well-known open-source projects into atproto. The key is the data storage layer. Atproto will latch onto anything, like a remora.

Too many of y’all get the shape of atproto fundamentally incorrect, thinking it’s about “data ownership,” but it’s literally never been about that, and if you keep banging that drum, you’ll miss the point, just like we have every other time.

There are many things being built on atproto. Many of them won’t get adopted or thrive. And yes, many are built without user research. It’s OK? Don’t use things you don’t want to. Promote things you like. And build something yourself if you feel like it. Do it the way YOU want it to be.

atproto devs, read this:

share atproto architecture diagrams you've seen in the wild