Around nine months ago the Beehaw admin team decided that we wanted to migrate to a Lemmy compatible software stack called Sublinks. Unfortunately, Sublinks is not yet Lemmy compatible—among other things the main dev recently had a child, and understandably that is taking priority currently. This means that plan to migrate is indefinitely on hold.

In addition, Lemmy has evolved and changed in a way that is simply not feasible for us to continue being behind on. In the upcoming 1.0 Lemmy release there are a number of breaking changes that would be problematic. This would be on top of existing third-party app issues with the older Lemmy version Beehaw runs, and bug-fixes and security improvements from later versions of Lemmy that we have to handle ourselves. We don't want our users to continue having friction or issues using Beehaw, or end up not able to federate with other instances. As such, within the next month or so, Beehaw admins will be working on upgrading Lemmy to the current/main release.

We're separately optimistic that with Lemmy API version 1.0 the Sublinks devs will have a good target to aim at and work towards, and though development is slowed we will continue assisting them toward an eventual Sublinks migration of Beehaw. We look forward to their first full operational release.

you are viewing a single comment's thread
view the rest of the comments

[–] Penguincoder 7 points 2 days ago

It wouldn't work for the down voting, but has some easier extensibility if we wanted to fork and make it more for Beehaw. We're hoping to work with Sublinks to get those mod and admin tools baked in from the start VS forking or the constant patch changes we do with Lemmy.