Author: rransom Date: 2011-04-26 15:06:46 +0000 (Tue, 26 Apr 2011) New Revision: 24678 Modified: projects/articles/browser-privacy/W3CIdentity.tex Log: Improve style more Modified: projects/articles/browser-privacy/W3CIdentity.tex =================================================================== --- projects/articles/browser-privacy/W3CIdentity.tex 2011-04-26 15:06:06 UTC (rev 24677) +++ projects/articles/browser-privacy/W3CIdentity.tex 2011-04-26 15:06:46 UTC (rev 24678) @@ -251,9 +251,9 @@ the cache to store identifiers. It does this by limiting the scope of the cache to the top-level origin in the URL bar. This has the effect that commonly sourced content elements are fetched and cached repeatedly, but this -is the desired property. Each of these prevalent content elements can be -crafted to include unique identifiers for each user, tracking users who -attempt to avoid tracking by clearing cookies. +is necessary to prevent linkability: each of these content elements can be +crafted to include an identifier unique to each user, thus tracking users who +attempt to avoid tracking by clearing normal cookies. The Mozilla development wiki describes an origin model improvement for cookie transmission @@ -266,7 +266,7 @@ current site. % XXXX I can't tell what this paragraph is supposed to mean. --RR -Similarly, one could imagine this two level dual-keyed origin isolation being +Similarly, one could imagine this two-level dual-keyed origin isolation being deployed to improve similar issues with DOM Storage and cryptographic tokens. Making the origin model for browser identifiers more closely match user