Yep, as a web app developer I can't see what that has to do with privacy, it'll just slightly annoy the user into redoing the login within the new home shortcut(I don't use cookies for Auth)
what do you use for auth if not cookies? genuinely curious
The usual JWT Token
Re:WebKit Features in Safari 17.2
by diebeforei485 on Monday December 11, 2023 @08:30PM
(#38608067)
I parsed that sentence as - the separate web app gets its own cookie jar, and it's pre-populated with whatever cookies existed for that website in the browser at the time the user created the separate web app, but from that point forward nothing is shared between browser and web app.
Re:WebKit Features in Safari 17.2
by amadeuspagel on Tuesday December 12, 2023 @08:31AM
(#38611828)
Yes, that's also how I parsed it.
Re:WebKit Features in Safari 17.2
by diebeforei485 on Saturday December 16, 2023 @12:27AM
(#38661984)
Because the browser login cookies would transfer to the web app, why would they have to log in again when they open the web app?
Re:WebKit Features in Safari 17.2
by jensimmons on Tuesday December 12, 2023 @11:52PM
(#38622821)
Correct.
> After a user adds a web app to the Home Screen or Dock, no other website data is shared, which is great for privacy.
So an offline-first app will not work. A user has to login if they want to see the same data when they open a web app from the home screen and when they open the same web app from the browser, and the data has to be synced in the cloud to make that work. Great for privacy.