 If you are an implementor of #ActivityPub, or any related social web apps or protocols, please try to come to the meeting on the future of ActivityPub standardization and related subjects next Wednesday, March 29. It's on-line and hosted by #FediForum and the W3C's Social Web Interest Community Group. We want to hear from you! Standards should not be created in a vacuum. If you have tried to use ActivityPub (successfully or not!), tell us what you need! And perhaps get involved making it so. 12 comments
 As someone who has already extended ActivityPub way too much, I may be interested in this @grishka It would be interesting to know what you extended, for what use cases, and why you think it was "way too much" compared to what you presumably wanted the standard to do. Johannes, I'm building Smithereen, an ActivityPub server that offers a Facebook-style UX. There are walls like in Facebook, so I had to extend the protocol to allow them to federate. Then there also are groups and events. And invitations. And tentative membership in events. These are all things that no one before me even tried to implement with ActivityPub. (this comment is sent from a Smithereen server btw) @grishka Interesting! Found the code, but is there an instance somewhere I could try it out?  Went to https://friends.grishka.me/system/about. Then saw https://smithereen.software/, clicked it but got Deus, hm. I never enabled SSL on that domain. But it simply redirects to the github repo for the time being. My fault. Had enabled  @J12t https://fediforum.org/fediforum-w3c-swicg-2023-03-29/ tomorrow at 10am Pacific, right? |
Gregory's Server
And if you are a user of a #ActivityPub-based app, and you love the interoperability you get with other #apps in the #fediverse, tell the developers your #app that this meetings is coming together, and they should participate.
Who knows, maybe we manage to make implementing #ActivityPub easier, more interoperable, with new features and what have you! That is much easier if app developers are involved directly, because they know what they need to make their apps better.