Home | Notifications | New Note | Local | Federated | Search | Logout
Note Detail
Reply to @petitminion@socialhub.activitypub.rocks
silverpill@silverpill@mitra.social (2026-03-24 04:43:42)
This may limit interoperability because audience is supposed to contain IDs (either actor IDs or collection IDs). I think many servers don't even check audience, and rely only on to and cc.
Here's how these special strings could be translated into IDs for to / cc:
- me: current actor ID.
- instance: special collection ID, similar to https://www.w3.org/ns/activitystreams#Public. Prior art: Akkoma uses https://server.example/#Public for local-only posts.
- followers: actor's followers collection ID.
- everyone: https://www.w3.org/ns/activitystreams#Public
---Reply---
petitminion@petitminion@socialhub.activitypub.rocks (2026-03-31 21:41:44)
\audience\ can be object or link : https://www.w3.org/TR/activitystreams-vocabulary/#dfn-audience . Your proposition is too complicate from my pov. We could, send an object like :{
"type": "Group",
"name": audience_string
},
Reply
---Replies---
silverpill@silverpill@mitra.social (2026-04-01 03:29:06)
That would probably make it compliant with ActivityStreams, but still, it is not good for interop, because other fedi software specifies audience using URIs.
I would be happy to federate with Funkwhale, but with the mechanism described in the FEP it will require special treatment.