Activity Streams 2.0
This article is a stub. You can help the IndieWeb wiki by expanding it.
Activity Streams 2.0 is (AKA Activity Streams Core) an open web standard (W3C Recommendation) and format for communicating a series of user activities across websites, based on prior ActivityStreams community proposals & specifications and developed in the W3C Social Web Working Group.
- Latest published version: https://www.w3.org/TR/activitystreams-core/
- Latest draft: https://w3c.github.io/activitystreams/core/
Software Support
Service Support
- Bridgy
- Bridgy Fed
- granary
- various Mastodon instances
Extensions
- AS2 extensions wiki page: https://www.w3.org/wiki/Activity_Streams_extensions
Criticism
- Unspecified semantics leads to de facto semantics definition by largest implementation(s): https://hachyderm.io/@danderson/109459311884227844
- "Every time the activitystreams core and vocab spec say "we left the semantics of these bytes completely unspecified on purpose", I die a little inside. In practice this seems to mean "today's most popular implementation owns the semantics, and shouldn't feel obligated to document them" :(" @danderson December 5, 2022
- ^ https://hachyderm.io/@ewenmcneill@cloudisland.nz/109459750261035043
See Also
- ActivityStreams
- Criticism for using JSON-LD for extensions in AS2: https://hachyderm.io/@hrefna/111634273843633052
- "I am not working with AP from a graph database.I am not working against a RDF data modelI am not dealing with RDF projectionsI am not an academic who is working with ontologies From a standards perspective: Every single time weirdness from RDF leaks into JSON, it adds complexity to downstream implementations. If your spec is entirely based on RDF that's one thing. But if your spec disclaims being based on RDF and says "only for extensions," then you can't have your cake and eat it too." @hrefna December 24, 2023