End of the road for Google Drive in Transmit
blog.panic.com
End of the road for Google Drive in Transmit
1–10 of 196 posts
Re: End of the road for Google Drive in Transmit
#2Google really is wrecking hell on third party integrations.
Re: End of the road for Google Drive in Transmit
#3Google really is wrecking hell on third party integrations.
"The fastest path to wealth is the construction of these digital platforms, where other people depend on you."
- Eric Schmidt.
Many products leads at Google seem to disagree!
Re: End of the road for Google Drive in Transmit
#4Title on the blog is now (changed?):
"End of the Road for Google Drive in Transmit"
The being unfamiliar with Transmit the "and" gave me a startle
Re: End of the road for Google Drive in Transmit
#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.
Re: End of the road for Google Drive in Transmit
#6I am not sure smaller devs were given the option of self-scanning code. I always wondered what the point of that was, given that there is no way for Google to ensure that the scanned code was the version distributed, and even then, as soon as a minor update was released it would have been out of date.
Re: End of the road for Google Drive in Transmit
#7There is a clear subtext to this and the Play Store changes: everyone interacting with the Google ecosystem is going to be pinned down and deanonymized with rights assigned based on legal identities. This will be done in the name of security. There is no freedom in who you trust here.
The big question here is if all this was preemptive or the response to something.
Re: End of the road for Google Drive in Transmit
#8The original title now reads “…for Google drive in Transmit”. @donatj can you correct the HN title please.
Re: End of the road for Google Drive in Transmit
#9Never 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, and stay mostly immune from the political rug pulls, and other kinds of rug pulls.
Re: End of the road for Google Drive in Transmit
#10Even 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 question to our use case
4) Two weeks later another person replies asking for screenshots of the "implementation", so you send a screenshot of "func storeTrailerMetadata()"
5) Another two weeks later, another automated person replies that you got approved.