[03:50:27] [[Tech]]; Stacker22; /* New Contributor */; https://meta.wikimedia.org/w/index.php?diff=15821471&oldid=15820528&rcid=8110971 [12:50:07] !bug T2986 [12:50:23] Any update on https://phabricator.wikimedia.org/T2986 ? [13:19:20] No. [13:33:25] the updates would be in the bug wouldn't they? [15:50:32] I want to set up edit notices on my wiki like they are set up on enwp. What do I need to do so that if a user creates User_talk:Name/editnotice it will show automatically without having to create MediaWiki:Editnotice-3-Name for them? [16:30:30] Okay, so I have got [[MediaWiki:Titleblacklist‎]], [[MediaWiki:Titleblacklist-custom-editnotice‎]], [[MediaWiki:Editnotice-2‎]], and [[MediaWiki:Editnotice-3]] so far. What else do I need to protect the editnotices so only the user and admins can edit them? [16:34:00] Hey MatmaRex [16:35:18] hi [16:37:56] Would you happen to know what I need to do to protect User*/Editnotice pages on my wiki so only administrators and the user who's page it is can edit it? [16:40:30] I don't think that's what enwiki does [16:40:34] ShoeMaker: i don't think it can be done, unless there's an extension that implements it [16:41:02] ShoeMaker: you could possibly write an AbuseFilter rule that would check this. [16:41:22] :/ Then I'd have to hack it and make people create their editnotices on User*/Editnotice.css or something. [16:44:02] hmm [16:44:07] yeah that might work actually [16:45:33] I think I'll leave them open so anyone can edit them, and if an issue occurs with vandalism - I'll adapt and move them all. Thanks. [16:47:01] if an issue occurs with vandalism you can just AbuseFilter it [16:47:16] if you're not enwiki then I wouldn't expect enwiki-scale vandalism [17:26:34] Krenair: My wiki doesn't have AbuseFilter. We have consensus against it. [17:26:44] Meh. /shrug [19:58:23] MatmaRex: do you have an idea of how to ping/cc to help with https://phabricator.wikimedia.org/T142137 [19:58:30] MatmaRex: s/how/who/ [19:59:37] greg-g: it looks hopeless to me until one of the affected users determines which gadget/script is responsible. since by now it quite clearly looks like a gadget causing problems [19:59:52] MatmaRex: /me nods [19:59:56] thanks [20:00:00] andre__: ^ [20:00:09] hmm [20:00:17] ... or not? [20:00:18] :) [20:00:30] greg-g: it looks like they blame wikEd now, so that narrows the options down a lot [20:04:21] greg-g: although, i can't reproduce it myself (with wikEd enabled in preferences, but disabled on the page). i'd try asking wikEd's maintainer, i think that's Cacycle on en.wp [20:08:18] Bit worried it may be related to my edit very shortly before that report was created [20:09:25] though I couldn't reproduce the issue [20:15:31] it was https://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js&diff=prev&oldid=733009953 [20:24:14] Krenair: you're saying that was the cause? mind mentioning as such on the task? :) [20:24:26] not necessarily [20:24:37] I mean, I'm saying it's not necessarily the cause but might be [20:31:01] * greg-g nods [20:38:03] anomie: You around? Looks like one of your changes killed all pywikibot bots [20:39:33] Yeah, let's wait until someone can isolate the gadget and others can reproduce... [20:46:40] multichill: How long ago was the change made because some of the pywikibots still seem to be working? [20:46:59] It's a logon change so slowly all bots will die [20:47:36] It's like not having a DHCP server anymore in your network. Every machine which has an IP will work for a while and slowly everything starts falling apart...