Google Drive trash items will be automatically deleted after 30 days
gsuiteupdates.googleblog.com
gsuiteupdates.googleblog.com
https://www.reddit.com/r/talesfromtechsupport/comments/22ke8...
https://www.reddit.com/r/talesfromtechsupport/comments/c24q2...
https://www.reddit.com/r/talesfromtechsupport/comments/flgsn...
https://www.reddit.com/r/talesfromtechsupport/comments/65cam...
https://www.reddit.com/r/talesfromtechsupport/comments/bks9e...
https://www.reddit.com/r/talesfromtechsupport/comments/9wrsc...
> IT: This is the trash bin, you would move files here to delete them off of your computer.
> CW: IT IS NOT A TRASH CAN, IT IS A RECYCLING BIN! IT SAYS SO RIGHT UNDER THE ICON!
Ok, now wait a second, why the hell is it called a recycling bin anyway?
"Recycling" doesn't mean "plan to throw this away later, but maybe I'll still grab it out of the trash can in case I made a mistake." Who came up with this metaphor?
The word you are looking for is "copying".
I'd honestly prefer if the policy would at least excempt reasonably small files or textfiles.
Of course it was never meant as a place to store users files temporarily, it was always for programs that needed to write a temporary file.
We had a BSD system and an Ultrix system. For convenience I temporarily NFS mounted the root of the Ultrix system into /tmp/foo on the BSD machine. After I was done I forgot to umount the volume.
The next day, the Ultrix machine behaved really weird. Things seemed to work fine, but a lot of files were missing. It took a bit of troubleshooting before we figured out what had happened.
As it turns out, the nightly /tmp cleanup script had run on the BSD machine, and this script deleted all files which had not been accessed in a week. Of course the script had traversed the NFS mount and cleaned up everything on the root disk of the other machine. This meant that all the files that were commonly used were still there, so things seemed fine until you tried to do anything that involved files that hadn't been touched in the last week.
That's when I learned never to use /tmp for anything important.
Not-very-well-thought-out-examples:
http - Always returns 404.
https - Always returns 404.
ipp - Returns whatever IPP says for "printer not found" or equivalent.
lpd - Takes data, does nothing with it.
dns - Always returns NXDOMAIN.
ident - Always returns nobody:nogroup
telnet - Accepts any username/password/credentials, returns "This account is not available" and immediately exits.
ssh - Accepts any username/password/credentials, returns "This account is not available" and immediately exits.
smtp - Accepts message, doesn't do anything with it.
pop3/imap - Accepts any login, always has 0 messages.
irc - Accepts any nick, PRIVMSG or other commands, commands don't actually do anything. Returns null list of channels and users when queried.
vnc - ?
rdp - ?
Etc.
Of course, when they first wrote this, I imagine keeping trash indefinitely had a nearly nonexistent impact on the bottom line, and now there's probably several datacenter racks worth of drives dedicated to storing and replicating trash.
Why is why they don't just let everyone upload HD videos to Youtube.
Oh wait
> ..Google Drive is making a change so that its trash behaves more consistently with the rest of Google applications (such as Gmail) with regards to automatic deletion.
https://android.stackexchange.com/questions/209777/drive-sen...
Seems like this could backfire badly on their upgrade revenues TBH, for this reason.
I was surprised last year, when my Drive was running out of space, to discover everything I'd ever deleted was still there and counting against my quota, even from years before. I mean, it was easy enough to empty the trash and fix it, but still -- I'd just assumed things got deleted after something reasonable like a month. A month feels "UX standard" to me.
[1] https://developers.google.com/drive/api/v2/reference/files/e...
Considering data stored for a long time and very rarely accessed is effectively free in a modern datacenter (since disks are all IO limited not capacity limited in cloud deployments), I reckon they're losing money with this change.
There's a good chance they're doing it because their lawyers have told them to - clicking the "send to trash" button could be considered a GDPR deletion request, and if Google leaves that document in the trash forever, they could be found in breach of GDPR rules.
Looking for recommendations for non-Google trashcans that provide strong guarantees of durability...
Are you seriously suggesting that when I'm at the coffee shop, I use their trashcan for this purpose?
I miss “Don’t Be Evil.”
The product is considered to be a sort of cloth receptacle with 1-3 handles or "straps" as we've com to call them, that can be used with almost any human protrusion, but the final product might change. We are also thinking about a zero-strap version that we just call "the unStrap".
Of course it will be cloud-native, k8s-native and almost virtually-sustainable. I have my C-CTO working on the multi-native strategy right now.
Pre-decision-decision is one of 3 to 15 things we have have identified that we will consider caring strongly about in the near future.
Thank you for your feedback, and would you mind filling in a short customer service form here: http://oracle.dev-enterprise.tech.ai/customer/"backpack"-sta... ((copy) copy 2).pdf?
It really helps us to know something (I think somebody said it was NPS or CRO or something called "W/E")
So deleting trashed items will mean Google is storing a lot less data, and probably not impacting people's storage purchase decisions much/at all. I expect it'd be a net benefit for their bottom line.
More likely, Google will be deleting vast quantities of data and saving money due to the reduced amount of storage they're using.
btw: it took me a lot of time to delete my trash once I started cleaning up an almost full gmail account: a bit like when you want to delete your old facebook posts.