Conversation

Notices

1. Jenniferplusplus (jenniferplusplus@hachyderm.io)'s status on Wednesday, 01-May-2024 23:01:44 UTC Jenniferplusplus

   I don't know who needs to hear this, but I'm getting tired just thinking about the testing path you would need to follow in order to fork mastodon and keep it as an in-place upgrade from baseline.

   1. stand up a baseline mastodon instance
   2. federate with some peers
   3. fill it with realistic data
   4. migrate to the fork
   5. test the fork
   6. test federation
   7. repeat across several combinations of mastodon base versions and other fedi servers
   8. rapidly, during development

   • Jenniferplusplus (jenniferplusplus@hachyderm.io)'s status on Wednesday, 01-May-2024 23:01:43 UTC Jenniferplusplus

     in reply to

     Extremely not comprehensive list of ActivityPub microblogging projects you could contribute to, instead of forking mastodon

     https://github.com/superseriousbusiness/gotosocial
     https://github.com/misskey-dev/misskey
     https://github.com/bonfire-networks/bonfire-app
     https://github.com/go-ap/fedbox
     https://akkoma.dev/AkkomaGang/akkoma
     https://iceshrimp.dev/iceshrimp/Iceshrimp.NET
     https://github.com/Letterbook/Letterbook

   • Jenniferplusplus (jenniferplusplus@hachyderm.io)'s status on Wednesday, 01-May-2024 23:01:44 UTC Jenniferplusplus

     in reply to

     If in-place upgrades aren't the goal, then just build something new. Or contribute to one of the various preexisting projects. Don't adopt mastodon's tech debt for no reason. It's not worth it.

     I know I'm eager to have more help, if existing projects suddenly sound better.

     rosa roja repeated this.