Re:Web Writable Files API: Simplifying Local File Access
by icebraining on Monday November 12, 2018 @04:55PM
(#18436267)
Nobody said the sites would have unfettered access to these files like they do with their cookies. Putting an ID on a photo is useless if you then have to ask the user to read it again the next time.
Also, why would they be outside the reach of adblockers? WebExtensions can already intercept and manipulate the use of certain APIs by sites, the same can easily apply here.
Re:Web Writable Files API: Simplifying Local File Access
by gdfasfklshg4 on Tuesday November 13, 2018 @04:16AM
(#18439704)
I suspect it will start with persistent login based on a file and grow from there.
This is certainly going to be immediately abused for encrypted storage of persistent cookies and tracking identifiers.
- If my site generates cat pics, I'll put identifiers in the metadata fields of the image format.
- If my site generates markdown, I'll put identifiers in an alternate data stream (Windows) or encoded in the whitespace.
Since the files exist outside of the sandbox, they'll be outside of the scope of privacy features like clearing the cache or cookies, and outside of the reach of adblocker extensions.