this post was submitted on 10 Aug 2024
7 points (100.0% liked)
Beehaw Support
2797 readers
1 users here now
Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.
A brief FAQ for lurkers and new users can be found here.
Our September 2024 financial update is here.
For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The goal (and the hold up thus far) is to migrate to Sublinks, with no downtime or noticeable issues for end users. Unfortunately there are a few blockers on the 'Lemmy parity' feature set in Sublinks. So we Beehaw admins assuredly want to migrate ASAP. Doing so right now would inconceive Beeple, or worse, remove functionality. We're in a holding pattern. Right now Beehaw is operational, and beyond everything else, that is the goal. Apps likely WON'T work with our current Beehaw Lemmy stack. They should work after the migration to Sublinks, with a Lemmy compatible API.
Thanks very much for explaining! I completely understand that things take time and thus no rush, was just curious about what was going on, appreciate the information and the great work y'all do!
Would you be willing to elaborate a little bit as to what the roadblocks are with Sublinks right now? Just curious, and the feature set/current status is not super obvious in their github.