So I try to make heads or tails of this situation. I got randomly banned from a community where I posted a youtube video showing something from a Convention. Then I wanted to post a question today but realised that I couldn’t since I was banned. That community is sadly the biggest of all Star Citizen communities (the next one would be from lemmy.world)

I took a look at the Mod log and see the following line in it:

So no clean up of violating comments or posts, just a strict out ban.

The community has a pretty standard ruleset:

further, the moderator @Rumblestiltskin@lemmy.ml hasn’t posted anything since a year, so what gives here, or was it some other mod that was able to declare the ban?

  • Draconic NEO@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    2
    ·
    11 days ago

    The only ways that I know of to user-block Lemmy.ml:

    There is a also another way, I saw someone suggesting that a person could contact a remote instance’s admins and have their accounts and data removed from the instance. Essentially requesting a ban.

    The big drawback to all but one of the methods listed above is that they are false-assurance or cosmetic/curation blocks, not functional blocks. And with some of the more problematic instances out there, false-assurance is almost worse than nothing at all. With your posts and comments removed from your instance you’ll never receive replies or attacks from users on that instance, they’ll just never see your content anymore.

    It makes sense that most instance admins do not want to defederate though, b/c some communities are still held hostage on the lemmy.ml instance - e.g. !firefox@lemmy.ml with 3.6K MAU (monthly active users) vs. the next largest one !firefox@lemmy.world with only 0.7K MAU, that’s an enormous difference!

    That’s why admins need to defederate it more often. If Lemmy.world alone gave them the boot it would slash their userbase in those communities significantly. It’s very likely that the moderators there would move or a large amount of other users would move. They’re not going to though unless they have to, and making it easier by keeping the door open only slows that down from happening.

    But so long as you continue to use the Lemmy software, what right does anyone have to complain about how the devs wish to implement their own code, which they wrote for themselves, for their own desires and ends?

    I would say every reason since the nature of open-source code means you can fork it and use it how ever you want. Especially given that many people are contributors. I say if you want complete control and don’t want to hear complaints about your code and platform don’t license as GPL and make contributors waive their IP ownership to the devs when contributing code. They didn’t do any of this though.

    If we want better, we have to make things that are better, on our own.

    Sublinks is looking very promising as a replacement for Lemmy not only is it written in a more well known language than Rust it’s also aiming to have more features while remaining mostly compatible with the Lemmy API.

    • OpenStars@piefed.social
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 days ago

      I don’t know how you would force compliance with a different instance though, especially if it is not located in the EU.

      In the end we can only control ourselves - e.g. note I’m writing this from a PieFed account:-). But yes Sublinks is a very exciting development as well, though I have not heard any developments for many months when it was mentioned that it was not stable yet.

      And yes someone could fork the Lemmy codebase. Many instances including Lemmy.cafe and Tesseract on dubvee.org have done exactly that, though unlike Mbin (since Kbin is now defunct) they don’t want to get too far ahead of the main branch so that they can still receive future updates easier, whereas PieFed and Sublinks and Mbin are each entirely separate projects from Lemmy to begin with, though they are interoperable with those federated communities which is awesome 😎.

      • Draconic NEO@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        1
        ·
        10 days ago

        I don’t know how you would force compliance with a different instance though, especially if it is not located in the EU.

        If you’re in the US and they’re in the US or countries that have copyright treaties you can request removal under DMCA since you own your posts and comment content. And if you don’t agree to their TOS or licensing it’s a kind of a grey area for them. Still not completely foolproof since if Instance admins are willing to go further than you’re willing to go (i.e. not complying without a lawsuit), you can’t really do much about it.

        In the end we can only control ourselves - e.g. note I’m writing this from a PieFed account:-). But yes Sublinks is a very exciting development as well, though I have not heard any developments for many months when it was mentioned that it was not stable yet.

        Yeah especially because Rust is much harder to contribute to. Once Sublinks gets off the ground I feel like there will be more people eager and willing to contribute code. I’m hoping that it’s still going since there would be great benefit in this project being an option.

        And yes someone could fork the Lemmy codebase. Many instances including Lemmy.cafe and Tesseract on dubvee.org have done exactly that, though unlike Mbin (since Kbin is now defunct) they don’t want to get too far ahead of the main branch so that they can still receive future updates easier, whereas PieFed and Sublinks and Mbin are each entirely separate projects from Lemmy to begin with, though they are interoperable with those federated communities which is awesome 😎.

        I believe Programming.dev does it too, they call it Pangora though they’re currently restructuring it to be a fork of Sublinks so they haven’t worked on it much at the moment. Also Tesseract is an alternate frontend of the Lemmy software, not a different software. It does improve Lemmy greatly though.