Our Firebase and Google Cloud project was suspended over suspicious activity
medium.com
medium.com
I got about two hours into this and my account was deactivated, one of the cloud engineers sent me a truly nasty email saying that bitcoin mining is not allowed on google cloud and I should stop abusing resources and being so irresponsible. I replied and asked how on earth they came to the conclusion I was a bitcoin miner and explained what I was actually doing, but never heard back from them again.
It was so bizarre, I felt like I was back in the 3rd grade getting in trouble for knowing more about the Apples than the computer teacher.
Advertised as one thing, but once you start using it as advertised, provider starts crying about you being an unfair user.
FFS, no one is forcing you to offer this or that package, but how dare you accuse people of defrauding you when they just use whatever you offered. Just offer VMs that have 10% CPU time and that's it.
This is a pretty big claim. It would be grossly inappropriate if true. Do you have any evidence to back it up?
- This is the first post on a new blog by somebody without a full name or any social media presence that I can find (googling "amton gaming blockchain" returns zero hits)
- The company/site in question is never named or linked to
- They used somebody else's credit card and don't seem to have matching ID for it
Is "blockchain gaming" code for an online casino or something? If so, this is likely against GCP terms of service.
A bit of googling indicates it usually refers to tracking ownership of in-game items that players can sell/trade with each other.
(Not implying anything about this unnamed company.)
You ignore the point of the post - that Google can and will shut some clients down with little warning and even less recourse.
I know it's a common trope here that Google does evil things just for fun, but we've only got one side of the story here and there's been a number of previous cases here of apps getting kicked out for what turned out to be pretty understandable reasons.
And whether any of your analysis about the customer is accurate is irrelevant and not worth debate here.
Citation needed.
There are fan boys everywhere, Google has it far share who will never believe that Google is evil
Correction, you _gave_ them full control of your project, when you decided to use their APIs and tooling as the literal backbone of your application.
This is the tradeoff, and server administration is not something you can hack at, DevOps style. Proper external backups would've at least made switching away less painful.
If you wish to have full control of your data, you have to co-locate your own servers and run things on bare metal. Though running things on the cloud is a trade-off that many of us have made.
Terms of service and other agreements do not justify the careless approach that Google takes toward it's customers and customer service.
This situation should be resolved with capable humans in the Google business/account management group, but as we have seen so many times here on HN, that is not how Google operates.
Many companies are going to have learn this lesson the hard way, time after time see stories of companies under the impression that cloud == no need for backups.. its the cloud why would you need to back things up
This way of thinking will burn many many companies, even worse when you use a SaaS product that has no ability to export data so you are locked in... those companies are screwed
I'm not being facetious, but ops people have always decried giving up control of the platform and especially buying into lock-in to services that only exist in a particular cloud.
If there's no corollary to firebase, and your app is built entirely on firebase, and they increase the price or change direction, you gotta go with it. I mean it's the definition of vendor lock-in; and it applies too when the political whims of the company change. IE; if you're making games and you're hosted on Azure, you have to have some level of knowledge that Microsoft makes games too, and that they could potentially subtly harm you if you're outcompeting them.
Everyone knows that you "buy" time, you "buy" less burden of operation and you "buy" the fact that you're living at a higher abstraction and can move more rapidly; this is baked in to the extra cost of hosting with a cloud provider.
Maybe people don't really know (or grok) that you also "sell" not only your competence, but your self reliance?
If it were published up front that x% of Google customers will get locked out and lose their business, I think you would see a lot fewer of these stories because Google would get a lot less business.
People just are ignorant of the true risks here.
While involving a different cloud provider, I recently read a long thread from a Amazon (re)seller that got his/her funds frozen. There was a lot of indignation, about how Amazon could treat him/her this way, while he/she was making more than a million dollar each month. Personally, I think that the level of arrogance, self-entitlement and hubris (not just of this seller, but also the fellow sellers chiming in) was the most remarkable about it all. Obviously very opportunistic, but suddenly full of moral judgment when "screwed over" by Amazon. I'm not so sure it's just ignorance of the true risks.
The classic tale of "the scorpion and the frog" always comes to mind, when I read stories like these.
/m2c
As far as even how Amazon treats third party sellers, I’m not saying it’s an excuse, but the seller isn’t the ultimate customer - the buyer is. Amazon is very focused on good customer service for the buyer.
Google’s customer support is horrible.
It's a horrible lottery to play though.
Any other provider suspends accounts too - everyone has the same kind of abuse problem.
I think there's more people/companies in that category, but by a factor of how much.
Lock-in could be the reason they're still using it.
But it's not a turnkey solution, particularly with how ACL works (read granularity is at the database level)