Re: [Wikimedia-l] CAPTCHA issues discouraging new editors

2015-06-19 Thread Glaisher
On 06/19/2015 05:54 PM, WereSpielChequers wrote: Earlier this year as a result of the glam organisers event in Paris I made a proposal at bugzilla for an event organisers useright. This would have allowed us to circumvent this problem at those editathons that are targeted at newbies, and it

Re: [Wikimedia-l] Farewell

2015-06-19 Thread Richard Farmbrough
We shall miss you. On 19 June 2015 at 09:30, Andrea Zanni zanni.andre...@gmail.com wrote: Goodbye Fabrice, and thank you for all your enthusiasm. It was very appreciated :-) Good luck! Aubrey On Fri, Jun 19, 2015 at 8:34 AM, Michael Jahn michael.j...@wikimedia.de wrote: May your next

Re: [Wikimedia-l] CAPTCHA issues discouraging new editors

2015-06-19 Thread Dennis During
Partially OT: re Sadly it got marked as resolved because there was something that looked similar to developers, though not of course to potential users. I've had a similar experience at Phabricator with respect to dump problems. Phabricator as it is used is really for WMF pros only, even though

Re: [Wikimedia-l] CAPTCHA issues discouraging new editors

2015-06-19 Thread John Mark Vandenberg
On Fri, Jun 19, 2015 at 12:22 AM, Andy Mabbett a...@pigsonthewing.org.uk wrote: [I'm posting this here because although the experiences described relate to en.WP, I'm sure it applies to other projects as well] I have trained over 100 people to edit Wikipedia this year; in around a dozen

[Wikimedia-l] What is the wikipedia http API address now?

2015-06-19 Thread Yuri
Now all previously http URLs redirect to https. https://www.mediawiki.org/wiki/API:Main_page also still mentions the old http address that now redirects. What is the new purely http API address? I need to know the hit of https on various processes. Yuri

[Wikimedia-l] [Wikimedia Announcements] The Signpost -- Volume 11, Issue 24 -- 17 June 2015

2015-06-19 Thread Wikipedia Signpost
Arbitration report: An election has consequences http://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2015-06-17/Arbitration_report Discussion report: A quick way of becoming an admin http://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2015-06-17/Discussion_report Featured content:

Re: [Wikimedia-l] Farewell

2015-06-19 Thread Michael Jahn
May your next steps be joyful, thrilling and challenging. All the best to you, Fabrice! Michael 2015-06-18 18:25 GMT+02:00 Fabrice Florin fflo...@wikimedia.org: Hello everyone, After three great years working at the foundation, the time has come to say goodbye. I will be leaving WMF at the

Re: [Wikimedia-l] CAPTCHA issues discouraging new editors

2015-06-19 Thread Andy Mabbett
On 19 June 2015 at 13:54, WereSpielChequers werespielchequ...@gmail.com wrote: Earlier this year as a result of the glam organisers event in Paris I made a proposal at bugzilla for an event organisers useright. This would have allowed us to circumvent this problem at those editathons that

Re: [Wikimedia-l] CAPTCHA issues discouraging new editors

2015-06-19 Thread WereSpielChequers
I'm tempted to point out that this mainly affects new editors who cite their edits, other new editors will get bitten in other ways. But the internet is not the best venue for irony. More practically, if you have a tame admin on tap then you can reduce this and other problems at editathons by

Re: [Wikimedia-l] Farewell

2015-06-19 Thread Andrea Zanni
Goodbye Fabrice, and thank you for all your enthusiasm. It was very appreciated :-) Good luck! Aubrey On Fri, Jun 19, 2015 at 8:34 AM, Michael Jahn michael.j...@wikimedia.de wrote: May your next steps be joyful, thrilling and challenging. All the best to you, Fabrice! Michael 2015-06-18

Re: [Wikimedia-l] CAPTCHA issues discouraging new editors

2015-06-19 Thread Hong, Yongmin
ThrottleOverride extension is not deployed on WMF cluster[1] so your best bet is to create a new bug which is already deployed on WMF cluster. [1] this means even if this is fixed, you will not see the fixed code on wikimedia wikis. -- Revi https://www.revi.pe.kr -- Sent from Android -- 2015. 6.

Re: [Wikimedia-l] CAPTCHA issues discouraging new editors

2015-06-19 Thread Eduardo Testart
Hi all, I know this might be a bit off topic but I'll risk it anyways. One told me a couple weeks ago that CAPTCHA (at least one CAPTCHA) was created or used to transcribe documents bit by bit, each word you enter corresponds to a two word link, that when it reaches so many equal responses is

Re: [Wikimedia-l] CAPTCHA issues discouraging new editors

2015-06-19 Thread Andy Mabbett
On 19 June 2015 at 14:58, Andy Mabbett a...@pigsonthewing.org.uk wrote: On 19 June 2015 at 13:54, WereSpielChequers werespielchequ...@gmail.com wrote: Earlier this year as a result of the glam organisers event in Paris I made a proposal at bugzilla for an event organisers useright. This

Re: [Wikimedia-l] CAPTCHA issues discouraging new editors

2015-06-19 Thread Ricordisamoa
Yes, I think it's a great idea! T34695 https://phabricator.wikimedia.org/T34695 has been assigned to me for a while, but I'd use some help. Il 19/06/2015 16:17, Eduardo Testart ha scritto: Hi all, I know this might be a bit off topic but I'll risk it anyways. One told me a couple weeks ago

Re: [Wikimedia-l] CAPTCHA issues discouraging new editors

2015-06-19 Thread Benjamin Lees
Events sometimes get whitelisted for account creation purposes: https://noc.wikimedia.org/conf/throttle.php.txt The exceptions there there could be made to set $wgCaptchaWhitelistIP too. On Fri, Jun 19, 2015 at 8:54 AM, WereSpielChequers werespielchequ...@gmail.com wrote: alternatively perhaps

Re: [Wikimedia-l] CAPTCHA issues discouraging new editors

2015-06-19 Thread Andrew Gray
It's true that events *can* get whitelisted, but this is a very complex method. It relies on the organiser knowing the IP ranges in advance, and knowing who to contact at WMF - and on WMF having the time to deal with it. It would rapidly break down if we needed to use this method for every small

Re: [Wikimedia-l] CAPTCHA issues discouraging new editors

2015-06-19 Thread Sydney Poore
Hi, I agree with Andrew that is not practical to whitelist ip addresses as a primary method of overcoming account creation/ CAPTCHA issues at events. Organizers often will not know the ip range in advance because of changes in the address, or last minute changes in the location of the event. The