I think e-mail address is something personal and sensitive and is out of the reach of CUs and nowhere in Wikipedia is compulsory. Additionally, Pywikibot may be used in various MW installations of which we don't know anything in advance. Thus not a very good idea. What was the goal of including the username? Is it worth? The price should not be bigger then the advantage. 2014-07-10 20:47 GMT+02:00 Amir Ladsgroup <ladsgroup(a)gmail.com>om>: -- Bináris

On Jul 10, 2014 2:48 PM, "Amir Ladsgroup" <ladsgroup(a)gmail.com> wrote: user-agent in header of API calls. but only ISO 8859 is being supported and usernames can be anything (utf-8). For usernames that might not compatible, people need to put e-mail address in user-config.py. Is it okay for you? Any comments? Why not just percent-encode the username?

I don't see anything like a compulsory username in this policy. I think Pywikibot has a UA that complies, it does not have to be unique and personal. I rememberd something like statistical purpose but may have mismatched something. But I have no problem with going to wikitech-l if you understand the policy in a different way. 2014-07-10 21:19 GMT+02:00 Amir Ladsgroup <ladsgroup(a)gmail.com>om>: -- Bináris

On Jul 10, 2014 3:30 PM, "Bináris" <wikiposta(a)gmail.com> wrote: Pywikibot has a UA that complies, it does not have to be unique and personal. something. policy in a different way. No, the whole point is to be unique, not statistics. I haven't read the policy recently but if the policy is unclear then we can change the policy. -Jeremy

Just sent an e-mail to wikitech-l Best On Fri, Jul 11, 2014 at 12:40 AM, Frances Hocutt <frances.hocutt(a)gmail.com> wrote: -- Amir

On Jul 11, 2014 1:08 AM, "Bináris" <wikiposta(a)gmail.com> wrote: Well, not identification exactly. But it should be unique per bot and offer a way to contact the operator. (not just identify the operator; a single operator may operate both misbehaving and compliant bots) It's beyond a doubt that this is part of the guidelines. If you don't comply and you're causing problems then you may find your IP blocked from *reading* (or maybe just writing to) the wikis. Imagine if that IP is the toolserver? (I know it's dead, pretend it's 2012 for a second) If you have a good UA string then roots can block narrowly just the problem and not everyone else on your server and also can initiate contact with the operator to get the bot fixed. Instead of waiting for the operator to find the roots and ask why the bot is blocked. Also, if the bot is somehow logged out, the bot/operator should still be identified in UA string. However, in this case there is still a point that it is only expected in Foundation's wikis and not neccessary in other MW installations.And once any personal data is not neccessary, it is not desirable and reasonable. What exactly is the objection to bots using unique UA strings? account the bot uses and personalize the UA only for those accounts where this switch is on. IMO, it should have nothing to do with which wiki you're using. If users want to turn it off for a given wiki, fine. Default to enabled. -Jeremy

Le 10/07/2014 21:29, Amir Ladsgroup a écrit : 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. -- Antoine "hashar" Musso

Re user agents, 2010 was a long time ago from an ops perspective. The need for a user agent is no doubt as strong as in the 2010 edict from Domas, but I would like clarification from ops regarding 'gold standard' before we build something which may no longer be needed by them. On Fri, Jul 11, 2014 at 11:32 PM, Amir Ladsgroup <ladsgroup(a)gmail.com> wrote: -- John Vandenberg

On Jul 11, 2014 9:33 AM, "Amir Ladsgroup" <ladsgroup(a)gmail.com> wrote: solution 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

On Mon, Jul 14, 2014 at 6:59 PM, Bináris <wikiposta(a)gmail.com> wrote: Urlencoded will be 'nice' for many usernames which are not quite ISO 8859 We could use the 'wiki name and oldid' of the userpage as a readable fallback for usernames which would contain 'too many' %s (4?). -- John Vandenberg

I made a patch to add any customized user agent and (username would be default) and if the person doesn't want to add any user agent, they just can set it to " " https://gerrit.wikimedia.org/r/#/c/147381/ I would be happy for any comments regarding this patch Best On Mon, Jul 14, 2014 at 2:08 PM, Bináris <wikiposta(a)gmail.com> wrote: -- Amir