Egregoros

Signal feed

API Docs
Timeline

Post

Remote status

Context

4
silverpill

silverpill

@silverpill@mitra.social remote
Open link

@hongminhee

>There's no going back.

We absolutely must go back. Either we have a vibrant ecosystem where building stuff is a pleasant experience, or fediverse slowly dies while linked data cultists harass developers about nonresolvable URLs in @context.

JSON-LD adds nothing to ActivityPub, it only creates problems. Time to move on.

Phantasm (away)

Phantasm (away)

@phnt@fluffytail.org remote
Open link
@lutindiscret @silverpill @hongminhee It was supposed to bring document schema validation (you shouldn't be able to fool a JSON-LD consumer into accepting invalid documents) and instead it added complexity that few know how to deal with and subtle vulnerabilities with plain JSON consumers due to the ability of overriding types.

Also it was supposed to be entirely optional, but the current spec editors would like you to believe otherwise.
silverpill

silverpill

@silverpill@mitra.social remote
Open link

@phnt @hongminhee @lutindiscret

>Also it was supposed to be entirely optional

Yes, exactly, here's ActivityPub:

https://www.w3.org/TR/activitypub/#obj

Implementers SHOULD include the ActivityPub context in their object definitions.

Here's ActivityStreams:

https://www.w3.org/TR/activitystreams-core/#jsonld

Implementations producing Activity Streams 2.0 documents SHOULD include a @context property with a value that includes a reference to the normative Activity Streams 2.0 JSON-LD @context definition using the URL " https://www.w3.org/ns/activitystreams".

In both cases it's a SHOULD, this means I am allowed to not include @context if I have a good reason to do so.

I have plenty of reasons but Mastodon can't process an activity if there is no @context. its_always_mastodon.jpg

Replying to @silverpill@mitra.social

Replies

0

Fetching replies…