2026-02-07 19:14 UTC
Replies (3)
-
@mat@friendica.exon.name 2026-02-07 20:06
@hongminhee @julian I'm a true believer in RDF from back in the day, so I'm hardly neutral. But... There are essentially no interesting ActivityPub extensions right now. Even Evan's chess example, no-one's actually using AP to play chess. It's just ActivityStreams + a few cute tricks now and then. Even if there were extensions, existing AP servers chop off and throw away data they don't understand. so none of these extensions could work. I feel like most of the "WTF am I learning JSON-LD for" criticisms are coming from this status quo. That includes "if someone wants to add a gallery thing or whatever, can't they make a FEP?" The way things work now, your extension either a) works only in your software or b) has to be painfully negotiated with the whole community. We're all gonna have a big fight about it on this forum anyway. Let's not pretend JSON-LD helps us. But if we add two things to the mix, the situation looks different. Those are 1. server software that "keeps all the bits", and 2. a whitelabel extensible app. That would make it very easy to spin up crazy new experiences for a sizeable existing userbase. Developers should not be forced to endure a FEP process, and they should not have to attract a userbase from nothing. They should be able to just build, without even worrying if they're stepping on toes. And of course, Fedify and libraries in other languages are a load-bearing part of that world, including enforcement of the JSON-LD rules. That world does not exist at all today, but JSON-LD does, so it's pretty valid to describe this design as premature optimisation. I dunno though, we don't seem that far away.
-
@mariusor@metalhead.club 2026-02-07 20:08
@julian I don't think it's premature optimization, but an artefact of ActivityPub being built on top of the Activity Streams vocabulary, which predates it by some time. @hongminhee
-
@sl007@digitalcourage.social 2026-02-08 14:39
@julian Manu, maker of JSON-LD who also helped with the AP Confs, made this nice video https://www.youtube.com/watch?v=vioCbTo3C-4 JSON-LD is a normative reference to ActivityPub. The context of AP is only 1 line, maybe 4 if you support the official extensions. It does not make anything much larger. It is for example important if you want to consume the federated wikipedia, wikidata, European Broadcasting Union or these Public Broadcasters https://www.publicmediaalliance.org/public-broadcasters-create-public-spaces-incubator/ but also to know that e.g. mobilizon uses schema.org for addresses. I give you an example, if you include "mz": "https://joinmobilizon.org/ns#", "wd": "https://www.wikidata.org/wiki/Special:EntityData/", "wdt": "https://www.wikidata.org/prop/direct/" in your context, then you know about mobilizon extension but also the whole common knowledge of the world … I like that, now you can support the whole vocabulary of wikipedia and wikidata which is just JSON-LD. You get it in all the languages of the world including the properties name. No problem, if others don't support it, but sad for users. @hongminhee