Hi, just moved to Beehaw and liking the experience and community a lot - this place is so much more chill and civil than reddit.

However, I just discovered that instances can block each other and I dislike the concept. Don’t get me wrong, I like safe spaces and moderation, and that the blocked instances in general are not great. But I dislike that I, as a user, can’t even browse another community just because the admins decided it, and worry that it would just lead to echo chambers and block wars between instances that end up isolating each other.

I think a soft block, where in communities from flagged instances don’t show up by default anywhere, and where users have to explicitly seek them out to browse or subscribe is a much better option.

I am enjoying my time on Beehaw and would like to continue to do so. Is there any option for me to subscribe or browse a community from another instance?

  •  jherazob   ( @jherazob@beehaw.org ) English
    4•1 year ago

    Blocking instances is not done lightly, and it’s usually done leaving visible moderation logs. Still, if you dislike that you can go to an instance that has not blocked the one you want.

    As for looking at communities of an instance, you can always go to the instance itself directly and browse things there.

    •  shufflerofrocks   ( @shufflerofrocks@beehaw.org ) OPEnglish
      2•1 year ago

      I mean, yeah, leaving is always an option - but I would rather prefer exploration of the possibility of a better solution. Not to mention, there doesn’t seem to be an option for moving your account from one instance to another. I would like to keep my comment and post history if I ever do move instances.

      Besides, leaving might not be the ideal solution, as blocked instances seem to block back, and many instances have a “follow our blocklist, or we will block you” rule from what I have been reading.

      you can always go to the instance itself directly and browse things there.

      Eh, I would like to access all the stuff I want to see in one feed, ideally.

      •  jherazob   ( @jherazob@beehaw.org ) English
        2•1 year ago

        Sometimes communication breaks. There’s many reasons this happens but many times it’s inevitable. If it comes to the point that instances get defederated likely there were attempts to not get to this point, which failed. Might not be convenient to you but it’s how things are. If an instance goes very much against the Beehaw ideals there’s no reason to keep federating it, even if inconvenient, as it would start affecting this instance, go check out the Beehaw philosophy posts for what that is and why.

  •  alehel   ( @alehel@beehaw.org ) English
    3•1 year ago

    In my personal opinion, a block should stop an instances users from posting to, but not browsing an instance. Keep the information open, while retaining the ability to block bad actors. That’s obviously not a change that’s up to beehaw of cours.