this post was submitted on 18 Sep 2023
48 points (100.0% liked)
Beehaw Support
2797 readers
17 users here now
Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.
A brief FAQ for lurkers and new users can be found here.
Our September 2024 financial update is here.
For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Thanks for your reports on it. We try to action it as quickly as we can, and your reporting it helps us. We are attempting a few other Beehaw-only Lemmy changes to mitigate this sort of spam; short of de-federation. One of the major issues is that Kbin does not federate moderator actions. So they could have already dealt with the spammer and removed the posts, from Kbin. Those actions don't get to us on Beehaw and the spammer posts still lives.
OHHHH! This explains a lot. I had assumed kbin was doing nothing, but they could be removing the posts/accounts, but that doesn't carry over to us.
Wow, that's a HUGE drawback to how federation is handled, isn't it?
It’s a major hole with regards to spam, but in a hypothetical whistleblower scenario it makes it hard for a single entity to silence and remove all evidence.
There are simply trade offs, but it doesn’t mean there isn’t room for improvement.
Given the nature of the internet, I feel that spam is a much bigger problem than a potential whistleblower being silenced, and wouldn't that kind of action show up in the logs anyways?
As a former admin, I guarantee no one seriously reads those logs outside of happenstance. It takes the users speaking up to warrant that.
The whistleblower can read (or ask someone to read) the logs and find out who silenced them, then whistleblow that/get get whoever did it defederated.
Deleting spam isn't optional. If you leave it there your community is dead.
What I meant with whistleblowing in terms of the fediverse is:
Whistleblower posts to instance A, and it gets mirrored on instance B.
Someone like Musk erases the post on instance A.
As the Fediverse currently works, the whistleblowing still exists on instance B, and cannot be deleted by an admin on instance A.
Asking a Musk to divulge who did the silencing is an exercise in futility.
That said, I’m totally on board with better tools to handle spam.