When writing the initial version of our project plan as signed and agreed with by NlNet we didn’t know yet about the dynamics of the community, specifically about how the cooperation between the maintainers of the #WordPress #ActivityPub plugin and #Mobilizon would be like. The level of collaboration with other #Fediverse developers would determine whether our project goals could only be achieved through a series of workarounds, or whether we could work together to strengthen interoperability and compatibility in the Fediverse.
Mobilizon was the first Fediverse application with true event federation. #Gancio has very limited ActivityPub capabilities, partly by design, but is working on an enhanced federation, and other services like #Friendica have a very different approach to events: their implementation focuses on sending invitations rather than publishing events. #Pleroma might get initial event support soon and it’s fork #Rebase already implemented it. As is usual with any software, you will find a lot of small bugs if you have not done any tests beforehand. In the case of Mobilizon, this was not possible since there were no alternative platforms to do the tests with in the past, especially if it comes to the instance-to-instance federation, so the only option was to test the Federation with other Mobilizon servers. We seem to be the first and we are fascinated and incredibly grateful for the willingness and prioritization that such issues have among the other developers (thanks to tcit and les). The issues may seem small, but they have a big impact: 304, 33, 321, 1509, 1507, 1392, 1385, 1388, 1387, 1378, 1376.
The other deciding factor for us was that we didn’t know how close the interaction with the upstream WordPress ActivityPub project would be. The exchange of ideas and the desire for a joint solution is strong. We would like to thank @pfefferle again for the regular exchange, his ideas and inspiration, without his commitment to the community our project would be less sustainable.
Tasks done (almost)
- We published a repository that aims to make it easy for other developers, including ourselves to start developing and debugging WordPress along with Mobilizon.
- We have created a pull request to add management of various ActivityPub transformers to the admin interface. The current implementation basically works, but we have a lot to polish and improve on our roadmap.
- Using that patched ActivityPub plugin we explored writing transformers for two popular event plugins, this gave us a lot insight on what is important. These transformers already have fundamental compatibility with Moblizon.
- Updating our About us page showing some information who we are.
- Implement FEP-2677: Identifying the Application Actor
- Implement the followers list of the application actor in the admin UI along with the ability to reject, approve, and remove followers. We are very inspired by how #PeerTube has solved this in the admin UI. This of course includes a an option as:manuallyApprovesFollowers that can be set for an ActivityPub actor within WordPress.
- Write an initial draft of the user documentation informing about custom ActivityPub transformers and instance-to-instance federation with Mobilizon. The target audience will be non-tech people. Parts of this will also be used as a non-tech description of our project.
- Improve the admin UI and propose a solution to handle the settings for each transformer, if there are any.
- Write more transformers for other popular event plugins to discover common pitfalls.
If you have any questions, ideas, or would like to help us, for example by testing our progress in case your are running a WordPress site with events yourself, please don’t hesitate to contact us. We don’t care if you have technical experience or what your background is: any kind of involvement is valuable to us.