[00:08:17] Re-sending my reply to @Inkster now that it's back up. [00:08:22] @Inkster IP addresses can't be globally locked; they can be globally blocked, but if the disruption is occurring on only one wiki, you can just block that IP address locally using [[Special:Block]] on your wiki. If you need some assistance with rangeblocking, then yeah, a GS or steward could definitely locally rangeblock that IP for you. Also, you could protect that page at "allow only logged in users," too, at least temporarily (for a week [00:08:22] 15:50 or two). Hope that helps. [00:08:23] https://meta.miraheze.org/wiki/Special:Block [00:08:24] [ Permission error - Miraheze Meta ] - meta.miraheze.org [00:09:26] @Void I'm surprised you didn't use this emoji with bonks it 🔧 😛 [00:22:20] I don't own that wiki. [00:22:36] But can't you globally block that user? [00:31:43] @Inkster, well, if the disruption is occurring only on one wiki, a global lock may not/should not be required, as the IP can just be locally blocked. [00:32:12] Are you an administrator on that wiki? Any administrator can locally block. [00:33:36] No. [00:33:39] And the owner and only admin left. [00:39:11] @Inkster, okay, fair enough, then yeah, maybe you can have a Global Sysop or steward locally block that IP address, as you're a member of the local community making a request and it is disruptive editing. [00:39:37] @CVT see @Inkster's request above to locally block or rangeblock, as applicable, the above IP address. [13:37:20] $log hid a revision on horriblevyonderswiki [13:37:30] Saved item "hid a revision on horriblevyonderswiki" [13:38:55] $log deleted comments on same wiki [13:38:59] Saved item "deleted comments on same wiki" [23:50:00] @CVT Low-ish priority RudolphRichart is a spam-only account that can be locked for spamming the AbuseLog. [23:50:03] .mhca RudolphRichart [23:50:03] https://meta.miraheze.org/wiki/Special:CentralAuth/RudolphRichart