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?
rest assured: we’re aware of it and we’re working on it
Whatever you do, DO NOT upgrade to v0.18 - which drops Captcha support entirely -
https://github.com/LemmyNet/lemmy/issues/2922
Thanks, that’s a relief.
Is that why the comments number on the main page doesn’t reflect the actual number in the post itself (much fewer) ?
probably not. that’s a different bug, likely related to duplicate comments
Wow fastest reply, thanks!
this is mostly because i’m currently i’m on “clearing our application backlog” duty, and that means in my other tab i get notifications from people replying to my posts (as a pop-up) lol
Yeah the popup works flawlessly! I think it’s the only site in the world where I accepted notifications :-)
Good luck with the work!
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.