4 ms·
You know, we put a "padlock" on the address-line for a reason. Why can't we just make it easy for anyone to inspect the persistent state associated with a websi
by lwlml 9y ago
You know, we put a "padlock" on the address-line for a reason. Why can't we just make it easy for anyone to inspect the persistent state associated with a website. Websites already make site-maps to tell search engines how they work, why can't websites tell end-users what data they create and use with your browser? Treat them like capabilities and let the user decide if your website gets to treat your localStorage as a stalking ground of your behavior or if they'll have to work even harder.
This kind of contract can do in both ways. The user can set up a permission set to give to the website. If the website balks then the user can go somewhere else or negotiate with their own principles how much they want to be "the product."
- pdimitar 9y agoAlways wanted something like what you suggested. It would be fair to the users, hence why it's not implemented (lol).