Worth noting that it's not actually "Google" that said to "hang tight". An entire brand does not make a decision like whether to support Linux. It's a two-pizza team with a shitty budget and a remit to just keep the damn thing from going down and working out all the bugs with basic features like moving a file to a new folder in a weird drop-down. I'm sure the team would like to support Linux, if they had a bigger bud…
The team who made the post were representing Google, therefor the company made the post. To propose otherwise implies that all similar actions/statements made in a similar way are not made by the company, which is both ludicrous and also causes Google to not exist.
10 years since Google said to “hang tight” about Linux support for Google Drive
141–150 of 227 posts
Re: 10 years since Google said to “hang tight” about Linux support for Google Drive
#142Insync works well, and it's 50% off for a couple more days: https://www.insynchq.com/ Not affiliated, but $15 is not a lot to pay, as opposed to waiting for something that probably won't happen.
Rclone has support for Google Drive, and it's open source: https://rclone.org/
There's a command line client that uses a push/pull workflow: https://github.com/odeke-em/drive It was written by a member of the Google Drive team.
Gnome supports Google Drive, or at least used to, directly in Nautilus. I don't use Gnome, so I can't comment.
There may be other options I've missed, but the point is that there is already good support in multiple forms. I'd be interested to know what support Google could provide that's not already available.
Re: 10 years since Google said to “hang tight” about Linux support for Google Drive
#143Earlier quoted context omitted.
There's Google Chat, which is really made for companies but available on normal accounts too, and Google Messages, their SMS/MMS/RCS app for Android, which requires that you have an Android phone and a phone plan.
I think I may make an independent thread about this soon (but my question may be stupid): why does messages use this paradigm of connecting to one's phone directly instead of accessing texts in some centralized fashion? Is that impossible because only the carrier has the contents of the thread (even though other services can be used to post texts)?
Re: 10 years since Google said to “hang tight” about Linux support for Google Drive
#144Worth noting that it's not actually "Google" that said to "hang tight". An entire brand does not make a decision like whether to support Linux. It's a two-pizza team with a shitty budget and a remit to just keep the damn thing from going down and working out all the bugs with basic features like moving a file to a new folder in a weird drop-down. I'm sure the team would like to support Linux, if they had a bigger bud…
The team who made the post were representing Google, therefor the company made the post. To propose otherwise implies that all similar actions/statements made in a similar way are not made by the company, which is both ludicrous and also causes Google to not exist.
Re: 10 years since Google said to “hang tight” about Linux support for Google Drive
#145I’m glad that Dropbox provides a Linux client, although it is annoying that it is limited to x86 and ext4. At least the latter can be worked around with a loopback device.
Dropbox works on zfs, xfs and btrfs just fine. Source: https://help.dropbox.com/installs-integrations/desktop/syste...
Re: 10 years since Google said to “hang tight” about Linux support for Google Drive
#146Earlier quoted context omitted.
Samba. I tried AD very briefly before realizing how absolutely terrible of an idea it was. It just makes life so complicated, and AD integration was not as good as I was hoping. I can see why this market constantly has all kinds of crazy offerings… As far as permissions go, I guess I am mostly ignoring granular permissions. I’m generally only concerned with permissions on a per-share basis. This way, file permissions…
SMB3 is secure over the internet. But you really have to make sure it is an encrypted connection. In Samba you do this by adding: server min protocol = SMB3 smb encrypt = required to the [global] section of your smb.conf.
That said: for the moment, I still have some SMB1 clients inside my network. Yes, this is terrible, and frankly it is surprising Samba still supports it (I won’t be too surprised or too angry if it gets removed now that it’s separated out.) I should probably segregate SMB1 clients onto a different fileserver on a different VLAN or something. Until then, it would be annoying to force SMB3 on all clients.
(As for why Anybody would use SMB1, the answer is retro computing. I also suspect that Open PS2 Loader is an SMB1 client, though I have not checked.)
Re: 10 years since Google said to “hang tight” about Linux support for Google Drive
#147Just give us a web filesystem already. Stop with these shitty infantilized GUIs with no hierarchical organization and an overreliance on search to find things. I have literally hundreds of thousands to millions of files on my local machines and have no trouble remembering where I put things. Drive can't seem to scale past a few dozen before it's confusing, useless, and apparently lossy. Remember when web servers woul…
There is a transition from a file-centric to an app-centric model, that I mostly disapprove of, but that's what is happening. Before, you had files stored in a filesystem, you picked the file and opened it with the app. On Windows, you double-click on the file, on a command line, you type "app filename". Now the trend is to first open the app and then use the app to fetch your data, that data is entirely managed by t…
Re: 10 years since Google said to “hang tight” about Linux support for Google Drive
#148Re: 10 years since Google said to “hang tight” about Linux support for Google Drive
#149But I understand the frustration and that some people do miss it...
Re: 10 years since Google said to “hang tight” about Linux support for Google Drive
#150Earlier quoted context omitted.
You nailed it. Every 3 years google renames and rebadges their chat system. I don't even know what to call it anymore.
I've posted this link before in comments, but for anyone who's not read this arstechnica piece it is well worth it: A decade and a half of instability: The history of Google messaging apps https://arstechnica.com/gadgets/2021/08/a-decade-and-a-half-...