cross-posted from: https://beehaw.org/post/570507

After the (temporary) defederation announcement of earlier i checked the Lemmy repo to see if there was already a ticket on the federation limiting option like Mastodon’s that people mentioned Lemmy doesn’t yet have. Not only i didn’t find it, i also saw that there’s about 200+ open tickets of variable importance. Also saw that it’s maintained mostly by the two main devs, the difference in commits between them and even the next contributors is vast. This is normal and in other circumstances it’d grow organically, but considering the huge influx of users lately, which will likely take months to slow down, they just don’t have the same time to invest on this, and many things risk being neglected. I’m a sysadmin, haven’t coded anything big in at least a decade and a half beyond small helper scripts in Bash or Python, and haven’t ever touched Rust, so can’t help there, but maybe some of you Rust aficionados can give some time to help essentially all of Lemmy. The same can be said of Kbin of course, although that’s PHP, and there is exacerbated by it being just the single dev.

  • PrincipleOfCharity@0v0.social
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 years ago

    I’m not super concerned. It’s been a little over a week since stuff hit the fan. Contributors need time to learn the code base. People are starting to help with the easy stuff, but the two main devs still need to check everything because they are the only ones that can understand how those changes affect long term visions. Also, the urgent fixes are all somewhat-breaking changes which is why it’s looking like the next release is going to be 0.18 instead of 0.17.5. It makes sense to get as many urgent breaking changes in as they can before publishing, and it’s only been 8 days since the last release to identify, code, and test.