Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

support.google.com

Post reply on HN
Print view View original

161–166 of 166 posts

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

#161

Post by ajvs »

jakear wrote: post #76
markussss wrote: post #53

Earlier quoted context omitted.

I have not found any shortcomings in Firefox for web development, so I'm wondering if you could you elaborate on what features are missing, or what killer features for web development Chrome has that Firefox doesn't?

The entire local file system api, for one: https://developer.mozilla.org/en-US/docs/Web/API/File_System... , which severely neuters any tooling designed to help you do real work on your own files.

Also a massive vulnerability surface letting arbitrary websites write whatever they want to your disk.

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

#162

Post by FateOfNations »

zagrebian wrote: post #129
ninju wrote: post #108

The title is tad incomplete. You need to enable 3rd party cookies ONLY FOR the drive endpoint, *drive.google.com*. You can whitelist which endpoints are permitted. They way the title is written it gave me the impression that you needed to enable 3rd party cookies globally (which is incorrect)

Are third-party cookies cross-origin or cross-site?

They specifically need to set a cookie so that googleusercontent.com knows who you are when you click a link on drive.google.com to download a file.

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

#163

Post by giancarlostoro »

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.

So why not just get rid of all browsers and have only Microsoft Edge then? Because that is the problem you end up with a bunch of proprietary features that only whoever maintains the main browser rendering engine has and everyone on Linux and probably Mac has to suffer for it.

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

#164

Post by zagrebian »

FateOfNations wrote: post #162
zagrebian wrote: post #129

Earlier quoted context omitted.

Are third-party cookies cross-origin or cross-site?

They specifically need to set a cookie so that googleusercontent.com knows who you are when you click a link on drive.google.com to download a file.

I’m asking generally.

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

#165

Post by jakear »

ajvs wrote: post #161
jakear wrote: post #76

Earlier quoted context omitted.

The entire local file system api, for one: https://developer.mozilla.org/en-US/docs/Web/API/File_System... , which severely neuters any tooling designed to help you do real work on your own files.

Also a massive vulnerability surface letting arbitrary websites write whatever they want to your disk.

Definitely not. You have to explicitly select a directory from a native file system UI then confirm both read and write access for each directory, across each domain, typically each session. And system directories are blocked outright with no way to override.

This attitude is why people dismiss Firefox: “well if FF doesn’t implement it, it must be bad. Other browsers surely have glaring security holes”

(Source: I implemented the file system integration for vscode.dev)

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

#166

Post by zmxz »

markussss wrote: post #53
zmxz wrote: post #46

Earlier quoted context omitted.

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

I have not found any shortcomings in Firefox for web development, so I'm wondering if you could you elaborate on what features are missing, or what killer features for web development Chrome has that Firefox doesn't?

Development console in Firefox is lacking compared to Chrome's. Also, the whole Firefox browser is massively slower. There have been benchmarks that prove what I'm typing here, I can't give you a definite list and I see that people started jumping on the downvote hammer so I'm not inclined to defend my opinion. It's my experience, and if someone else's experience differs - I'm glad for them.
Post reply on HN