3 ms·
Identity (as in a stable handle for your browser/device/profile) is an important part of the web. It's tied into all kinds of functionality and security. What
by manigandham 10y ago
Identity (as in a stable handle for your browser/device/profile) is an important part of the web. It's tied into all kinds of functionality and security.
What we really need is a device/OS level "ID" that can be read by any app or website so that it is stable. Since it's controlled by the OS, resetting your identity is as simple as generating a new ID. This single change would improve security and performance across the web and remove the vast majority of fingerprinting being used today.
- I_am_neo 10y ago"Identity (as in a stable handle for your browser/device/profile) is an important part of the web" Not for me I feel that only for the egotistical and those with money flatulent to spare does identity on the web mean as much as identity in real life.
- Paul-ish 10y agoThis wouldn't give us any more privacy. It would just become another signal in the tracker's model, they wouldn't solely rely on it. Cookies were the same idea limited to a single website. We were told to clear our cookies and we could prevent tracking. We have seen what cookies have become, with zombie cookies[1][2] raising from the dead after we think they are gone. At the end of the day, advertisers and trackers didn't really want us to have the capability to reset our identity with them. If you try to change the ID, trackers will use other things to try to keep tracking your browser session. [1] https://en.wikipedia.org/wiki/Zombie_cookie https://en.wikipedia.org/wiki/Zombie_cookie [2] https://en.wikipedia.org/wiki/Evercookie https://en.wikipedia.org/wiki/Evercookie
- manigandham 10y agoThe functionality (and corresponding machine implementation) matrix of a user will always give enough entropy to construct an identity, but much of this was created because of the lack of any other reliable and stable option. A stable ID would definitely be used since services now spend a considerable amount of time and effort in constantly figuring it out through other means. A single website is too narrow since things like ad networks (which are the economic backbone of the web) work across many sites. A single root domain is an outdated isolation model on the modern web. Outside of that, the only other answer is regulation. Something that is missing in many areas although some countries seem to be making good progress.
- harshreality 10y agoServices where security matters already manage it: they have a handful of contact points for each user, and they alert when an unknown browser/device/profile logs into the service. You want that centralized and made universal? An internet passport? Goodbye vpn services. Goodbye, tor. Goodbye doing anything that's not in your permanent browsing profile stored by advertisers, google, facebook, twitter.
- manigandham 10y agoA standard UUID generated at the OS level and passed through seamlessly through a browser? Yes. Client-side control means that you can turn it off depending on TOR, private-mode, VPN, or whatever else. The technical aspects though would make the web faster and easier to deal with.
- harshreality 10y agoSo you turn it off, and half the web stops working for you because websites don't want to serve you content unless their ad networks receive your unique hardware id from some mandatory hardware TPM? Then, since a TPM is effectively mandatory once the web can't be used without it, all media content can be DRM'd with less customer push-back. I get that the web is a mess, but is this the best idea anyone can come up with to fix it? And does this actually fix it?
- manigandham 10y agoIt's just a UUID number. Private browsing mode just generates a new UUID for that session by that browser. Otherwise use the default system UUID. And at any time, you can reset that default system UUID. Easy and seamless. Why turn it off? If you do, then the networks would just generate their own ID numbers and we're back to the same scenario as today. There's nothing technically wrong with not using it but having a stable API to program against helps a lot and is the main reason this would improve the web. Android and iOS get somewhat close to this, although both are broken and unfinished. I'm not sure why this requires any hardware TPM or DRM though.