Misskey is an unprecedented forking party. Sharkey is one of the many forks. Maintained by the Blåhaj folks, if I’m not mistaken.
Iceshrimp is another one to watch. Specifically Iceshrimp-NET, a full rewrite to fix the performance issues that probably play some role in why these forks often meet such sad ends.
It’s not so much the performance issues that kill the projects – instances with hundreds to a couple thousand users are very, very healthy for the fediverse – it’s that the codebase is…
Well, Misskey is a 10-year-old solo development project that’s been cancelled at least once by the dev due to burnout, with documentation partially in broken english, and the rest in Japanese. Working with it is… yeah…
I wish a lot of Western fediverse community helps Misskey dev in documentation and development.
It’s sad that sometimes they don’t want help Misskey community to globalize, and just soft-fork and even hard-forking the software. Misskey community is desperately need global contributor.
I would really love a more globalized development for misskey, but it is easier said than done. Majority of bug reports, release notes and even some comments are written in Japanese (yk kana/Kanji). It would take a lot more than translating the documentation. It is hard to even report a bug (without worrying if there is a bug report already present in Japanese) let alone fix one.
It’s just there’s a concern that any FOSS project that developed by non-English speaker will “force taken” by another “Western” maintainer. If we want fediverse to be truly inclusive, language barrier is something should be taken care for further maintreamization.
Maybe we can learn from English Asia community (usually on Facebook group) that already practicing multi-language community, where each people can speak their own language and still properly moderated and connected.
I thought Calkey went belly up, so to speak.
Misskey is an unprecedented forking party. Sharkey is one of the many forks. Maintained by the Blåhaj folks, if I’m not mistaken.
Iceshrimp is another one to watch. Specifically Iceshrimp-NET, a full rewrite to fix the performance issues that probably play some role in why these forks often meet such sad ends.
It’s not so much the performance issues that kill the projects – instances with hundreds to a couple thousand users are very, very healthy for the fediverse – it’s that the codebase is…
Well, Misskey is a 10-year-old solo development project that’s been cancelled at least once by the dev due to burnout, with documentation partially in broken english, and the rest in Japanese. Working with it is… yeah…
I wish a lot of Western fediverse community helps Misskey dev in documentation and development.
It’s sad that sometimes they don’t want help Misskey community to globalize, and just soft-fork and even hard-forking the software. Misskey community is desperately need global contributor.
I would really love a more globalized development for misskey, but it is easier said than done. Majority of bug reports, release notes and even some comments are written in Japanese (yk kana/Kanji). It would take a lot more than translating the documentation. It is hard to even report a bug (without worrying if there is a bug report already present in Japanese) let alone fix one.
Yeah, I acknowledge that.
It’s just there’s a concern that any FOSS project that developed by non-English speaker will “force taken” by another “Western” maintainer. If we want fediverse to be truly inclusive, language barrier is something should be taken care for further maintreamization.
Maybe we can learn from English Asia community (usually on Facebook group) that already practicing multi-language community, where each people can speak their own language and still properly moderated and connected.