this post was submitted on 18 Sep 2023
41 points (100.0% liked)

Beehaw Support

2797 readers
3 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.


if you can see this, it's up  

founded 2 years ago
MODERATORS
 

Permanently deleted

you are viewing a single comment's thread
view the rest of the comments
[–] LinkOpensChest_wav@beehaw.org 24 points 1 year ago (4 children)

One of the major issues is that Kbin does not federate moderator actions

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?

[–] Wooster@startrek.website 8 points 1 year ago (1 children)

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.

[–] Crankpork@beehaw.org 9 points 1 year ago (2 children)

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?

[–] Wooster@startrek.website 6 points 1 year ago (1 children)

As a former admin, I guarantee no one seriously reads those logs outside of happenstance. It takes the users speaking up to warrant that.

[–] abhibeckert@beehaw.org 3 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] Wooster@startrek.website 3 points 1 year ago

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.

[–] Drusas@kbin.social 4 points 1 year ago (1 children)

It's a bug which Ernest is working to correct.

[–] LinkOpensChest_wav@beehaw.org 3 points 1 year ago (1 children)

It's not a bug, and I don't think it will be corrected. It's fundamental to how federation works on Lemmy.

[–] Drusas@kbin.social 3 points 1 year ago (1 children)

That is not what I have read Ernest say elsewhere.

[–] LinkOpensChest_wav@beehaw.org 2 points 1 year ago (1 children)

Sounds like he's offering false hope then. Afaik Lemmy was designed that way.

[–] Drusas@kbin.social 2 points 1 year ago

We'll see. Can't say I've been keeping up too closely on the specifics. But I have been a happy kbin user. Guess I'll have to catch up a little more thoroughly.

[–] theangriestbird@beehaw.org 4 points 1 year ago

For real. I knew that Lemmy was a mess but this feels inexcusable. How could you NOT federate mod actions!?

[–] Penguincoder@beehaw.org 2 points 1 year ago (1 children)

Can't say we're 100% responsible for the reduced spam lately; but wanted to get your thoughts. Has there been less Kbin spam lately? Do you feel our countermeasures are working well since a few weeks ago?

[–] LinkOpensChest_wav@beehaw.org 2 points 1 year ago

Sorry I didn't see this sooner. Yes, there has been a noticeable improvement in the amount of spam coming from kbin. Whatever you're doing seems to be working! Thank you.