On 05/17/2013 04:23 PM, David Abián wrote:

Hello all,

In the last weeks, I have been applying protocol-relative URLs in links with an HTTP defined protocol, and converting links from external to internal link format with my bot in all content pages of some (few) Wikimedia projects (please see details in [1]).

You quote Ryan Lane, "A number of templates, CSS, and Javascript on projects are improperly referencing resources, and as such, they are being loaded incorrectly. All resources should be referenced using protocol-relative URLs now (//<resource-url> vs http://<resource-url>)."

But he is talking about resources like CSS/images/JavaScript, which can cause mixed content warnings. Your bot only does links, which is a separate issue.

Note that public WMF wikis do not have such external content in wikitext. Images can only be from the local wiki or Commons (which of course handles the protocol right).

The rest (CSS, JavaScript, other images, etc.) can only be from extensions, gadgets, and user scripts.

However, most of the projects are still pending, this task is not included in GBs scope, the community is raising many doubts, and I think that, in some way, running this task on all pages and projects, even without exceptions, should be allowed.

I use HTTPS Everywhere myself, so I get where you're coming from. But I see this is a normal task that should follow the normal per-wiki bot approval process(es) (if any).

Matt Flaschen