On 04/02/15 14:57, Manish Goregaokar wrote:
> I don't see any, however since Servo isn't being dogfooded yet, there's not
> much data we can gather on this (yet).
>
> Still, it would be interesting to hide a bunch of "useful" web platform
> features behind some flags, add some specific reporting/l
I don't see any, however since Servo isn't being dogfooded yet, there's not
much data we can gather on this (yet).
Still, it would be interesting to hide a bunch of "useful" web platform
features behind some flags, add some specific reporting/logging, and see
how many of them are really needed (an
> However, do see Brian Smith's recent proposal on this topic:
> https://briansmith.org/referrer-01.html
This looks extremely reasonable. Is there any reason not to adopt this
in Servo and see if it works?
jack.
___
dev-servo mailing list
dev-servo@list
On 20/01/15 19:33, Kyle Huey wrote:
> Unfortunately removing the referrer header is generally not compatible with
> the web.
However, do see Brian Smith's recent proposal on this topic:
https://briansmith.org/referrer-01.html
Gerv
___
dev-servo mailing
On Tue, Jan 20, 2015 at 4:50 AM, Marcus wrote:
> The HTTP referer hurts people's privacy and serve no purpose but to give
> companies, governments and website owners in general information about the
> person visiting the page.
> If servo is to respect its users and their privacy, actually being t
The HTTP referer hurts people's privacy and serve no purpose but to give
companies, governments and website owners in general information about the
person visiting the page.
If servo is to respect its users and their privacy, actually being the browser
of the future, I think the HTTP referer sho
6 matches
Mail list logo
