To download from Google Drive, you must enable third party cookies? • Hacker News Board

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

#31

Post by LinAGKar » Tue, Jul 19, 2022, 10:55 AM UTC

newscracker wrote: post #15

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…

That's not really usable until they fix the issue where it wipes the tabs history.

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

#32

Post by wanderingmind » Tue, Jul 19, 2022, 11:00 AM UTC

If using linux or mac, just FUSE mount with rclone. If you need more privacy,load the mount with encryption so google has no idea about the files you are working with.

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

#33

Post by jefftk » Tue, Jul 19, 2022, 11:01 AM UTC

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)

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

#34

Post by grosswait » Tue, Jul 19, 2022, 11:03 AM UTC

sneak wrote: post #30

pjerem wrote: post #28

Earlier quoted context omitted.

The problem is that you are giving full power for creating de-facto standards to the rendering engine. If Blink decides to support a feature, it becomes a de-facto standard even if the feature solely serves Google (think FLoC, AMP ...) or is hard to replicate. It's also an issue because now the web is at risk to become only usable from devices that are physically able to run Blink/Webkit which means nobody in the fut…

Neither FLoC nor AMP are part of the renderer. AMP isn't even clientside, it is a feature of the Google search webapp. If Google were trying to leverage the renderer to assert Chrome over say Brave or Edge, sure, but they're not, and if they do, it will be forked. Do we have the same concerns over type layout engine monoculture?

We have the same concerns over any lower level components, yes. I don’t think a type layout engine is comparable to a web render.

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

#35

Post by jefftk » Tue, Jul 19, 2022, 11:03 AM UTC

GTP wrote: post #18

And from their solution: "Type chrome://settings/cookies in the browser address bar" I love how they assume everybody uses Chrome.

It's only broken on Chrome, though. In Safari it works fine without third party cookies.

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

#36

Post by frognumber » Tue, Jul 19, 2022, 11:06 AM UTC

sneak wrote: post #19

giancarlostoro wrote: post #17

Earlier quoted context omitted.

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

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.

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

#37

Post by shreyshnaccount » Tue, Jul 19, 2022, 11:19 AM UTC

sneak wrote: post #19

giancarlostoro wrote: post #17

Earlier quoted context omitted.

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

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

I see the problem if the monoculture is dominated by for profit big tech corpos

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

#38

Post by dvfjsdhgfv » Tue, Jul 19, 2022, 11:20 AM UTC

kevin_thibedeau wrote: post #29

dvfjsdhgfv wrote: post #2

Seems like in this particular case, notwithstanding Google's long history of abuse and opportunism, this one is a genuine case when you enable a cookie for technical and not (necessarily) user tracking reasons.

It's just another dark pattern their middle management cooks up under the guise of legitimacy.

In other cases - yes. In this one - not necessarily. The content itself is hosted on a different domain and for a good reason. Most importantly though, they don't need another cookie to track you: you are already there, they know who you are, they know you already requested a resource, and they can track you over all Google services and many others anyway. They don't need to use a dirty trick to send you an additional cookie although the very fact that we're having the discussion means Firefox made a good decision and hopefully people will notice this pattern more.

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

#39

Post by [deleted] » Tue, Jul 19, 2022, 11:22 AM UTC

newscracker wrote: post #15

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…

[deleted]

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

#40

Post by dethos » Tue, Jul 19, 2022, 11:24 AM UTC

I've faced this problem in the past and it is really annoying. One of the many reasons why I dislike this service and try to avoid it as much as possible.