![]() ![]() Having some form of revokable authorization to be able to click on links from a person is superior to "all sketchy links working instantly." Third party cookies have nothing to do with it. The alternative is trusting all shared links, which is currently what Google does. it's a link to a drive that I already have read/write access to. It's not an unsolicited link to someone else's Google Drive. Moreover, in a work context, you would probably be sharing links to files that are on a shared google drive that I have equal access to already, so that would not require additional verification. Based on my own experience, most people would go months or years between seeing these emails, since people tend to share files with (and receive files from) the same people over and over. Do you know this person? Are you sure you want to receive files from them?" "This person tried to share a file with you. You can think of it as the equivalent of a friend request. The error page denying access could even indicate that the user should check their email for additional verification. When you share something with me for the first time, I would have to accept it via a Google-sent email containing a link that only Google knows (not something that can be sent via slack), and then all your future share links would work for me on slack. So, if I've never accepted a share from you before, your links won't work. X.Maybe my phrasing was awkward, but I said you would only have to do this once for a given account. Step 2: Paste below code in index.js file "use strict" Step 1: Paste below code in index.html file Or, without jQuery: function download(.urls) )) You can create a temporary set of hidden iframes, initiate download by GET or POST inside of them, wait for downloads to start and remove iframes:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |