I see a lot of comments pointing out bugs and saying something along the lines like “they need to fix this ASAP, otherwise… something something”.

As a software developer myself (not in the fediverse), I can tell you one thing:

Keep in mind that all of this literally escalated pretty quickly, and no one was prepared for that. What started out as a hobby project of some enthausiasts, quickly turned into a high demand over the course of a few days.

Having hundreds of enthusiasts use a software is different than having thousends of “average” people using it. 100 users won’t detect many bugs, and if they do, they’re more tolerant since they know it’s all volunteering. But thousands of users will detect even more bugs that no one bothered to deal before.

Once the userbase grows and the demands are clear enough, this should be tackled, eventually.

So yeah, hang in there.

  • kreynen@kbin.social
    1·
    1 year ago

    So is Kbin. Both projects use the AGPL license, but Kbin is a PHP/Symfony based solution while Lemmy is primarily a Rust backend with a Typescript front end. If someone is going to run an instance or contribute to the code, they are likely going to choose the stack that they are most familiar with.

    With a lot of #Drupal experience, the Kbin code is very approachable for me… but as other commenters have already said… whatever floats your boat.

    The Kbin and Lemmy projects aren’t competing as much with each other as the ActivityPub driven communities are competing with the walled gardens.