On Jul 11, 2014 9:33 AM, "Amir Ladsgroup" ladsgroup@gmail.com wrote:
On Fri, Jul 11, 2014 at 1:23 PM, Antoine Musso hashar+wmf@free.fr wrote:
Le 10/07/2014 21:29, Amir Ladsgroup a écrit :
As ISO 8859 supports % character, this sounds like a reasonable
solution
for me. we need to just use urllib2 library to encode it.
That it is a bit hard to read though :-D The whole purpose is for site operators to quickly find out who is behind the bot and work with them to fix it / stop hammering the site. A human readable user-agent with detailed point of contact for the bot operator will dramatically speed up looking up the contact.
I disagree, decoding websites can decode username in just a second, and
note that just a very low proportion of bot usernames needs to encoded (i.e. the encoded version is not the same as real one.)
Well, my idea was that you could paste in browser location bar and let it magically decode for you.
e.g. append after https://meta.wikimedia.org/wiki/Special:CentralAuth/
or it might even get decoded automatically if you use it in the path for a nonworking host. (depending on browser) e.g. 127.0.0.1:85/%32
Another option is to make users install a redirect onwiki from latin to canonical.
But the operator knows the best way to contact them, we should let them specify what they want. (but see also caveat about single operator running multiple bots. some may cause problems while others do not)
-Jeremy