Is full instance blocking as a user unavaliable because it’s not in the version this instance runs or has it been disabled?
If it’s the latter could it be enabled? As there are some instances I’d like to block as a user that don’t necessarily need to be to blocked from an instance perspective (though maybe they should be).
If it’s the former, any idea how long before y’all will update to a version with it in? Thanks!
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.
This is precisely what I was looking for just now. I was trying to determine what the next steps for beehaw were. Could anyone provide a link to an announcement from beehaw? I’m going to look into sublinks later today. A cursory look shows that it’s lemmy compatible and has better moderation tools. I know this has been one of the key reasons why beehaw struggled with the current version of lemmy they are using. I’m very curious about it now.