ATProto is a post-app protocol trapped in a world of apps. I can feel it all around the edges of the network.

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

atproto devs, read this:

new proof of concept: ATProtoCall! video calling over atproto with just static files and no dedicated signaling or streaming infrastructure.

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

soooooo where did we land on the whole "internet handle" vs "atproto handle" vs "bluesky handle" vs ...

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

atproto's moat is drawbridges

Can everyone building on atproto please answer this question? 😇

new proof of concept: ATProtoCall! video calling over atproto with just static files and no dedicated signaling or streaming infrastructure.

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.