Nearly there with the rss -> activitypub script first cut, but slightly hampered by the fact that it seems like there's a bug (github.com/bonfire-networks/...) in the handling of Update activities in Bonfire's client to server #activitypub API. Either that or I'm holding it wrong, which is entirely possible given it is the first time I'm using the API!
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".
> 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..