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

End of the road for Google Drive in Transmit

blog.panic.com

Post reply on HN
Print view View original

71–80 of 196 posts

Re: End of the road for Google Drive in Transmit

#71

Post by sadeshmukh »

dewey wrote: post #25
addisonj wrote: post #17

Man... this stuff sucks. If I were panic, I would do the same... but I also wouldn't want to be the one at google to navigate this. With Google Drive now being at the center of so many companies for storing business data, I am certain it is a juicy target, and third party access with full access to read and write to that big hard drive full of proprietary data is one that I would understand want to lock down... but n…

> With Google Drive now being at the center of so many companies for storing business data, I am certain it is a juicy target, and third party access with full access to read and write to that big hard drive full of proprietary data is one that I would understand want to lock down... but not like this? Could be a Google Workspace policy where you can just set that employees can't access the corporate Drive account th…

That's already how it works for workspace, in my experience.

Re: End of the road for Google Drive in Transmit

#72

Post by aaronharnly »

davedx wrote: post #5

> But then… a couple of months later, Google completely removed the option for us to scan our own code. Instead, to keep access to Google Drive, we would now have to pay one of Google’s business partners to conduct the review. What a racket. Smells downright anti-competitive The EU will have fun with this when it catches up.

Just as a data point, we paid $750 for one of these engagements (scan + some discussion about use cases etc) to one of Google's preferred providers. There were multiple options for providers.

Re: End of the road for Google Drive in Transmit

#73

Post by JamesBarney »

dewey wrote: post #10

Even the "audit" they require for increasing something simple as your YouTube API quota is already annoying and a massive waste of time, and this is not even close to the one they are requiring from Panic. The quota increase process is roughly: 1) Fill out the same form every year from scratch 2) Send it into the black hole that's Google "support" 3) A few weeks later receive a reply from someone asking a irrelevant…

When we filled ours out for a CRM they wanted a video of the CRM. So we showed them a video (from dev with fake data). We appealed the process explaining that Mickey Mouse is a not a real person. They rejected that appeal. So after going back and forth for a week or two we uploaded a video with basically everything but the navmenu blurred out and they finally approved it.

The entire process was awful.

Re: End of the road for Google Drive in Transmit

#74

Post by quantadev »

mullingitover wrote: post #20
quantadev wrote: post #9

Never hitch your wagon to somebody else's horse. Entire companies have been destroyed because they rely on Amazon, Google, or some other service, and then have the rug pulled. Sometimes companies have even been destroyed, notably by Amazon, for having the wrong political viewpoints. My rule of thumb is: Only use open source components, and only run my stuff on Linux. So that way I maintain full control over my stack,…

> Sometimes companies have even been destroyed, notably by Amazon, for having the wrong political viewpoints. Ok, I'll ask: what company did Amazon destroy for having the wrong political viewpoint? AWS hosts some pretty vile stuff without blinking. The last time a company made a big "woe is me, my ideas are being suppressed" claim against Amazon, it was Parler, and they weren't kicked off for their viewpoints. They w…

[flagged]

Re: End of the road for Google Drive in Transmit

#76

Post by cpr »

hn_throwaway_99 wrote: post #24

I wrote this response to another front page HN article on a similar topic: https://news.ycombinator.com/item?id=41664753 I know everyone loves to dunk on Google, and I definitely agree their communication and customer service to app developers is shite, but this change to permissions scope is a good thing. If you have full, unfettered access to large number of people's Google Drive data, you're a huge target for male…

The problem is that if you want to provide a full-featured file picker, and not rely on Google's limited browser-based version, your app will require the full "drive" scope. (We do, and we do, for our InDesign-to-Google Docs connector plugin.)

If you use some of the lower-tier CASA labs, it's not that expensive (4K/year), but it is definitely a nuisance for a pure desktop plugin like ours that has absolutely no cloud component (other than connecting to GDocs).

Re: End of the road for Google Drive in Transmit

#78

Post by happymellon »

8338550bff96 wrote: post #48
dewey wrote: post #10

Even the "audit" they require for increasing something simple as your YouTube API quota is already annoying and a massive waste of time, and this is not even close to the one they are requiring from Panic. The quota increase process is roughly: 1) Fill out the same form every year from scratch 2) Send it into the black hole that's Google "support" 3) A few weeks later receive a reply from someone asking a irrelevant…

Have the same experience with Microsoft support. The difference is the timeline is much shorter and when our issues don't get any traction our rep intervenes and escalates to engineers. I understand that level-1 support for these orgs are basically documentation librarians. Cool. We pay an incredible amount for premium support, but whatever. It's fine. What matters is that we have a rep that is engaged and cares abou…

And as much as I dislike Amazon and the juggernaut of AWS, this is how they win me over.

It's rarely a complete black hole, and I have spoken to product engineers and owners for multiple lines.

Re: End of the road for Google Drive in Transmit

#79

Post by tiltowait »

quantadev wrote: post #9

Never hitch your wagon to somebody else's horse. Entire companies have been destroyed because they rely on Amazon, Google, or some other service, and then have the rug pulled. Sometimes companies have even been destroyed, notably by Amazon, for having the wrong political viewpoints. My rule of thumb is: Only use open source components, and only run my stuff on Linux. So that way I maintain full control over my stack,…

> Never hitch your wagon to somebody else's horse.

Though this was a nice and welcome feature, it wasn’t Transmit’s only feature nor even its main one. I don’t think this sentiment applies, exactly.

Re: End of the road for Google Drive in Transmit

#80

Post by quantadev »

dewey wrote: post #12
quantadev wrote: post #9

Never hitch your wagon to somebody else's horse. Entire companies have been destroyed because they rely on Amazon, Google, or some other service, and then have the rug pulled. Sometimes companies have even been destroyed, notably by Amazon, for having the wrong political viewpoints. My rule of thumb is: Only use open source components, and only run my stuff on Linux. So that way I maintain full control over my stack,…

That sounds great, but also for an app that interacts with > 10 services and companies it's not really a good advice. > Only use open source components, and only run my stuff on Linux Most people don't have the luxury of never having to interact with Google Drive, MS Teams, Slack etc.

Sure integration points to all that are great. The mistake is when your entire company can no longer function at all without Amazon AWS for example. I've worked at a place like that.

EDIT: Of course if you're sure your politics are completely left-leaning you'll have no censorship worries, because these platforms are mostly Silicon Valley run. Also since conservatives basically don't play dirty in this way, the conservatives won't censor stuff just because it's left-leaning. We're for protecting freedom of all legal speech and actions.

Post reply on HN