this post was submitted on 20 Jun 2023
30 points (100.0% liked)

Beehaw Support

2796 readers
1 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
Zmodem@beehaw.org
Gaywallet@beehaw.org
alyaza@beehaw.org
Lionir@beehaw.org
Penguincoder@beehaw.org
remington@beehaw.org
30
Heads Up! Bots are coming. (fedidb.org)
submitted 1 year ago* (last edited 1 year ago) by cura@beehaw.org to c/support@beehaw.org
22 comments fedilink hide all child comments
 

Maybe you guys already know about the bot signup over lemmy.world. Now they are all over the lemmyverse. The top 20 fastest growing instances in the threadiverse are probably suffering from it. The top one, lemmy.podycust.co.uk, has 10k users with 7 total posts. The total user count of threadiverse is now 544k, compared to 270k on June 19. We may be facing 200k+ bots at this point. Also these instances are in the federation. If any admin of these instance abandons ship, this creates huge liabilities to the threadiverse.

Lemmyverse needs to figure out how to deal with this. But before that happens, do you guys think Beehaw should preemptively defederate these affected instances? Or could there be a better solution?

you are viewing a single comment's thread
view the rest of the comments
[–] th3raid0r@tucson.social 3 points 1 year ago* (last edited 1 year ago)

Also, please please please please PLEASE have the Beehaw admins comment on that issue. Right now everyone seems to agree that spam is bad but no one is expressing that this is urgent back to the devs.

If 1 out of every 10 admins did that, I'm fairly certain the Devs would hold off and fix that before releasing..

Right now I'm incredibly frustrated because the only place this is being communicated is on the fediverse - even amongst admins.

This is open source, we as administrators of project instances have a deep responsibility to communicate back with the devs, and I fear that's not happening.