[06:38:37] @CVT [06:38:47] i am trying to handle this myself currently but would appreciate some helf [06:38:55] this is some pretty big vandalism i'm handling [06:39:02] https://cdn.discordapp.com/attachments/443926951292567562/1469220827970142382/Screenshot_2026-02-06_at_6.35.08_a.m..png?ex=6986de06&is=69858c86&hm=5868c2dcf1ffbf7467f05dff5ecc02137f063a06ec4c5b2fbee210ca6046d2f4& [06:41:14] start blockin accounts dude, try to minimise the damage until cvt gets to it [06:41:51] CVT here. I can help you with that. Could you share the wiki URL? [06:42:20] https://norm.miraheze.org/wiki/Special:Contributions/NonaNerd [06:49:43] Locked the account and blocked the IP they were using [06:49:47] Let me know if you need any further assistance [06:55:44] fyi you might want to enable the "protect site" extension if this happens again [07:01:12] probably will [07:01:24] thx [07:21:47] I wonder is there any way to make a wiki vandal proof without getting rid of people's ability to edit [07:23:58] moderation is technically one way [07:24:53] i suppose you can protect pages to make it more difficult to vandalise specific pages, but i presume the vandal target is a wiki and not a topic [11:57:55] [1/3] advertising only account [11:57:55] [2/3] https://meta.miraheze.org/wiki/Special:CentralAuth/Transhipviewer [11:57:56] [3/3] https://cdn.discordapp.com/attachments/443926951292567562/1469301076053332124/image.png?ex=698728c2&is=6985d742&hm=3e1b4d60e61884b90e7861def8c3fd6afb17498093b0417dcd01e6138fee46e0& [13:24:19] afaik doesn't work [13:25:01] but you can just disable editing permissions for users on MH so it's not that much of an issue [19:18:49] Really? [19:19:34] https://exttest.mirabeta.org/wiki/ProtectSite [19:20:47] [1/2] actually looks like it didn't work [on 1.44](https://issue-tracker.miraheze.org/T13645) either [19:20:47] [2/2] https://cdn.discordapp.com/attachments/443926951292567562/1469412525752717427/image.png?ex=6987908e&is=69863f0e&hm=fcfbcc64bc78f9341d1cc0a70d643cf08e363d33674b6c4804451093ac6ef9e0& [19:20:53] Hm [19:21:21] but like ManageWiki basically obsoletes ProtectSite anyway [23:21:54] How so? [23:22:13] But also I also had the issue that Protect site doesn't work when using manage wiki, works without it though so I suspect there's some conflict [23:22:57] ProtectSite's entire function is to restrict certain features, which can also be done via ManageWiki [23:24:25] Yeah, but it's a lot more tedious (you also can't set expiry times on that, you have to go back and add the rights back) [23:26:20] If it's not a huge workload, I'd rather see it fixed. [23:26:23] But yeah appears to just be doing the same thing as manage wiki looking at the code. I assume it doesn't work as it modifies wgGroupPermissions [23:26:44] ah [23:26:55] why would that change over recent updates though [23:26:58] The more elegant solution rather than using a callback would probably be to use the relevant hook which checks whether a user can edit [23:27:10] It never worked for me with ManageWiki so idk [23:27:43] There's no way it's been on Miraheze for years and no one ever noticed the extension doesn't work [23:27:46] Right? [23:30:38] https://cdn.discordapp.com/attachments/443926951292567562/1469475406708211846/image0.gif?ex=6987cb1e&is=6986799e&hm=c7bd5212ddf58fc8561623501685faf5082e81ebc3205df5206ccc67789435e6& [23:31:23] It logs to special:log so could check ig