> As an aside, I'm quite liking the ActivityPub APIs so far, although ld-json does leave me feeling like there's a fair jump from "script that works" to "actually does everything the spec would theoretically allow".
There's the "linked data conundrum" as I call it, which recently reared its head again, triggered by a #SocialHub post I created the other day:
https://socialhub.activitypub.rocks/t/practices-around-json-formatting-of-json-ld-messages/8628
The #LinkedData conundrum is the eternal friction between the plain #JSON and the #JSONLD view of the #ActivityPub social web. And it has never really be solved. I consider it one of the misconception that led to endless discussion, confusion, and waste of time. For the ActivityPub API which hold the promise to correct course towards a more standards-compliant #fediverse, I created an issue on the subject..
https://github.com/swicg/activitypub-api/issues/63
Followed by another on protocol design..
