Conversation

Notices

1. Embed this notice
   silverpill (silverpill@mitra.social)'s status on Thursday, 04-Sep-2025 06:53:36 JST silverpill

   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.

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Thursday, 04-Sep-2025 07:29:20 JST silverpill

     in reply to

     • 洪 民憙 (Hong Minhee)

     cc @hongminhee

   • Embed this notice
     FenTiger (fentiger@zotum.net)'s status on Friday, 05-Sep-2025 04:29:21 JST FenTiger

     in reply to
     @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.