I want to address some of the issues you brought up, @hrefna.
We are taking on a few, very bounded projects to start of with the SWF. We will be executing on this work, while we plan out projects throughout 2025. Sometimes, you need to work on the tasks that you can actually complete, rather than the tasks that are most important.
I’m taking the suggestions you have for our new projects pipeline. There are a few I need more info for, though:
- What do you mean by “registry”? Registry of software, extensions, something else?
- What do you think we could do to address homogeneity in independent software implementations?
- Feditest is working on testing; do you think there is more work to do here?
For E2EE, my user interface research shows that the lack of E2EE is a big inhibitor for people to use DMs at all, and that DMs are a crucial part of the stack for having real, human relationships happen on the Fediverse.
For the GDPR work, it will be an analysis of how and whether ActivityPub implementations can be compliant with GDPR requirements. Other work has been done in this space, but we want to pull it together into one document for implementers and for policy-makers.
For the question you ask, will it help small developers?, it’s a good question. We are more interested in helping users (sorry, @hamishcampbell ) get on, and stay on, the Fediverse, and have a good experience while there. If supporting small developers does that, I think it’s a good goal.