There'sNoTime on most Wikis
Oct 24 2018
Oct 22 2018
@Legoktm on reflection, I'm agreed entirely i.r.t "I don't think adding all oversighters and all checkusers to individual security tasks is a good idea" - there are a few other cases where general, non-security tasks are of immediate interest to the greater CU/OS community, but I'm not sure using an acl* project would be useful there.
Oct 21 2018
Oct 18 2018
Oct 17 2018
Oct 16 2018
No, I'm saying that the description of this task reports a problem, but the actual task is about a totally different one.
Oct 15 2018
Aug 5 2018
Jul 17 2018
That makes a lot more sense :-)
Jul 14 2018
Thank you all for looking into this - just noting that we rely heavily on GUC for steward activities, so this does currently impact our ability to deal with problems quickly
Jul 13 2018
This task doesn't only affect Russian Sites, nor is it a consequence of the site being Russian
Jun 30 2018
Just noting per T198057 (good merge!) - could we not filter against the action of emailing?
Jun 25 2018
May 26 2018
May 24 2018
May 11 2018
Apr 25 2018
Having had a quick look per this wikitech guide on adding an extension, it notes:
Mar 27 2018
Mar 26 2018
Mar 20 2018
It may be helpful to note a while back I found that this query returned the information I needed:
Mar 15 2018
@ayounsi I'm happy to pass on comments and suggestions to the OTRS ticket.
Mar 14 2018
Mar 13 2018
Changes made, retrospective task filed for logging my actions
Mar 5 2018
(fwiw, still not working for me)
Mar 4 2018
Following the advice of the above linked document, I have checked logstash
Feb 24 2018
I was only making a suggestion
Obviously we're not going to start doing web requests to the website to check each password... So we would need a copy of the data ourselves, and to stick it somewhere...
Feb 23 2018
Feb 22 2018
Asked to look at the trace by @MarcoAurelio
Feb 20 2018
Feb 2 2018
No rush by any definition of the word :-)
@RobH per T157483#3026051 "..NDA doesn't actually have an expiry date", I'm not entirely sure it has expired (I just think my access to the stats server has). Happy however to re-sign/be re-evaluated if needs be!
Jan 27 2018
Dec 27 2017
Dec 21 2017
Dec 20 2017
@Anomie agreed :-)
Dec 19 2017
Dec 5 2017
This only occurs on revisions prior to draftquality being enabled, so is expected behaviour - oops!
System --> Options --> Reverting [tab] --> Send welcome message...
Dec 1 2017
Nov 13 2017
Apologies for the bump, but where-abouts are we on this task? Just so us mere onlookers understand if things are moving forwards, or if there is something blocking 😺
Nov 2 2017
Good rename, though echo notifications for when a filter is automatically disabled would be a good idea..
Nov 1 2017
Oct 27 2017
Could you have an arb' verify this request? I'll ask the ones I know, but unless there is an official AC request this should be declined
Could you link to this "decision"? First I'm hearing of it..
Sep 29 2017
Sep 20 2017
Hi @Heathart, thanks for the task - this is definitely enough for someone to lift the IP cap. Unfortunately, we often need a bit more notice, so I can't guarantee this will be done in time for Thursday September 21st.
Sep 19 2017
I believe you're essentially looking for CheckUser or CheckUser-like functionality? I've had a scour of the beta cluster docs and can't see why it wasn't installed, but I imagine there was a privacy concern reason?
Sep 17 2017
The frequency of spikes seems to be increasing over the last 24 hours when compared to the last seven days
Sep 16 2017
@Framawiki that explains that then!
Does it not say in the disclaimer text?
It looks like cp1052 had a spike, but has since recovered
Sep 15 2017
@Sau226 it would be highly unlikely these groups would be granted to non-WMF accounts, even on the beta cluster, given their intended use.
@FULBERT Were you using The Wikipedia Adventure with visual editing? Currently only source editing is supported
It may be worth noting that the two spikes previous to cp1068's were also caused by cp1053
Sep 14 2017
Which rights are you referring to?
Thanks @Aklapper, looks like this will sort the issue for the user
Sep 12 2017
Sep 11 2017
Sep 10 2017
Overarching issue tracked in T174932, still minimal 503s in logstash and no further reports. Closing resolved (503s "resolved" by restart of varnish backends)
Appears to be resolved now