A Potential Privacy Model for the Web
github.com
A Potential Privacy Model for the Web
1–10 of 40 posts
Re: A Potential Privacy Model for the Web
#2A similar idea has occurred to me. I imagine a browser plugin that allows third-party cookies, but associates them per-domain visited. That is, the cookie that google analytics gets would be different when I'm visiting siteA.com vs siteB.com.
I don't share the author's optimism that dialogue will result in "a new identity end state that works for everyone." I believe on-line privacy has to be protected through non-negotiable mechanisms, against the interests that stand to profit from taking it away.
Re: A Potential Privacy Model for the Web
#3A similar idea has occurred to me. I imagine a browser plugin that allows third-party cookies, but associates them per-domain visited. That is, the cookie that google analytics gets would be different when I'm visiting siteA.com vs siteB.com. I don't share the author's optimism that dialogue will result in "a new identity end state that works for everyone." I believe on-line privacy has to be protected through non-ne…
> That is, the cookie that google analytics gets would be different when I'm visiting siteA.com vs siteB.com.
Isn't this part of what Firefox containers do?
Re: A Potential Privacy Model for the Web
#4> The identity "Me while I'm visiting nytimes.com" is distinct from the identity "Me while visiting cnn.com".
Trying to solve this through purely technical means is futile. If you block it at the user-agent, sites will share data at the back-end to create a super-profile.
Right now it's really convenient for advertisers to run an ad auction right in the user's web browser because all the context is there -- take that away and you'll see user data aggregated on the back-end instead.
Absent some type of regulation and enforcement, I really don't see how this puts a dent in the "reads a lot of articles on NY times about dogs, sees a lot of ads on cnn.com for dog food" profile aggregation.
Re: A Potential Privacy Model for the Web
#5I seriously can't see any dialog working while one of the sides has a strong vested economical interest in keeping the status quo.
Even with all JS and cookies disabled, servers can still collect your IP and infer if it is indeed you visiting by analysing your usual visit times -- and likely a lot more other metrics.
Unless the browsers use Tor-like visitor source obfuscation, I don't see anything changing in favour of privacy.
Re: A Potential Privacy Model for the Web
#6> The identity "Me while I'm visiting nytimes.com" is distinct from the identity "Me while visiting cnn.com". Trying to solve this through purely technical means is futile. If you block it at the user-agent, sites will share data at the back-end to create a super-profile. Right now it's really convenient for advertisers to run an ad auction right in the user's web browser because all the context is there -- take that…
> take that away and you'll see user data aggregated on the back-end instead
OK, but at least then it's not polluting the user's experience and burning the user's CPU cycles. Still a strictly positive change IMO.
Re: A Potential Privacy Model for the Web
#7we designed www.abine.com's Blur to enable users to implement some of these "compartementalization" techniques in practice. web traffic, fingerprinting, and tracking is one layer, but stateful registration, login, and payment is a whole other layer. tldr: it is a tough problem to deliver a simple experience on.
Re: A Potential Privacy Model for the Web
#8I seriously can't see any dialog working while one of the sides has a strong vested economical interest in keeping the status quo. Even with all JS and cookies disabled, servers can still collect your IP and infer if it is indeed you visiting by analysing your usual visit times -- and likely a lot more other metrics. Unless the browsers use Tor-like visitor source obfuscation, I don't see anything changing in favour…
With JS and cookies disabled and using a VPN you can get a decent browsing experience without tor slowness and blocks. At least your browsing is mixed with thousand people.
Re: A Potential Privacy Model for the Web
#9> The identity "Me while I'm visiting nytimes.com" is distinct from the identity "Me while visiting cnn.com". Trying to solve this through purely technical means is futile. If you block it at the user-agent, sites will share data at the back-end to create a super-profile. Right now it's really convenient for advertisers to run an ad auction right in the user's web browser because all the context is there -- take that…
> take that away and you'll see user data aggregated on the back-end instead OK, but at least then it's not polluting the user's experience and burning the user's CPU cycles. Still a strictly positive change IMO.
The negative side is that you can no longer see what sites are doing it, what they're doing, or block it in your browser
Re: A Potential Privacy Model for the Web
#10I seriously can't see any dialog working while one of the sides has a strong vested economical interest in keeping the status quo. Even with all JS and cookies disabled, servers can still collect your IP and infer if it is indeed you visiting by analysing your usual visit times -- and likely a lot more other metrics. Unless the browsers use Tor-like visitor source obfuscation, I don't see anything changing in favour…
With JS and cookies disabled and using a VPN you can get a decent browsing experience without tor slowness and blocks. At least your browsing is mixed with thousand people.
Sure. But lately I keep hearing that these users are implicitly under attack by constantly requiring them to fill CAPTCHAs.