I'm confused about if this means that IndexedDB will always wipe data after 7 days. That seems like it would prevent storage from being used for user data in PWAs.
The 7-Day Cap on All Script-Writeable Storage is troublesome: if I don't log into a computer for a week 'cause I'm on vacation then you wipe my saved data? I have local storage based utilities I've written that I sometimes don't touch for weeks, but whenever I go back everything I put in there is STILL THERE.<p>Seems like a great way to drive less use of local browser storage options and promote greater use of cloud storage solutions. Cynical me says "YAY iCloud".
> Safari continues to pave the way for privacy on the web, this time as the first mainstream browser to fully block third-party cookies by default<p>Too bad Safari isn't my default browser anymore, ever since they essentially killed it when they neutered extensions.
Rather than wiping indexed DB data after 7 days, could you not just make it an opt in thing, like the camera or mic? For example, ask users "Allow myapp.com to store app related data on your computer?". If they allow it, then give access to indexed DB API. That way we can still have fully local PWAs.
Still dreaming of a way to block cookies per-domain<p>Edit: someone just told me you can do it with osx adguard, in the user rules you can set "||domain.com^$cookie" to block all cookies from domain.com
Is there any legitimate reason Chrome doesn't follow suit other than they like ad revenue? An answer from a Googler here would be great. And a real answer, not corp-speak.<p>Blocking third party cookies seems like overall a good thing for security. Security is good right?<p>Edit: 2 years is a long time to wait for a security improvement that is literally flipping a switch.
The list of addons I consider essential for privacy just keeps growing. Here is another great addition:
<a href="https://github.com/Cookie-AutoDelete/Cookie-AutoDelete" rel="nofollow">https://github.com/Cookie-AutoDelete/Cookie-AutoDelete</a><p>Does what it says on the tin.
> this time as the first mainstream browser to fully block third-party cookies by default<p>Third party cookies have been blocked in Firefox since September 3rd (2019) [1]. They mention Brave in the article, so surely Firefox being large than Brave should be included in "Major browsers", but not a single mention was made in the article. It really reminds me of the meme "what do you mean you've seen it?".<p>[1] <a href="https://blog.mozilla.org/blog/2019/09/03/todays-firefox-blocks-third-party-tracking-cookies-and-cryptomining-by-default/" rel="nofollow">https://blog.mozilla.org/blog/2019/09/03/todays-firefox-bloc...</a>
meh. i mean ok yes this does kill the tracking (although i can imagine how to be more devious) but i already <i>very</i> easily do this with ghostery.<p>i suppose it’s great for the 90% of “default settings” users.<p>because a solution (many) is already available for tracker blocking , i’d rather see effective html5 video and popup blocking. is that infeasible?
Soooo... like Firefox has done be default since June 2019 then <a href="https://blog.mozilla.org/blog/2019/09/03/todays-firefox-blocks-third-party-tracking-cookies-and-cryptomining-by-default/" rel="nofollow">https://blog.mozilla.org/blog/2019/09/03/todays-firefox-bloc...</a> ?<p>I guess later is better than never, but this seems like something they could have done long ago.
So much for the advertisement-powered web. Congratulations, privacy people: you win. I hope the new web is everything you hoped. If it isn't, you have only yourselves to blame. Enjoy the paywalls.