@ernest how do I report a Magazin on kbin.social ? There is a usere called “ps” who is posting to his own “antiwoke” Magazin on kbin.social. Please remove this and dont give them a chance to etablish them self on kbin.social. When I report his stuff it will go to him because he is the moderator of the magazin? Seems like a problem. Screenshot of the “antiwoke” Magazin /sub on kbin.social. 4 Headlines are visible, 2 exampels: “Time to reject the extrem trans lobby harming our society” “How to end wokeness” #Moderation #kbin #kbin.social 📎

edit: dont feed the troll, im shure ernest will delet them all when he sees this. report and move on.

  • I just need a little more time. There will likely be a technical break announced tomorrow or the day after tomorrow. Along with the migration to new servers, we will be introducing new moderation tools that I am currently working on and testing (I had it planned for a bit later in my roadmap). Then, I will address your reports and handle them very seriously. I try my best to delete sensitive content, but with the current workload and ongoing relocation, it takes a lot of time. I am being extra cautious now. The regulations are quite general, and I would like to refine them together with you and do everything properly. For now, please make use of the option to block the magazine/author.

    •  Noki   ( @Noki@kbin.social ) OP
      link
      fedilink
      42
      edit-2
      1 year ago

      thank you!

      I appreciate all you do and your quick respond.

      Multipile Things I noticed as a creater of this thread:
      can I close comments ?
      can I hide comments ?
      can I pin a response?
      can I quickly see from what server peope are interacting?

      I am no coder but would love to support you with all the work that is done.

      At least some of the costs can be taken of your shoulders:

      https://www.buymeacoffee.com/kbin

      Edit: Can you close this thread for me ?

      • All the things you mentioned are in the roadmap. However, we can either do it quickly and potentially encounter issues in a few weeks or months, or take a bit more time for a more thorough approach. I’ve decided to move away from playful prototyping. From now on, every change will be tested before it’s approved for kbin.social - it’s no longer just my code (https://lab2.kbin.pub/). I’d like to close this thread for you… but can we just agree not to respond in it anymore? ;p

        • I don’t think closing threads is a great idea or in keeping with how this all works. I think it’d be nice to be able to mute a thread as an individual, but by its nature these discussions are open and shared with many instances. If we close it on kbin.social, other kbin instances, lemmy instances, and even places like mastodon and pixelfed could keep discussing, if I understand activity pub correctly.

          • In such important tasks, I would like to engage in community-driven development. When I start planning these tasks, I will come to you with my whiteboard and sketch out the individual stages. Together, we will look for the advantages and disadvantages of such a solution, the weak and strong points. This is to jointly make a decision on whether the change makes sense on kbin.social but also in the perspective of the entire federation. It can be a great fun ;)

          • Let’s all agree that of its many issues, locking/deleting open threats to targeted minority groups and pro supremacist propaganda meant to hurt or influence vulnerable people was NOT a drawback of the Reddit experience.

            Yes, it’s a difficult thing to enforce a subjective line of a basic standard of decency, but it’s also what a society is and one of the main reasons we gather as people. The quality of a group is shown in how they accommodate the weakest and most vulnerable among them.

            If we aren’t prioritizing a way to send this CHUD and people liked them to the hypothetical edge of town, to be sure they can’t bombard the young person struggling with their gender identity with targeted hate at their weakest moment, then what are we doing here?

    • I joined kbin recently and I’m kind of concerned about the implications of this. I don’t support those posts at all, but who gets to say what’s worth banning and what not? Wouldn’t that go against the decentralized nature of the site? Or is it the specific instance that magazine is on that has the authority to ban what’s inside? How does all of this work?

      Edit: my bad, I got kbin and kbin.social mixed up. Noob mistake.

      • kbin.social administration controls only what is published on kbin.social, and what content from elsewhere kbin.social users can see. An user banned from kbin.social can make another account, on another site and start recreate there his banned community. kbin.social will be able to ban this remote user and remote community, but this restricts only what kbin.social users can see.

        Exactly the same for another /kbin or lemmy site - just replace the domain name accordingly.

      • Wouldn’t that go against the decentralized nature of the site?

        No, it’s exactly the opposite. The entire point of a decentralized federation is that while yes, the admin is in complete control of what content is allowed on his or her own instance, users who don’t like what the admin is doing can just spin up their own new instances.

        Ernest can ban this type of content if he likes. Others can take the kbin software and make a new instance where it’s welcome. Ernest can choose not to federate with that instance if they continue to push content that’s against his rules, but Ernest doesn’t have the power to dictate the direction for hundreds of millions of users’ experience like a certain centralized site’s mad CEO or admin board does.

        What would be against the nature of ActivityPub is if Ernest built something into the software to prevent it being used for types of content he doesn’t like, even on other instances.

      • Remember, kbin.social is just one instance of kbin. Ernest banning something on kbin.social does not mean banning it from the fediverse.

        It could pop up on another fediverse site or even another kbin site.

      • “who gets to say what’s worth banning and what not?”

        Just like with privately hosted services like Twitter and Reddit, it’s the person/group hosting the content. The decentralized nature means that if you disagree, you can voice that, or host your own instance, or move elsewhere that aligns with your viewpoints. Some people have multiple accounts spread out across instances to see different kinds of content.


        Rambling below, you can stop reading here if you want.

        Being federated doesn’t mean moderation can be ignored on either end. Some groups may not want to deal with certain content that others want to (could be for personal or legal reasons), and that’s OK. Since individual posts can’t be moderated across instances, if there are big patterns of moderation disagreements, then defederation is the only option and that’s usually not fun for anyone, so it’s generally in everyone’s best interest to stay generally acceptable to everyone else.

        Of course, nothing is forcing that. There are currently instances defederated from my home instance Beehaw, for example. I’d imagine they’re still doing just fine without that federation, too. It can be argued that it’s against the spirit of federation, but at the same time you really can’t expect people to want to host data on their server that may not be morally or legally acceptable to them.

        (This is all ignoring purpose-driven instances. People can choose to make an instance where only a specific kind of content is available, too. It’s much easier to manage that kind of instance due to the smaller scale, but as with anything there are downsides to that, too.)

    • The regulations are quite general, and I would like to refine them together with you and do everything properly.

      I have been wondering how instance-wide moderation will end up looking on kbin, once you’ve had a chance to get a team in place for that. While it is (I assume) a “generalist” instance, it’s important to keep in mind that you can’t please everyone. Trying to have too broad of an audience will just result in retaining those with a high tolerance for toxicity (usually highly toxic themselves), while everyone else leaves in favor of better-managed spaces.

      Communities in general, and particularly on the internet, need to understand what their purpose is, and be proactive about filtering out those that are incompatible with that purpose. This doesn’t mean judging those people as wrong, or “bad people”, it just means recognizing that not everyone is going to get along, and that some level of group cohesion needs to be maintained.

        • I think there is value in having both generalist and specialized instances, and the big landing spots for new users should probably strive to be more generalist. As you point out though, there are limits to how broad of an audience one can practically cater to.