3 ms·
I rarely use my GDrive but today I had to download an image sent from my phone and wasn't allowed because third party cookies were disabled. It seems like they'
by kevin_thibedeau 5y ago
I rarely use my GDrive but today I had to download an image sent from my phone and wasn't allowed because third party cookies were disabled. It seems like they've added a new dark pattern to force 3PC on but nobody's been complaining about it. It seems absolutely ridiculous that a Google property depends on a separate domain for access. After enabling, there were network requests to googleusercontent.com which really has no reason to exist other than to serve as a wedge for the dark pattern.
- g_p 5y agoNot excusing their dark patterns (which don't play nice if you block double-click at DNS level, but just as an observation, googleusercontent.com itself is actually a legitimate and valid (at least IMO) security precaution. By serving up all user generated content from a separate domain, it gives defense-in-depth against any kind of uploaded content getting script execution - it's served up from a domain that is completely separate from any authentication tokens or valuable cookies etc. That way, a user-uploaded HTML file (if someone found an endpoint that would render it) shouldn't be able to be served up from a first-party domain.