Yep - this was done at 18:49GMT today from my registered email.

Added verification on wmflabs to prove control of private key - tools-sgebastion-07.tools.eqiad.wmflabs:/home/mdann52/2fa-reset-request.txt

Is there a discussion on a community you can link us to showing this is a desired feature?

Any progress on this? Just had another report on this issue (OTRS ticket 2017030910017821). Screenshot attached.

Looks ok viewing this page (the issue above looks sorted). @Luke081515, has this been resolved now?

Seemingly resolved with T94774

@Dereckson have you made any progress on this?

Note the OTRS ticket was sent in " Created: 16/01/2016 15:27 ", so this may have already been caught with the other patch

Pinging @Spinster about the above

Has a new logo been created yet?

Code removed, this appears to have resolved the underlying issue. If there is anything else, please open a new bug to request this is reinstated.

Has this now all been done and resolved?

Done with css

As this hasn't been done yet. Just wanted to check - you do mean 2016, not 2015? :P

Closing as stalled as there has been no further community discussion moving towards implementation.

And I'll nab this off @samtar if they don't grab it by the time I'm home too :P

Can you please link to a community discussion/announcement on this issue please?

https://gerrit.wikimedia.org/r/#/c/262894/

In T122995#1918914, @JEumerus wrote:

Is there a consensus to add the domain to $wgCopyUploadsDomains?

So what happens is that the expected behaviour should be it follows X redirects (so if x=2, it will go a>b>c), however currently it only follows one (and shows the redirect page to c). I'd expect it to follow the number of redirects specified.

Tested on mw 1.26.2, and this does not work with the current config - will set a blocking task.

Tested on mw 1.26.2, and this does not work with the current config - will set a blocking task.

Merged together as these seek the same thing - the merged one seeks to achieve this. I'm doing some testing to see if this works as intended on a private wiki before pushing the patch

Oh, and just for reference, I'm another volunteer who goes through and answers these, as and when I have the time

I believe it has been mentioned a lot of these are crash reports, and OTRS is not the primary system for these. Any chance these could be cut off if not used?

We are already discuss on our preject:user right page in a guwiki. Admin can add and remove user right.

Is this still an issue, or has it been resolved?

On it!

Can already be done manually should it need to be (add ~~~ to the message, then append ~~~~~ while sending it out). I'm guessing you're proposing we change the name that is sent out on emails and recorded in the page history, which opens up a whole new kettle of worms in terms of implimentation, and also makes contribution flooding an issue (because the sending user will usually not have a bot flag, so this clutters up the watchlist as well).

I don't think this is needed - there are many reasons why senders name is not always needed (for example, Wikiproject newsletters or another group). I think the existing implementation (where the bot timestamp is posted, which is the posing user, and the sending user is included in a timestamp) is better - if users want to include their signature in the message, that's also easy enough to do with the existing implementation (sign the message with ~~~, then append ~~~~~ to the message as you send it).

As I'm doing a load of these at the moment, I'll take this one too!

https://gerrit.wikimedia.org/r/#/c/255361/

so basically, we can just go convert all of these, if I'm understanding correctly?

Appears to have been done (default is 5000, can't see any other limits)

Per response above

1. you can make it default to other languages if you want - it should reflect ULS settings, and there's always &uselang= if needed. Secondly, thus site is used for en arbcom elections too, which are also meant for only those editing enwiki. The extension is not actually installed on your site AFAIK, so this is a much easier way of achieving this. It's down to ops at the end of the day, just my 2 cents here.

Shouldn't this be done on https://vote.wikimedia.org/wiki/Main_Page anyway?

Closing - as far as this request is at the minute, it is non-actionable and effectively declined by legal, so no action can be taken at this point. As and when everything is resolved, a new bug should be opened - the main reason for the closure is the multiple proposals sneaking in above.