🫧 socialcoding.. @smallcircles@social.coop
Public

@eyeintheskyThe Eye

I think a problem is more that instead of "ActivityPub has JSON-LD" you might also say that AP delegates to.. or even 'handwaves' to linked data.

is linked data --> ✅ Extensibility mechanism DONE"

Which is either..

- By far not the case, if you consider the promise and power of ActivityPub

- May perhaps be true, if you have a very particular notion on what the fediverse is and isn't.

That last bit remained unspoken, so what AP vs. fediverse is, is really in the eye of the beholder. There exists no shared (technology) vision. discuss.coding.social/t/major-

With the extensibility mechanism unclear, there is no clear separation either to what is protocol and what is solution space, and there's continuous confusion around this.

I replied to @evanEvan Prodromou yesterday, as his remark would entail that all post-facto interoperability introduced on-the-fly by app impls would have to be honored now in the standards. What standards process does that give?

social.coop/@smallcircles/1161

The Eye @eyeinthesky@mastodon.social
Public

@smallcircles🫧 socialcoding.. It's even crazier than that. I saw the thread a few days ago where @cwebberChristine Lemmer-Webber apologized for JSON-LD in AP and @evanEvan Prodromou defended it (but for backwards-compat, not because AP is linked data). The "extensibility" claim is technical gaslighting since that's only true if you use JSON-LD processing of AP data (practically no one does and there's no requirement to do it). 🤪 Even then it's a weak form of protocol extensibility.

0
1
0

If you have a fediverse account, you can quote this note from your own instance. Search https://mastodon.social/users/eyeinthesky/statuses/116119217607305571 on your instance and quote it. (Note that quoting is not supported in Mastodon.)