@hongminhee I think that's a very good description of one of the key attributes of ActivityPub and the difference with AT Proto. ActivityPub can add something to the existing web, it allows for great diversity, and adds huge value in doing so. But over on AT Proto the way that infrastructure is composed is supporting a lot of completely new apps and developments, which is also exciting in its own way.
@hongminhee@hollo.social yeah that's exactly why I decided years ago to go "all in" on ActivityPub instead of scuttlebutt.nz which was in every other way a very cool technology and community.
@hongminhee I think that's a very good description of one of the key attributes of ActivityPub and the difference with AT Proto. ActivityPub can add something to the existing web, it allows for great diversity, and adds huge value in doing so. But over on AT Proto the way that infrastructure is composed is supporting a lot of completely new apps and developments, which is also exciting in its own way.
@hongminhee also making decentralised ID just URL you fetch simplifies a lot
I've read about dereferencing at:// urls, and it's...well, it's more like recursive DNS resolving, where you go to the registry (PLC), to get information where stuff you need is hosted (PDS), and then go there and get it
sure, it gives more flexibility, but I still don't get how they're gonna decentralise PLC
Blockchain is the only suitable solution I know, and in terms of efficiency they suck
@hongminhee activitypub has a top-down feel, abstracting "social web" concepts and indeed sticking (mostly) within the Web conventions. It is not very prescriptive about implementations.
In comparison ATproto is more of a bottom-up design, in a sense the bluesky code is the documentation of the protocol. Important design choices target a certain type of "scaling".
Its quite fascinating and revealing that such different approaches, help create the same "twitter" microblogging illusion.