News for hackers. Stuff that matters.
Re:Full third-party cookie blocking and more by infotogivenm on Tuesday March 24, 2020 @07:28PM (#22680173)
It is confusingly worded, but DOES NOT mean all browser storage mechanisms will break.

The key phrase is “without user interaction”. Only e.g. invisible nested iframes that scammy ad companies love to use will have their localstorage limits affected. Top level frames are unchanged.

Re:Full third-party cookie blocking and more by jahewson on Tuesday March 24, 2020 @07:46PM (#22680309)
I think you’ve also misread the original text:

“seven days of Safari use without user interaction on the site”

Does not mean that top-level frames are unaffected. Everybody is affected. They specifically call out first party storage as being misused currently. I think the correct interpretation is:

Whenever the user interacts with your page then the clock gets reset to 7 days, also the clock only runs on days the user uses Safari.

Re:Full third-party cookie blocking and more by jessaustin on Tuesday March 24, 2020 @07:53PM (#22680368)
I hope you're right! Where TFA has:

Now ITP has aligned the remaining script-writable storage forms with the existing client-side cookie restriction, deleting all of a website’s script-writable storage after seven days of Safari use without user interaction on the site.

...maybe "script-writable" should be "third-party-in-iframe-script-writable"? If so this document should be edited.

Re:Full third-party cookie blocking and more by infotogivenm on Tuesday March 24, 2020 @07:30PM (#22680190)
To be clearer; this is a huge win for privacy/antitracking without any? real downsides.

> “chrome will never have this”

Indeed :)