[13:00:13] [1/4] https://discord.com/channels/407504499280707585/1072042278580928532/1414541234625708042 [13:00:14] [2/4] new one [13:00:14] [3/4] this time insults to the mother of moderator [13:00:14] [4/4] is there any way of blocking more effective than a range ban? [13:59:02] Even if you geo-block them (Which would limit all users of that country) they would use VPNs to circumvent that. (Not sure if that's possible per wiki :ThinkerMH: [14:00:59] You could restrict editors to registered users with an email ad´dresss. [14:01:30] Use a moderation extension [15:39:30] Moderation extensions don't prevent account creation, which is the issue here [15:40:17] True, but their comments/posts will not be shown public, was my point [15:42:32] The main issue is offensive usernames, which appears to be the troll's modus operandi - enabling a moderation extension will do nothing about that [15:45:19] Another option would be to disable account creation on their own wiki, and defer that to Login wiki, which is what I have done for my wiki. [15:45:29] How can i create a wiki [15:45:51] Please ask in #Support [15:45:56] Ok [15:45:58] or in #general [16:42:58] [1/4] yes it is [16:42:59] [2/4] a troll can even create multiple accounts at once [16:42:59] [3/4] they don't make any edits, they get banned first [16:42:59] [4/4] but the nicknames contain insults and death wishes [16:46:06] That wouldn't solve the issue as you admit - the troll would just create an account on another wiki [16:55:12] Yeah, i was thinking if there was any way to accomplish this via abuse filters, e.g. prevent local attach unless the admin forces a local creation [16:55:40] It's ugly and breaks the openness of the wiki, but I can't think of any more effective workaround. [16:55:50] The names can't really be regex-caught [17:04:32] [1/2] True, but at least it would make it harder for them, and easier for us to detect. [17:04:33] [2/2] The account would be created on meta and login. I often check accountnames for suitabillity and to see if the LTA is coming in again.