thatcasualgamingguy

I think it’s actually pretty clean. Thanks to the references on the person table all related entries in the database like posts, comments, etc. also get deleted if there are any. It’s better than banning all those fake users and thereby spamming the modlog of all instances that federate with you 😅

Just did that for my instance. Luckily it’s fairly easy. Since there were no human registrations after those bots I just looked up the lowest bot id in the local_user table which was 9 and then used delete from person where id in (select person_id from local_user where id >= 9);. Thanks to the references and triggers on the table, the rest of the database was also cleaned up by that, including the local_user table.

That would probably only slow them down. And since their main goal is to create a ton of working accounts, speed is probably not that important to them. On my own instance the bot-registrations stopped immediately after I enabled the required application.

While looking for a way to enable captchas I found out that they will remove that feature from lemmy: https://github.com/LemmyNet/lemmy/issues/2922

This seems to be the issue for the feature: https://github.com/dessalines/jerboa/issues/522

Same here. I always have to search for and subscribe to new communities through a browser. And after that, I have to kill the app and open it again for the new community to show up in my list. There might be a different way to reload the community list, though. Just haven’t found it, yet.

For me that only works in a browser, not in the app.

I run a Jellyfin server, complete with Jellyseerr, Sonarr, Radarr, the works.

They’re already using Jellyseer.

Wouldn’t it still be a bit less taxing even with only one user? If I’m not mistaken then your instance only initially requests a community/post/comment from another instance when you specifically search for it. After that your server gets updates through activities pushed by the other instance. So if you refresh a post multiple times those requests only go to your instance. It somewhat acts like a cache, while the other instance can push activities at it’s own pace instead of being hammered with requests. Of course multiple users per instance would still be better.

A game I equally loved and hated for having multiple ways the story could go was KGB. Sometimes you would lose because of a decision you made hours ago. :D