Skip Navigation

Admin update - Hexbear Defederated

This is an admin post, intended for blahaj lemmy users. Top level posts from members of other instances will be removed.

==

Edit - Hexbear announced plans to deferedate from us.

==

After recent events, it feels to me that sentiment has shifted and more people are asking for defederation of hexbear than previously

I've been doing my best to try and mend bridges and keep us connected, as it's my hope that we can maintain trans solidarity and work with them, despite the friction, however, ultimately, I feel that this is an issue for the blahaj lemmy community to decide, not the admins alone

So here's what we're going to do

We're going to leave things as they are for a week. That will give time for things to calm down whilst we see if we can work together. After a week, I'll put up a vote and get a feel for where the community is at in regards to our continued federation with hexbear. That poll will run for a week. If there is a strong will to defederate (a clear majority), then that's what we will do

284

You're viewing a single thread.

284 comments
  • I do want to say that user level instance blocking is in the works: https://github.com/LemmyNet/lemmy/pull/3869

    • That will solve so many problems!

      • Oh and I had a suggestion. If you're able to, look at the poll figures for accounts created after this announcement vs the figures for pre-existing accounts. There may be evidence of people attempting to steer the results one way or another.

      • The Android app "Connect" does instance blocking and it's so useful!

    • It's too bad that it doesn't also block comments from users of blocked instances. Isn't there a uBlock Origin cosmetic filter that does that? Does anybody remember what that was?

      Also, does anybody know of a way to browse two instances as one feed, and easily switch between users? I swore I heard there was some way to do that, but I don't remember the details.

    • I’m not a GitHub user, although I’ve done some browsing of open issues. Am I seeing that this feature has been coded (or is actively being coded) or am I just seeing that people are still discussing the issue?

      I ask because last time I looked (probably 2-4 weeks ago), I saw some discussion on the issue dating back to over a year ago, but nothing that looked like actual traction on it getting implemented.

      • Its a pull request so its probably at least mostly complete

        • Thanks for that. Looking again, I see now at the top that I’m looking at pull requests and not “issues”. And because I don’t really know, I just looked up what pull requests are:

          Pull requests let you tell others about changes you've pushed to a branch in a repository on GitHub. Once a pull request is opened, you can discuss and review the potential changes with collaborators and add follow-up commits before your changes are merged into the base branch.

          So that means that code has been written and requested to be merged into the main branch. Does that mean it’s already been tested in a non-main branch and is (hopefully) ready for prime time after some final review?

          • Yeah, assuming the code is ready (im not very good at programming so idk) the owners of the repository just have to merge those commits and the feature will end up in a subsequent release

You've viewed 284 comments.