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? 😇

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.

atproto devs, read this:

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.

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

Read through atproto proposal-0016 and took some notes on important points that I think are worth sharing and talking about.

I think if you're saying "atproto doesn't need a ____" then you're missing the point. Let people build the things they want to see in the ecosystem that they, themselves, will use. We don't need ten things shaped the exact same way, we need every type of shape.

I need to write more about this, but one of the core benefits of atproto is that it (dramatically) lowers the cost of coordination, both in divergence and convergence.