https://socialwebfoundation.org/2026/01/15/new-social-web-working-group-at-w3c/
My original link was for the group’s kick-off meeting. I should have linked to the announcement as well.
I hope it went well, Darius Kazemi (npub1fd2…f2f9)! Thanks for being the chair. 👏🏻
#Mastodon #Fediverse #W3C #ActivityPub #FOSS #SmallTech
Today the [W3C](https://w3c.org/ ) standards organization [announced a new working group](https://lists.w3.org/Archives/Public/public-socialweb/2026Jan/0000.html ) to advance the ActivityPub and Activity Streams standards. The Social Web Foundation, as a W3C member organization, will be participating in the group. The working group’s goal is to release a backwards-compatible iteration of each specification in Q3 of 2026.
Activity Streams was released in 2017, and ActivityPub was released in early 2018. Since that time, the experience of hundreds of implementers and millions of users has shown places that the specifications are confusing or unclear, or missing features. Some problems have been documented with [errata](https://www.w3.org/wiki/ActivityPub_errata ), but others require more work. The [Next Version](https://github.com/w3c/activitypub/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Next%20version%22 ) tag in the ActivityPub GitHub issue repository gives some good examples of topics to be considered. The new Social Web Working Group will provide revisions of these documents to make them easier to use for implementers.
ActivityPub is an actively used protocol with millions of users and billions of notes, images, video and audio files published. Standards work on ActivityPub will necessarily be evolutionary, not revolutionary, and will incorporate backwards compatibility. Developers can confidently keep working on ActivityPub today without worrying about breaking changes in the future.
The Social Web Working Group will work closely with the [Social Web Community Group](https://www.w3.org/groups/cg/socialcg/ ), the organization that has been stewarding ActivityPub and its extensions since 2018. The Community Group will remain the focal point for innovative developments extending ActivityPub into different areas like [geosocial](https://github.com/swicg/geosocial ) applications or threaded forums, while the Working Group will concentrate on the core documents.
One Community Group document that will be moving into the Working Group is [LOLA](https://swicg.github.io/activitypub-data-portability/lola ), the live data portability spec that originated in the CG’s [Data Portability Task Force](https://github.com/swicg/activitypub-data-portability ). LOLA lets users move from one ActivityPub server to another while retaining all their social connections, their content, and their reactions. It’s a great improvement for data portability on the social web.
The Social Web Working Group will consist of representatives of W3C member organizations and [invited experts](https://www.w3.org/invited-experts/ ) from the standards and development community. The group will be chaired by [Darius Kazemi](https://tinysubversions.com ), longtime contributor to the ActivityPub developer community. Meetings and proceedings will be public, and developers can review the work happening in the [ActivityPub GitHub repository](https://github.com/w3c/activitypub/issues ).
Thanks to everyone who’s done the work getting this charter to completion; especially [Dmitri Zagidulin](https://social.coop/@dmitri ), the SocialCG chair who drove the charter editing and review process. Now, the work begins!