Live data from Hacker News

10 years since Google said to “hang tight” about Linux support for Google Drive

abevoelker.github.io

221–227 of 227 posts

Re: 10 years since Google said to “hang tight” about Linux support for Google Drive

#221
post #157

Earlier quoted context omitted.

It was Slack/etc years before those existed. They just couldn't figure out how to market it because there were no reference points at the time, so few could see any reason to use it.

I doubt it's just that. If those things were actually great, people would have embraced them like they did slack. Consider Google+ also. They had plenty of reference points for that. It was just not very good. Google tends to abandon development on new projects way too quickly, before they're ready for mass appeal. They probably expect it to explode like Gmail did. But I think they forget they lost a lot of promotors…

Before Slack there was Flowdock (which was never as popular) and I'm pretty sure another I'm forgetting from back then. I used Slack as probably the best-known example.

"We couldn't figure out how to market it" was from an interview straight from the people who made it: The companies they pitched to responded with things like "why would we need this, we have email".

Re: 10 years since Google said to “hang tight” about Linux support for Google Drive

#222

I connected my Linux systems to my Nextcloud server, and then I connected my Gdrive as external storage in Nextcloud. When I turned on server side encryption in Nextcloud it also encrypted my connected storage of Gdrive. So I accomplished both Gdrive integration as well as file encryption at the same time.

> I connected my Gdrive as external storage in Nextcloud. This bit sounds interesting, could you explain it a little more, how you managed it?

I have since just moved everything into my Nextcloud server since it does everything I need and keeps my data totally private. It is on a Raspberry PI running Yunohost, and I can add additional drives as needed. I don't remember all I did when I setup the Gdrive, but I recommend checking the official documentation at https://docs.nextcloud.com/server/latest/admin_manual/config...

Re: 10 years since Google said to “hang tight” about Linux support for Google Drive

#224
post #117

Earlier quoted context omitted.

I've been very happy with self-hosting a Seafile instance to serve as a personal cloud for myself and a small academic ML team. I built a small NAS, Proxmox runs on baremetal, on top of which there's an ubuntu VM running a Seafile docker instance. Fantastic performance, so so much more efficient for syncing large libraries b/w machines. Owncloud/Nextcloud was a pig for my purposes, it seemed unable to sync libraries…

The last time I used Seafile, it was very slow, and it was more of a pain to get and keep running than it was worth, though I was using the free version instead of the paid version. The problem with seafile I had was if I tried to sync down files and the sync client stopped, it would have no problem uploading the incomplete downloads as changes to the server, as well as pushing missing as deletes to the server. I did…

> The problem with seafile I had was if I tried to sync down files and the sync client stopped, it would have no problem uploading the incomplete downloads as changes to the server, as well as pushing missing as deletes to the server.

this surely does not seem like a 'corner case' and would be absolutely terrifying if true.

could you be more specific in regards to the circumstances?

Re: 10 years since Google said to “hang tight” about Linux support for Google Drive

#225

Earlier quoted context omitted.

I've been very happy with self-hosting a Seafile instance to serve as a personal cloud for myself and a small academic ML team. I built a small NAS, Proxmox runs on baremetal, on top of which there's an ubuntu VM running a Seafile docker instance. Fantastic performance, so so much more efficient for syncing large libraries b/w machines. Owncloud/Nextcloud was a pig for my purposes, it seemed unable to sync libraries…

Why are you running Seafile in Docker, and not directly in Ubuntu? Why are you running Ubuntu in Proxmox, and not directly on the metal? Thank you! I might set up a NAS in the very near future.

container/vm makes for easier deployment and management, seldom technical reasons.

Re: 10 years since Google said to “hang tight” about Linux support for Google Drive

#226
post #9

Times have changed in many more ways than one. These days I greatly prefer to own my data more directly, which I accomplish using a NAS. I don’t use Dropbox OR Google Drive, I use Syncthing, which can do stuff that neither of those could ever dream of in terms of syncing between machines. Not only do I not want Google Drive, I don’t even want anything like it. That said, I totally get why it’s still important. I do u…

My NAS of 6 years just crapped out on me a couple days ago. Probably just the power supply, but my suggestion is to get 2 NASes in RAID6 and mirror data between them if you can.

raid5/6 are traps because they increase complexity by a unreasonable ammount (and recovery workload).

just use raid1 if you are not in a position to write an academic paper on the differences.

Re: 10 years since Google said to “hang tight” about Linux support for Google Drive

#227
post #140

Earlier quoted context omitted.

I work on Drive. If you're observing deleted files, and you don't have any third party applications with access to your Drive, we'd be very interested in hearing from you, we take data integrity issues very seriously. You can check the activity under any folder and see what issued the deletes. If there are missing files _without_ an entry there, and it doesn't seem to be a rogue integration with the Drive API, feel f…

I appreciate the response. Despite my acidulous comment I have only once personally experienced a silent deletion, and it was with a Google Sheet a few years ago. It was a "Copy of" produced by "make a copy" menu option that ended up deleted, which I confirmed with someone else who also had made a copy the same exact way, who couldnt access theirs either. Is this expected behavior when the source file is deleted, or…

> It was a "Copy of" produced by "make a copy" menu option that ended up deleted, which I confirmed with someone else who also had made a copy the same exact way, who couldnt access theirs either. Is this expected behavior when the source file is deleted, or is it, as I thought, a bug?

Without being able to look at the item in question, I couldn't tell. However, deleting copies when a source file disappears is unexpected and as far as I'm aware there's no mechanism for "dependent" deletes.

Where did you copy the item to? Was it stored in your My Drive?

Post reply on HN