Sat, Jun 2
Wed, May 30
May 4 2018
The reduction there is because of other mitigation techniques (not a bad thing)
Mar 22 2018
FTR (said in a call with the Stewards Tuesday but for the record) I'm going to be talking with Legal about this and will loop back once we're set there and/or have other questions.
Mar 21 2018
Assigning High so that it's first looked at if we have time for it since it makes the CP tool unusable (they are basically always deleted/suppressed already).
Feb 27 2018
Feb 22 2018
Feb 21 2018
Feb 20 2018
This is approved from the Trust & Safety side now (and hence the WMF). @MarcoAurelio is doing the global changes now and submitting the local patch which I'll shepherd though SWAT this afternoon.
Feb 16 2018
We're pretty much good, done a bit of testing and will do a bit more but should be ready to roll out a patch to give to CUs on Tuesday (US Holiday on Monday and I'd rather not launch with folks either on their weekend or going to it in case there are issues/questions).
Grabbed this because in addition to walking through it with Aeryn tomorrow going to do some production testing from the SuSa side. Once we're all set I'll submit the patch to turn on for CUs etc. (assuming the old data purge stuff is set up? I believe that is now but will check on).
Feb 7 2018
Dec 20 2017
Dec 15 2017
The patch looks good from SuSa's side. We'll also want to add it to a couple global groups but I've verified it's available and we do that on-wiki so I'll send a note to the Stewards to do that side.
Dec 9 2017
done :) thanks RadiX
Dec 8 2017
Nov 19 2017
Thanks Marco, done. Verified with CUWiki
Sep 6 2017
FTR this can get held off for now (or even just closed as rejected). We're transitioning away from Mailman for this list. Handling the archives that currently remain will be decided after.
Sep 5 2017
Aug 30 2017
Aug 24 2017
Thanks David, still got this though the file upload is definitely working now. For the error I'm filling in the the form for DMCA completely and so far have tried either not uploading a file, not sending to Lumen and Not posting to WMF Wiki and still getting the error (though the exact error adjusts since some things are no longer saved in the query). For simplicity writing down exactly what I'm using in case there is any weirdness that's causing it:
Jul 31 2017
Jul 24 2017
Jul 23 2017
Pulling this in to the security zone because the attack vector it exposes.
Jul 17 2017
Still need on my end preferably without expiration. Biggest use is hive/beeline access for relatively routine subpoena/legal data gathering (one might need to happen today for example depending on what we decide at a meeting) and occasionally other T&S investigations when needed and approved (rare given the level of private data but important when needed).
Jul 13 2017
Jul 3 2017
This is going to be slightly stalled for a short time, the salesforce instance is still having it's final setup because we've been transferring over all of our data from Sugar. It should be done and available to be dealt with later this week. I'll see if I can scrounge up documentation to help in the meanwhile too :)
Jun 29 2017
@kaldari do you know if this is possible atm?
Jun 22 2017
Jun 10 2017
Jun 5 2017
Jun 1 2017
May 30 2017
May 25 2017
May 24 2017
May 13 2017
These both seem to be working now, not sure exactly what happened but I'm at least a bit nervous that it was me a couple hours ago :( ( in an attempt to fix some issues with a gadget I tried to set a dependency to solve a race condition https://meta.wikimedia.org/w/index.php?title=MediaWiki:Gadgets-definition&diff=16752348&oldid=16751393 ). Still don't think it "should" have caused everything else to fail but wouldn't be the most surprising thing.
May 5 2017
resolving, was completed earlier
Apr 27 2017
Apr 25 2017
Apr 20 2017
Apr 18 2017
For the record I'd support Matanya in this as someone who can be really useful to have insight and input into Security/private cases.
Apr 5 2017
Mar 23 2017
Sorry for the delay, I'm the one who understands the setup the most but the massive amounts of Phab emails I get mean that it's fairly easy for me to miss any pings unless I get a poke elsewhere. I've verified the request and am making the change now.
Feb 17 2017
Feb 8 2017
Feb 3 2017
Jan 29 2017
I'm going to reopen this rather then creating a new one (or not) in order to allow people to wave their hands and call me crazy as needed given that it was previously declined. I'd like to (and currently plan to barring good reason not to) create this acl in order to allow it to be added as managers on the Confidentiality Agreements (the only way they're able to see signatures) so that they're able to quickly and efficiently process requests for access on meta without waiting on staff.
Jan 21 2017
Created at media-reports-tool
Jan 20 2017
Yeah, I think that in this case media-reports-tool may end up being best, we'd try to avoid using -tool as a common word usually but I worry that media reports has too many other possible meanings (such as the report the tool is designed to help create) and would be confusing otherwise.
Jan 5 2017
New password emailed to both registered list admins :)
Dec 21 2016
Dec 20 2016
Dec 19 2016
Approval from the SuSa/Legal side is already done, the NDA discussed is the OTRS version of the Confidentiality agreement for nonpublic information and the OTRS administrators having access tot he signatures was always planned. I can set up the ACL myself (to work similarly to the one we use for SuSa staff and the main agreement) if easiest.
Dec 14 2016
Also: How hard is it to deactivate a url if worst comes to worst? Is it just a db row being dropped (or changed) or is it something more massively pita?
yeah, I think a rate limit could prevent the biggest amount of this. That makes it a lot harder to try and force a problematic, specific, url to use. 10 per 2 is probably ok for anon/newbie (building it in allows us to adjust if we see people trying to abuse anyway). Honestly for users without rate limit exemption (or higher limits in general) I would think it doesn't need to be set crazy high either (50-100?) but could certainly be higher then 10.
Dec 8 2016
Dec 2 2016
New PW sent to all current admins.
Nov 30 2016
If IPs are blocked then blocking password resets from that IP makes sense given the history of abuse there. That said:
Nov 22 2016
Have you lost the current one and need to change it or have all admins lost the old one now?
Oct 18 2016
Adding ops for now because it seems like it could be something stuck on the server side but may not be.
Oct 17 2016
Yeah, thanks for switching it back, it would have been done before the next election just wasn't yet because there hadn't been any reason to (was waiting until we were setting up the next cycle).
Aug 23 2016
Well the first thing you could do would be to crowd source it from Wikipedia ;) one of my favorite little tricks is that you can already search for many emoji since redirects are set up for many of them (and you should be able to relatively trivially do a search on the emoji and see if a direct result comes up)
Aug 2 2016
Ok.... we can try to experiment a bit more and you may want to ask around on IRC. Im happy to grant whatever rights are required for you to do this but this may not be a rights issue, you have every right you should need and so we probably need to check abuse filters or oddities in global user pages, flow etc. I'm not sure what the issue is.
Can you try now? We've added the move user page and move sub page right
It looks like there are a bunch of different move rights now include "move root user pages" I assume that's what'a stopping you... I don't remember those even existing last time I looked but I'm sure they've existed longer then I think. I'll get the stewards to add to the user rights.
This actually looks like this was done in March but we never updated the task? Everyone with global flow create has move :) Let me know if you need anything else however!
Jul 11 2016
another new password sent to emails of admins... I've tested and works not sure what happened with the old one
Jul 7 2016
@Philippe is also having this issue (under User:Philippe) tried to do the work around listed (go to https://test.wikipedia.org/w/index.php?title=Special%3ACentralAuth&target=Philippe and log in to scnwiki which is what it lists) but he just got another exception when doing that.
updated the table for both myself and Joe (who at the moment is there generally to shadow and back me up). I obviously don't really care what specific rights group we have but I'm not sure any other groups currently exist for our use case other then restricted (unless we were upgraded to deployer obviously which I leave to others, I generally work under 'least access' type rules but there are obviously different things to balance). The biggest things we get out of restricted and need to keep: