Post · bonfire.cafe

New compatibility table at funfedi.dev: JSON-LD @context

https://funfedi.dev/support_tables/generated/context/

6 out of 9 implementations accept any @context value. But Mastodon, Hollo and Friendica reject activity entirely if https://www.w3.org/ns/activitystreams is not included in @context. Mastodon probably does this for no reason, but what about #Friendica and #Hollo?

#ActivityPub specification, section 3. Objects:

Implementers SHOULD include the ActivityPub context in their object definitions. Implementers MAY include additional context as appropriate.

ActivityPub context is recommended, but not required.

FenTiger

@fentiger@zotum.net replied · 2 weeks ago

@silverpill ActivityStreams allows @context to be missing, too:

When a JSON-LD enabled Activity Streams 2.0 implementation encounters a JSON document identified using the "application/activity+json" MIME media type, and that document does not contain a @context property whose value includes a reference to the normative Activity Streams 2.0 JSON-LD @context definition, the implementation MUST assume that the normative @context definition still applies.

julian

@julian@activitypub.space replied · 2 weeks ago

Re: New compatibility table at funfedi.dev: JSON-LD @contexthttps://funfedi.dev/support_tables/generated/context/6 out of 9 implementations accept any @context value.

@silverpill@mitra.social why do I get irrationally nervous whenever a new test by @helge@mymath.rocks drops?

silverpill

@silverpill@mitra.social replied · 2 weeks ago

cc @hongminhee

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances

Bonfire social · 1.0.0-rc.2.21 no JS en

Automatic federation enabled