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

i want to do a little ✨ ama about atproto ✨ in this thread. no question is too simple if you’ve been curious about atproto but don’t know much (anything?) about it, ask any question and i’ll try to explain it in my own words. (+ would love to hear from friends who aren’t very active on bsky)

i want to do a little ✨ ama about atproto ✨ in this thread. no question is too simple if you’ve been curious about atproto but don’t know much (anything?) about it, ask any question and i’ll try to explain it in my own words. (+ would love to hear from friends who aren’t very active on bsky)

A 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…

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

Hot 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.

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.

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