Comment by danabramov

There’s a clear difference in architecture between

1) a layer of app-agnostic hosting providers + a separate independent layer of apps aggregating over data from those (like personal sites with RSS + aggregators like Google Reader)

2) a circle of flat instances where each node couples app+hosting (like many little Twitters)

One doesn’t couple hosting with apps, another one does.

Mastodon/AP model is (2), atproto model is (1). You should be able to see the outcomes from different network shapes.

In atproto, you can build a new app that works with existing data, but in AP you can’t. In atproto you can move hosting with zero effect on your identity or how you show up in apps, in AP you can’t.