Live data from Hacker News

To download from Google Drive, you must enable third party cookies?

support.google.com

41–50 of 166 posts

Re: To download from Google Drive, you must enable third party cookies?

#41
post #26

Earlier quoted context omitted.

It's a defense in depth mechanism: when you allow user-generated content uploaded on your main domain, somebody will find a way to break your security system and make that content executable on the user's browser. When doing so, an attacker can steal cookies, and/or invoke APIs for the user. Now, there are of course ways to avoid that, but in the end, if every other system fails, being on a domain without any API and…

Is this also another case for hosting your main site on www.example.com instead of example.com? This way you could have cookies only on www.example.com while hosting user generated content on assets.example.com or whatever sub-domain you want that's not www?

Yes and no: one thing I totally forgot to mention is phishing. You don't want to give any semblance of endorsement to user-generated contents: many viewers will check only the main domain, due to how browsers' URL bars hide stuff.

Having a total different domain help highlighting that it is not official content.

Re: To download from Google Drive, you must enable third party cookies?

#42

If you’re anyway using Google Drive, you could use Firefox with the Google Container extension [1] to limit Google’s tracking activities across Google tabs to this container. Also install Cookie AutoDelete [2] and let the cookies, cache, local storage, etc., get cleared soon after you close the tabs. [1]: https://addons.mozilla.org/en-US/firefox/addon/google-contai... [2]: https://addons.mozilla.org/en-US/firefox/add…

Honestly anyone concerned about a Chrome / WebKit browser monopoly needs to use Firefox now if you already are not.

Can't do that when Firefox simply isn't good enough. Vivaldi beats it in features and what I need from browser as a power-user.

Re: To download from Google Drive, you must enable third party cookies?

#43
post #19

Earlier quoted context omitted.

I don't see any problems with a monoculture of rendering engine. Browser (and features, especially privacy ones), absolutely. Renderer, not so much.

In general, I like to have at least two implementations to make sure multiple implementations are possible. If the rendering engine bit-rots, goes the way of the original Netscape, Internet Explorer, etc., you don't want the internet to break.

Eh. That’s kinda like “don’t put all your money in dollars”

If the US Dollar goes to zero or the only rendering engine bit rots, other things are happening such that I won’t be too concerned about not having money or not being able to browse the web.

Re: To download from Google Drive, you must enable third party cookies?

#45
post #33

This is wrong: try downloading something with Safari, which blocks third party cookies by default, and it works fine. Instead, the problem is that downloading from Google Drive is using User-Agent sniffing to determine whether third party cookies are expected to be enabled, and choosing between implementations. (Disclosure: I used to work at Google, but I don't know anything internal on this)

[deleted]

Re: To download from Google Drive, you must enable third party cookies?

#46

If you’re anyway using Google Drive, you could use Firefox with the Google Container extension [1] to limit Google’s tracking activities across Google tabs to this container. Also install Cookie AutoDelete [2] and let the cookies, cache, local storage, etc., get cleared soon after you close the tabs. [1]: https://addons.mozilla.org/en-US/firefox/addon/google-contai... [2]: https://addons.mozilla.org/en-US/firefox/add…

Honestly anyone concerned about a Chrome / WebKit browser monopoly needs to use Firefox now if you already are not.

I'd love to, but it's simply unusable compared to Chrome when it comes to web development.

Re: To download from Google Drive, you must enable third party cookies?

#47
post #19

Earlier quoted context omitted.

I don't see any problems with a monoculture of rendering engine. Browser (and features, especially privacy ones), absolutely. Renderer, not so much.

Have you ever used a service in life where there is no competition? Straight up lack of competition examples are the easiest: DMV, airport food court, buying beer at a sports stadium etc. If you work in tech then you’ve probably had to use software over whose purchase you had no control: Jira, PeopleHR, Taleo, Concur. There’s no competition there because you, the end user, don’t have the option to choose from a free…

We are talking at cross purposes: your comment is a reasonable refutation of a browser monoculture, something we agree would be bad.

FWIW I am typing my response to you in Graphene.

Ultimately the issue is: what is the harm in using a library maintained by Google to do the webview rendering in a non-Google browser? I just don't see it.

Re: To download from Google Drive, you must enable third party cookies?

#49
post #33

This is wrong: try downloading something with Safari, which blocks third party cookies by default, and it works fine. Instead, the problem is that downloading from Google Drive is using User-Agent sniffing to determine whether third party cookies are expected to be enabled, and choosing between implementations. (Disclosure: I used to work at Google, but I don't know anything internal on this)

Or Safari has an exception for google cookies.

Re: To download from Google Drive, you must enable third party cookies?

#50
post #19

Earlier quoted context omitted.

I don't see any problems with a monoculture of rendering engine. Browser (and features, especially privacy ones), absolutely. Renderer, not so much.

Have you ever used a service in life where there is no competition? Straight up lack of competition examples are the easiest: DMV, airport food court, buying beer at a sports stadium etc. If you work in tech then you’ve probably had to use software over whose purchase you had no control: Jira, PeopleHR, Taleo, Concur. There’s no competition there because you, the end user, don’t have the option to choose from a free…

The argument needs to be more subtle to make sense, since Blink is open-source, whereas IE was not. Contrarily, I see another analogy; Blink being like Linux's dominance in infrastructure.
Post reply on HN