3 ms·
Everything has been moving to first party especially during the last year. So the origin is the one storing the tracking data, capturing it and sending it to M
by threeseed 3y ago
Everything has been moving to first party especially during the last year.
So the origin is the one storing the tracking data, capturing it and sending it to Meta etc.
Which is what makes this so hard as there is no difference between a PWA and a rogue website.
- no_wizard 3y agoNow we're getting into the fundamental fact that some websites have lots of tracking and such, and some don't. This is no different than having to send the files to a server owned by the website. I fail to see any meaningful difference here. Should we also not allow HTTP requests? I don't see how this is different.
- threeseed 3y agoWe are talking about storing data on user's computers. If you allow PWA apps to do this. You also allow websites to use it for tracking. Hence why Apple restricted this feature.
- no_wizard 3y agoStoring data with user permissions, not permission-less. Its in no way like local storage or indexdb. Those permissions could be scoped to only allowing explict read/write of certain files (IE, the ones the user initiated) and not allow for arbitrary writing of files to the filesystem, for instance. We already do this with the file upload API