Post AvyF3se6oo3oAN09Vg by raphael@mastodon.communick.com
(DIR) More posts by raphael@mastodon.communick.com
(DIR) Post #AvrCsMhbgSFPtXIcvw by steve@social.technoetic.com
2025-07-06T12:02:57Z
0 likes, 0 repeats
To follow up on my #ActivityPub C2S post from a few days ago, I wrote a blog article on my thoughts about improving the C2S protocol and a description of some related experimentation I've been doing.https://www.stevebate.net/activitypub-client-api-a-way-forward/
(DIR) Post #AvrCsO8aLdQELUvgci by silverpill@mitra.social
2025-07-06T12:55:52.980672Z
2 likes, 0 repeats
@steveTreating ActivityPub messages as plain JSON undermines extensibility because it prevents the use of JSON-LD features like context definitions, leading to potential property name collisions and making it difficult for implementations to reliably interpret or extend messages.No, treating ActivityPub as JSON doesn't undermine extensibility. ActivityPub is extended by adding new properties to JSON objects, and if you want to avoid collisions you can use URLs or reverse-DNS strings for property names. JSON-LD is not needed for that, it only complicates things for no reason.
(DIR) Post #AvrJTlj0DGUxwMAeeW by steve@social.technoetic.com
2025-07-06T13:27:14Z
0 likes, 0 repeats
@silverpill Those workarounds for the undermined extensibility don't negate my point and will not generally interoperate. According to the ActivityPub book, "One point to note is that correctly parsing and interacting with AS2 objects with extended properties requires a JSON-LD-aware parser." I agree this isn't absolutely true (in special cases) but try sending expanded "toot" context term URIs and see how well it works 😉 (since all servers AFAIK expect those terms to be compacted).
(DIR) Post #AvrJTnDsdwnAaPcpQ8 by silverpill@mitra.social
2025-07-06T14:09:59.712098Z
2 likes, 0 repeats
@steve Why would I send an expanded toot: URI when all servers expect a short name? Your example is another proof that JSON-LD is only useful for solving problems created by JSON-LD.
(DIR) Post #AvuotmzLoj8XRSaKLQ by steve@social.technoetic.com
2025-07-08T06:38:17Z
0 likes, 0 repeats
@lanodan There’s no public repo yet. It’s WIP. Isn’t Pleroma C2S only supported on the server side?
(DIR) Post #AvupFJ1FvHIerfjgWG by sun@shitposter.world
2025-07-08T06:50:34.552962Z
3 likes, 1 repeats
@steve @silverpill is there even a single ap server implementation that can handle arbitrary json-ld and not just compacted to specific prefixes
(DIR) Post #AvuqAyvulDp9MejufQ by steve@social.technoetic.com
2025-07-08T06:56:40Z
0 likes, 0 repeats
@sun @silverpill Vocata, ActivityPods, rdf-pub, …
(DIR) Post #AvuqB0PNHAz1wJWxE0 by sun@shitposter.world
2025-07-08T07:00:58.712957Z
0 likes, 1 repeats
@steve @silverpill alright. I found it basically impossible to store and index efficiently for common access patterns and gave up and just went back to treating it as json. I tried a few triple store databases and the performance wasn't great for my historic dataset. I'll try it again someday though
(DIR) Post #AvyF3se6oo3oAN09Vg by raphael@mastodon.communick.com
2025-07-06T16:18:20Z
0 likes, 0 repeats
@silverpill @steve > Why would I send an expanded toot: URIBecause you might be using a different namespace which is conflict with the one from mastodon, so the extended form is needed to remove ambiguity?
(DIR) Post #AvyF40QZszzSIijSWu by raphael@mastodon.communick.com
2025-07-06T16:23:54Z
0 likes, 0 repeats
@silverpill @steve JSON-LD is just one different way to serialize RDF data. Throwing JSON-LD away means throwing away all the power, benefits and flexibility that RDF can bring and in exchange gives us what? Another series of ad-hoc of data exchange formats? Why not lean in into the standard which is in development for 25+ years?
(DIR) Post #AvyPllowYSsBHVdVTc by sysrq@lab.nyanide.com
2025-07-10T00:23:57.688188Z
0 likes, 1 repeats
@raphael @silverpill @steve You're stupid.
(DIR) Post #AvyQMkBtZr6AwQ0CSe by sysrq@lab.nyanide.com
2025-07-10T00:30:38.678345Z
1 likes, 1 repeats
@steve No.