I agree with those statements. That is why we are using Atom on top of Pubsub in XMPP to built social networking features. The sub-layer is changing (Atom is e

I agree with those statements. That is why we are using Atom on top of Pubsub in XMPP to built social networking features. The sub-layer is changing (Atom is embeded into Pubsub XML on top of TCP real time streams, XMPP) but in the end the content is not "transformed" but just "transported". Atom already provides most of what ActivityPub provides regarding the description of the content (rich content, attachments, external links, comments, reply-to...). You just need to put it on top of a layer that specifies how this content can be accessed, subscribed and delivered. In our case it's XMPP Pubsub but it can also be pure HTTP requests. Good thing is that moving from one to another is pretty easy. This is a static page generated from Atom articles published on a XMPP Pubsub feed from TechCrunch RSS/Atom feeds https://nl.movim.eu/?node/news.movim.eu/TechCrunch https://nl.movim.eu/?node/news.movim.eu/TechCrunch, we can even generate back an Atom feed from it easily. On a similar way you can handle personal "blogs" https://nl.movim.eu/?blog/edhelas@movim.eu https://nl.movim.eu/?blog/edhelas@movim.eu with likes, shares and comments :) The XMPP Standard Fundation is working for more than 10 years now on integrating those concepts together and glueing existing standards to deliver social-features next to IM features and so on... You don't have to create "new standards that will cover everything else" (see https://xkcd.com/927/ https://xkcd.com/927/) if you can just glue the existing ones together.