That complexity, however, comes at a cost and, unlike say JSON schema or some other options in this space, that cost is borne by the implementer. Especially problematic since a lot was punted to JSON-LD: #ActivityPub didn't want to define a metamodel and wanted to lean on #JsonLD for a lot.
Option 1: We can define an #ActivityPub2 specification (or equivalent) that moves wholesale away from #JsonLD and adopts something that pushes the complexity to a different level. Preferably something with a more defined metamodel.
Bluntly: I do not think this is feasible. Not from a technical standpoint, but rather from a cultural one. Too many people too invested in JSON-LD, and too much already built on top of #ActivityPub to do this.
So with the surge of traffic that's coming to #ActivityPub and the #Fediverse, I stumbled into a conversation about updating ActivityPub. I'm curious what people with a better #Dev and #admin background think should be changed in regard to an #ActivityPub2 since the original standard was released in 2018 and the Fediverse has changed dramatically since then.