On 22/01/13 01:44, Bawolff Bawolff wrote:
Given that there are algorithms that can solve our captcha presumably they
are mostly preventing the lazy and those that don't have enough knowledge
to use those algorithims. I would guess that text on an image without any
blurring or manipulation would
Nikola Smolenski wrote:
On 22/01/13 01:44, Bawolff Bawolff wrote:
Given that there are algorithms that can solve our captcha presumably
they are mostly preventing the lazy and those that don't have enough
knowledge to use those algorithims. I would guess that text on an image
without any blurring
On Mon, 21 Jan 2013 21:50:32 -0800, Alex Brollo alex.bro...@gmail.com
wrote:
I tried to build a template which wraps template parameters into data-
attributes. First results have been incouraging, then I find something
logical but unexpected, crushing the whole idea.
I wrote into the code
Hi, following the process for requesting the creation of a MediaWiki
group, here is a proposal for MediaWiki Group Surakarta
http://www.mediawiki.org/wiki/Groups/Proposals/Solo Your endorsements,
improvements and feedback are welcome at the wiki
page. Thank you! PS: see also
On Tue, 2013-01-22 at 10:13 +0100, Nikola Smolenski wrote:
A simple thing that could be done is to introduce localized captchas on
non-Latin wikis (just remember that not everyone has the appropriate
keyboard).
For the records, this is covered in
What do you mean by
any wikicode (template call, parameter, link) present into
the value of infobox parameter breaks the stuff, since it is parsed and
expanded by parser with unpredictable results.
If your {{{author}}} doesn't have anything and it's aсceptable, then make
it {{{author|}}},
Hi all,
As you might have heard Wikimedia Nederland, Wikimedia UK, Wikimedia
France and Europeana are collaborating to provide a set of tools to get
material from GLAM institutions onto Wikimedia Commons. The Wiki GLAM
Toolset has to be created in a way that re-use can easily be tracked,
and
On 01/22/2013 08:45 AM, Geer Oskam wrote:
Hi all,
As you might have heard Wikimedia Nederland, Wikimedia UK, Wikimedia
France and Europeana are collaborating to provide a set of tools to get
material from GLAM institutions onto Wikimedia Commons. The Wiki GLAM
Toolset has to be
Hello,
I have finally integrated PHP_CodeSniffer to report PHP style errors in
MediaWiki core. PHP_CodeSniffer tokenises PHP and detects violations
based on a set of coding standards.
You can get it running on your local installation by following the very
lame install guide I wrote at mw.org :
On Tue, Jan 22, 2013 at 3:53 AM, Daniel Friesen
dan...@nadir-seen-fire.com wrote:
On Mon, 21 Jan 2013 21:50:32 -0800, Alex Brollo alex.bro...@gmail.com
wrote:
I tried to build a template which wraps template parameters into data-
attributes. First results have been incouraging, then I find
Per the previous comments in this post, anything over 1% precision
should be regarded as failure, and our Fancy Captcha was at 25% a
year
ago. So yeah, approximately all, and our captcha is well known to
actually suck.
Maybe you'll just use recaptcha instead of fancycaptcha?
On 22 January 2013 17:37, vita...@yourcmc.ru wrote:
Per the previous comments in this post, anything over 1% precision
should be regarded as failure, and our Fancy Captcha was at 25% a year
ago. So yeah, approximately all, and our captcha is well known to
actually suck.
Maybe you'll just
On Tue, Jan 22, 2013 at 10:37 AM, vita...@yourcmc.ru wrote:
Maybe you'll just use recaptcha instead of fancycaptcha?
/me gets popcorn to watch recaptcha flame war
There has been discussion on this list in the past about the use of
recaptcha, but it has generally ended in a down-vote because
The problem is that reCaptcha (a) used as a service, would pass
private user data to a third party (b) is closed source, so we can' t
just put up our own instance. Has anyone reimplemented it or any of
it? There's piles of stuff on Wikisource we could feed it, for
example.
OK, then we can take
Even ignoring openness and privacy, exactly the same problems are present
with reCAPTCHA as with Fancy Captcha. It's often very hard or impossible
for humans to read, and is a big enough target to have been broken by
various people.
I don't know if it's constructive to brainstorm solutions to a
On 21/01/13 08:04, Chris Grant wrote:
Not sure about enwiki, but from my experience with hosting smaller wiki's
CAPTCHA's are pretty useless (reCAPTCHA, FancyCAPTCHA, some custom ones).
The spambots keep on flooding through.
I've found its much more effective to just use the AbuseFilter.
--
Luke Welling WMF писал 2013-01-22 21:59:
Even ignoring openness and privacy, exactly the same problems are
present
with reCAPTCHA as with Fancy Captcha. It's often very hard or
impossible
for humans to read, and is a big enough target to have been broken by
various people.
It's very good to
It's very good to discuss, but what are the other options to minimize
spam?
(maybe I know one: find XRumer authors and tear their arms off... :-))
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
Luke, sorry for reiterating, but «brainstorm solutions to a problem
before we measure the extent of the problem» is wrong: it's already been
measured by others, see the other posts...
Nemo
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
Our coding conventions for PHP are currently ambivalent on whether we
should write if ( or if(. It's probably time to pick one.
Discussion at
https://www.mediawiki.org/wiki/Manual_talk:Coding_conventions/PHP#Control_structures
___
Wikitech-l mailing
On 2013-01-22 3:01 PM, Brad Jorsch bjor...@wikimedia.org wrote:
Our coding conventions for PHP are currently ambivalent on whether we
should write if ( or if(. It's probably time to pick one.
Discussion at
https://www.mediawiki.org/wiki/Manual_talk:Coding_conventions/PHP#Control_structures
That was not the end of the problem I was referring to. We know our
specific captcha is broken at turning away machines. As far as I am aware
we do not know how many humans are being turned away by the difficulty of
it. It's a safe bet that it is non-zero given the manual account requests
we get,
I'd like to notify you that thanks to the generosity and cooperation if
the previous owner, wikimania.org and wikimania.com are now owned by
Wikimedia CH.
The domain is currently set up in the same way as it was before but we
have now the possibility tu use ssl.wikimania.org for the registrations
On Tue, Jan 22, 2013 at 8:18 PM, Luke Welling WMF lwell...@wikimedia.orgwrote:
That was not the end of the problem I was referring to. We know our
specific captcha is broken at turning away machines. As far as I am aware
we do not know how many humans are being turned away by the difficulty of
Yeah, this has gotten pretty frustrating, because sometimes even in the
same function different styles are used. We need to stick with one. I'd
recommend using the spacey version, because we use the non-spacey version
for function calls and definitions, so at least IMO it's a good way to
On Tue, Jan 22, 2013 at 11:28 AM, Manuel Schneider
manuel.schnei...@wikimedia.ch wrote:
I'd like to notify you that thanks to the generosity and cooperation if
the previous owner, wikimania.org and wikimania.com are now owned by
Wikimedia CH.
The domain is currently set up in the same way as
Am 22.01.2013 20:42, schrieb Leslie Carr:
On Tue, Jan 22, 2013 at 11:28 AM, Manuel Schneider
manuel.schnei...@wikimedia.ch wrote:
I'd like to notify you that thanks to the generosity and cooperation if
the previous owner, wikimania.org and wikimania.com are now owned by
Wikimedia CH.
The
On 2013-01-22 3:30 PM, aude aude.w...@gmail.com wrote:
On Tue, Jan 22, 2013 at 8:18 PM, Luke Welling WMF lwell...@wikimedia.org
wrote:
That was not the end of the problem I was referring to. We know our
specific captcha is broken at turning away machines. As far as I am
aware
we do not
I liked the post, but I'm not sure what exactly we should change in our
code reviews. Could you explain?
On 01/21/2013 01:40 PM, Ori Livneh wrote:
There's a useful blog post on code review at Mozilla by Mozilla developer David
Humphrey on his blog: http://vocamus.net/dave/?p=1569.
I like
On 22 January 2013 19:44, Manuel Schneider manuel.schnei...@wikimedia.chwrote:
Am 22.01.2013 20:42, schrieb Leslie Carr:
On Tue, Jan 22, 2013 at 11:28 AM, Manuel Schneider
manuel.schnei...@wikimedia.ch wrote:
I'd like to notify you that thanks to the generosity and cooperation if
the
On Jan 23, 2013 8:09 AM, Thehelpfulone thehelpfulonew...@gmail.com
wrote:
On 22 January 2013 19:44, Manuel Schneider manuel.schnei...@wikimedia.ch
wrote:
Am 22.01.2013 20:42, schrieb Leslie Carr:
On Tue, Jan 22, 2013 at 11:28 AM, Manuel Schneider
manuel.schnei...@wikimedia.ch wrote:
I feel we should keep in line with the function calls. There are already
way too
many spaces as it is, and there is never a problem telling control
structures
apart - they are always followed by an indented block and most editors
highlight
them. I think if(), while(), foreach(), for() should all
2013/1/22 Paul Selitskas p.selits...@gmail.com
What do you mean by
any wikicode (template call, parameter, link) present into
the value of infobox parameter breaks the stuff, since it is parsed and
expanded by parser with unpredictable results.
If your {{{author}}} doesn't have
Hey,
I hereby admit defeat. My thread was clearly not the ultimate bikeshed.
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
Lmao. Honestly I don't care either way, and any attempt to make up reasons
for one over the other is going to be insignificant. We just need to pick
one and stick with it. If we can agree on one, I'll personally go through
the entire codebase and change it.
*--*
*Tyler Romeo*
Stevens Institute of
On 2013-01-22 6:05 PM, Jeroen De Dauw jeroended...@gmail.com wrote:
Hey,
I hereby admit defeat. My thread was clearly not the ultimate bikeshed.
Cheers
--
On this bikeshed, allowing both styles sounds perfectly acceptable to me.
-bawolff
___
On 2013-01-22 6:03 PM, Alex Brollo alex.bro...@gmail.com wrote:
2013/1/22 Paul Selitskas p.selits...@gmail.com
What do you mean by
any wikicode (template call, parameter, link) present into
the value of infobox parameter breaks the stuff, since it is parsed
and
expanded by parser
There will be no mess. You'll just get span data-author=[[Alessandro
Manzoni]]/span (did you even lift^Wtry, bro? :)), at least at Wikipedia
that is what I get. If it could pass raw HTML into attributes, you'd get a
huge hole for XSSploits lovers.
On Wed, Jan 23, 2013 at 1:03 AM, Alex Brollo
It will just strip the whole attribute if there is a quote in. That is why
we have {{urlencode:{{{1}}}|WIKI}} (or any other mode).
On Wed, Jan 23, 2013 at 1:18 AM, Bawolff Bawolff bawo...@gmail.com wrote:
On 2013-01-22 6:03 PM, Alex Brollo alex.bro...@gmail.com wrote:
2013/1/22 Paul
On 01/22/2013 05:24 PM, Paul Selitskas wrote:
It will just strip the whole attribute if there is a quote in. That is why
we have {{urlencode:{{{1}}}|WIKI}} (or any other mode).
URL-encoding is not the same as HTML-encoding for an attribute. I'm not
sure if we have a parser function for the
I think adding reviewers to commit messages would be a useful thing to
do and I guess should be relatively easy?
I think a form of tagging in gerrit would be highly useful.
The thing I got from this article is sometimes it is useful to a
potential code reviewer to get an idea of how much time
All,
The switchover work is done.
The site was was available to readers throughout the migration work though
it was in read-only mode for about 32 minutes, when Asher and Mark had to
migrate the database masters over from Tampa to Ashburn.
We will cancel the reminding maintenance windows.
On Tue, Jan 22, 2013 at 2:53 PM, Ct Woo ct...@wikimedia.org wrote:
The switchover work is done.
The site was was available to readers throughout the migration work though
it was in read-only mode for about 32 minutes, when Asher and Mark had to
migrate the database masters over from Tampa to
Good work to everyone involved!
-bawolff
On 2013-01-22 6:53 PM, Ct Woo ct...@wikimedia.org wrote:
All,
The switchover work is done.
The site was was available to readers throughout the migration work though
it was in read-only mode for about 32 minutes, when Asher and Mark had to
migrate
Wow, awesome, congratulations all!
On Tue, Jan 22, 2013 at 3:53 PM, Ct Woo ct...@wikimedia.org wrote:
We will cancel the reminding maintenance windows.
Does this mean the deployment freeze for the rest of the week has been
thawed, or are deployments still on hold until next week?
--
Arthur
Congrats, guys and gals.
--
Ori Livneh
On Tuesday, January 22, 2013 at 3:22 PM, Bawolff Bawolff wrote:
Good work to everyone involved!
-bawolff
On 2013-01-22 6:53 PM, Ct Woo ct...@wikimedia.org
(mailto:ct...@wikimedia.org) wrote:
All,
The switchover work is done.
The
2013/1/22 Paul Selitskas p.selits...@gmail.com
There will be no mess. You'll just get span data-author=[[Alessandro
Manzoni]]/span (did you even lift^Wtry, bro? :)), at least at Wikipedia
that is what I get. If it could pass raw HTML into attributes, you'd get a
huge hole for XSSploits
So seamless. Well done!
--tomasz
On Tue, Jan 22, 2013 at 2:53 PM, Ct Woo ct...@wikimedia.org wrote:
All,
The switchover work is done.
The site was was available to readers throughout the migration work though
it was in read-only mode for about 32 minutes, when Asher and Mark had to
Filed a bug report: https://bugzilla.wikimedia.org/show_bug.cgi?id=44262.
On Wed, Jan 23, 2013 at 1:34 AM, Matthew Flaschen
mflasc...@wikimedia.orgwrote:
On 01/22/2013 05:24 PM, Paul Selitskas wrote:
It will just strip the whole attribute if there is a quote in. That is
why
we have
On 01/22/2013 07:52 PM, Paul Selitskas wrote:
Filed a bug report: https://bugzilla.wikimedia.org/show_bug.cgi?id=44262.
On Wed, Jan 23, 2013 at 1:34 AM, Matthew Flaschen
mflasc...@wikimedia.orgwrote:
On 01/22/2013 05:24 PM, Paul Selitskas wrote:
It will just strip the whole attribute if
On Tue, Jan 22, 2013 at 4:14 PM, John Vandenberg jay...@gmail.com wrote:
They were.
I hope that will be fixed quickly.
The easiest way to do that would be to redirect them to
wikimania.wikimedia.org, which already redirects to the proper year
through Wikimedia's redirects.conf.
--
Casey Brown
On 30/12/12 08:23, Alex Brollo wrote:
I'd like to use html comment into raw wiki text, to use them as effective,
server-unexpensive data containers that could be read and parsed by a js
script in view mode. But I see that html comment, written into raw wiki
text, are stripped away by parsing
On Wed, Jan 23, 2013 at 3:53 AM, Bawolff Bawolff bawo...@gmail.com wrote:
Someone should write a browser addon to automatically decode and fill in
captchas for blind users. (Only half joking)
Don't joke, I have a blind relative who's screen reader does just that
(simple captchas only).
There
Well done, very pleased to see that the careful planning paid off so well.
I raise a glass in honour of those who worked so hard to make this an
almost invisible operation.
Risker
On 22 January 2013 19:04, Tomasz Finc tf...@wikimedia.org wrote:
So seamless. Well done!
--tomasz
On Tue, Jan
On 23/01/13 10:05, Brion Vibber wrote:
Note that test.wikipedia.org is still in read-only mode
https://bugzilla.wikimedia.org/show_bug.cgi?id=44259.
Fixed.
-- Tim Starling
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
I agree with the reviewers thing. Because then it gets put on the record as
to who supported/had a problem with the commit.
*--*
*Tyler Romeo*
Stevens Institute of Technology, Class of 2015
Major in Computer Science
www.whizkidztech.com | tylerro...@gmail.com
On Tue, Jan 22, 2013 at 5:40 PM,
There is a Firefox extension to get past the captchas...
-- Forwarded message --
From: Graham Pearce graha...@jazi.net
Date: Wed, Jan 23, 2013 at 5:41 PM
Subject: Re: Fwd: [Wikitech-l] Why are we still using captchas on WMF sites?
To: John Vandenberg jay...@gmail.com
Yes, I
Am 22.01.2013 22:14, schrieb John Vandenberg:
Were the domains not previously set to redirect to the latest wikimania
wiki?
They were.
I hope that will be fixed quickly.
That has been done beforehand already, so the transfer of the domains
was transparent to the users.
/Manuel
--
Am 23.01.2013 02:12, schrieb Casey Brown:
On Tue, Jan 22, 2013 at 4:14 PM, John Vandenberg jay...@gmail.com wrote:
They were.
I hope that will be fixed quickly.
The easiest way to do that would be to redirect them to
wikimania.wikimedia.org, which already redirects to the proper year
59 matches
Mail list logo
