Just recently, I received a grant to develop from scratch the single-person, self-hosted microblogging engine NLnet; #Seppo! being part of the fediverse but also offering a lean (atom) approach as well (inspired by https://mro.name/ShaarliGo).
What else do you think should be considered?
How do you recommend to test federation?
Congratulations mro on your grant!
I guess you’ll be pretty busy just getting the basics going. Nice job on your repo: https://codeberg.org/seppo/seppo#seppo
For me the best thing after basics is to get users and just keep solving their problems. Trading design and roadmaps for a steady stream of solutions to valuable problems is core to my favorite project management paradigm.
For testing, this was a neat idea but it fizzled out. I’d be interested to help resurrect it or to know of a replacement. I think many projects just setup other servers and do it manually or rely on bug reports.
Learned of another test suite which is up for grabs:
and there’s also go-fed’s
GitHub - go-fed/testsuite: Unofficial ActivityPub test suite server, which runs machine-assisted test cases against federated software.)
the latter has an expired cert as usual, but is maybe hostable without containers, dbs and stuff.