An update on this request: Lars and I went off-list for a bit (Nuria and Mikhail are cc-ed in those conversations). Research doesn't have capacity to pick this task up at the moment, but if other people with appropriate access have bandwidth to pick it up and respond to it, they should feel free to. A few things for those who may be able to help: * Lars confirmed that even the skewed data from very specific browsers may help them gain some insight and it can be better than not knowing anything extra at all (the current case). * If you decide to work on a query and release the data, please ping Research and Legal before releasing it unless the data is highly aggregated. This can especially be important in this case where only a few not-very-widely used browsers are sending this information to our servers.
Lars: I'm sorry that Research was not able to be of help. With the best of our intentions, we have to say no to so many requests. We need to be aware of our already long backlogs, but also aware of other teams' backlogs that will be affected by our decision. In this case, depending on which path we go with, Research commitment can mean Security, Legal, Analytics, and Tech Ops commitment and work. Thank you for your understanding, and I'm here to help if someone else picks up this task and they need Research input. Best, Leila -- Leila Zia Senior Research Scientist Wikimedia Foundation On Tue, Nov 7, 2017 at 12:22 PM, Nuria Ruiz <[email protected]> wrote: > I would say that referrer "origin-when-cross-origin" (Send a full URL when > performing a same-origin request, but only send the origin of the document > for other cases) is probably the most widely deployed default on the > internets, we use it as well as google, facebook... > > > For wikipedia, see: https://phabricator.wikimedia.org/T87276 > > On Tue, Nov 7, 2017 at 12:07 PM, Lars Noodén <[email protected]> wrote: >> >> On 11/07/2017 09:49 PM, Mikhail Popov wrote: >> > The referrer policy is already in use at Google, which is why we >> > don't see users' search queries in referer field in our request logs; >> > just that they came from Google. >> >> Thanks. I'm looking at the current version: >> https://www.w3.org/TR/referrer-policy/ >> >> Are there any published articles, statistics, or reports about how >> widely referrer policy has already been deployed? >> >> /Lars >> >> _______________________________________________ >> Analytics mailing list >> [email protected] >> https://lists.wikimedia.org/mailman/listinfo/analytics > > > > _______________________________________________ > Analytics mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/analytics > _______________________________________________ Analytics mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/analytics
