The thing with federation is if that is the kind of thing you are dealing with then it is up to the instance that had lax signup to clean up their own mess.
If this did happen and the admins of the offending instance said they were dealing with it then I would be happy to give them some slack to do so, and would probably offer any assistance I could.
That said, it is still very much their responsibility to handle it, or they risk their instance being blacklisted.
Lemmy is compatible with bots which can cause some serious headaches, however there are tools that can combat these.
Every instance of Lemmy has a reputation that is associated with it. If it becomes clear that a particular instance is being used as a bot hub and the moderators are unresponsive then other instances will quickly start to black list it for being too spammy. More so if word starts to get out about it. Point is that the admins of an instance will make a good job of ensuring their users aren’t bots (or at least being misused as a bot) or face their whole instance being blocked across the board.
Even if the bots have their own instance then other instances will resort to enforcing whitelists for connections. Over time we may also see the development of additional mod tools too.
Considering I am looking at this – while having disabled NSFW for myself and my instance – this is a problem?
This sounds oddly familiar 🤔
This is not a bad idea. This is how the Fediverse is supposed to work.
@snowe I think Lemmy is going to have a hard time handling any meaningful traffic if lemmy.ml is struggling with ~2k active users.
Some work probably needs to be done, however the more early adopters there are – particularly in these types of communities – the more likely the work will actually get done.
Once I started using CLion I couldn't go back
Microsoft aren’t exactly big on implementing “the latest” stuff. Not at a keyboard currently but I’d be willing to bet GH doesn’t support TLS1.3 either.