71–80 of 927 posts
Safari already was lagging behind Chrome, Chrome forks and Firefox in a lot of feature adoption. This will only make it more of a "new Internet Explorer", a browser that sites recommend you NOT to use.
Good luck with telling people not to use Safari (or more accurately WebKit) on iOS....
https://www.forbes.com/sites/gordonkelly/2020/03/14/apple-io...
You Apple users will put up with anything!
(disclaimer: iOS user)
> "...But deleting all local storage (including Indexed DB, etc.) after 7 days..."
From the Apple announcement:
> Now ITP [Intelligent Tracking Prevention] 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. ...
https://webkit.org/blog/10218/full-third-party-cookie-blocki...
Better title: Apple restricts tracking by limiting browser storage, which hurts my particular app. Browsers need to be severely limited due to them running arbitrary code from the web. Doesn't matter if it's an offline web app. If you want more access, make a native app (with or without web technologies).
But browsers are severely sandboxed already. What the article is talking about is: > deleting all local storage (including Indexed DB, etc.) after 7 days which I can see how it might help privacy (since you could be tracked via local storage too) but also how it might break any potential web app that might need data to last more than 7 days. > If you want more access, make a native app But then, everybody will compla…
webkit is open source - can't this be changed (be it by fork, or a commit proposal?)
Earlier quoted context omitted.
User not coming to website 7 days can't be invalid use-case. Losing important data simply because someone went on vacation is unacceptable.
So store this data on the server.
Earlier quoted context omitted.
Yea, we actually don't use safari at all in our app. So this might not have an effect but it's pretty vague.
If you don't use Safari you can patch webkit to change the policy, right? Change 7 to 10000000
Do you mean that you deploy a 'native' app that's really just a wrapper around a web view that would also be just Safari? Same policy applies, but now, you have the option, in native code, to siphon off data and put it into Real Storage.
Earlier quoted context omitted.
I have many useful files in my computer, which I don't want to be deleted. You are saying, that it is ok, if the OS deletes all files in my computer from time to time. A local storage is the only way webapps can store any data in your computer (other than asking you to manually load / save some configuration file). Not all webapps can afford cloud storage for all user.
I am not saying that it is OK to delete all your files. I am saying it has always been like that in the case of a browser's local storage. As I said, that use case was out of the window long before. From the start, as far as I know. No browser has ever given you any definite promise on whether your local storage data will be kept. That's also true for IndexedDB. So you need a mechanism to restore that data, be it clo…
Better title: Apple restricts tracking by limiting browser storage, which hurts my particular app. Browsers need to be severely limited due to them running arbitrary code from the web. Doesn't matter if it's an offline web app. If you want more access, make a native app (with or without web technologies).
How's installing a native app better for a random user privacy or security wise, exactly?