Live data from Hacker News

Addressing Antigravity Bans and Reinstating Access

github.com

21–30 of 230 posts

Re: Addressing Antigravity Bans and Reinstating Access

#21

I still kinda wish that the subscriptions would just allow you to use the tokens however you wish. I get that they rely on people not using all of their quota. But e.g. with open code it doesn't really matter if I use antigravity or gemini-cli the usage should be about the same. What they are actually trying to force you to do is to pay for the tokens that you don't use in their applications to increase their revenue…

> But e.g. with open code it doesn't really matter if I use antigravity or gemini-cli the usage should be about the same.

This is not at all true. What is prompting this behavior from Google and Anthropic is that people are using their oauth creds/API keys to run OpenClaw bots that use orders of magnitude more tokens than the IDEs. The official clients also can use a lot more prompt caching because they have expected workflows.

And like, if you want to run OpenClaw, they’re not saying you can’t do that: use the API pricing, that’s what it’s for. But people are getting mad that they’re not allowed to roll their pickup truck up to the all-you-can-eat buffet table and fill it.

Re: Addressing Antigravity Bans and Reinstating Access

#22
post #11
post #8

Way too risky to use Google services like this tied to your primary account. There’s too much risk of cross damage. Imagine losing access to your Gmail because some Gemini request flags you as an undesirable. The digital death sentence of losing access to your email with a company that notoriously has no way for the average human to contact a human is not worth the risk.

This wasn't due to some random Gemini request. Users were using sketchy antigravity auth plugins to use their antigravity tokens on things like OpenClaw, clearly against ToS. It's great that Google is giving these users a second chance.

When's the last time you read the ToS of a service you signed up for?

Re: Addressing Antigravity Bans and Reinstating Access

#24
post #11

Earlier quoted context omitted.

This wasn't due to some random Gemini request. Users were using sketchy antigravity auth plugins to use their antigravity tokens on things like OpenClaw, clearly against ToS. It's great that Google is giving these users a second chance.

It’s be great if Google just revoked antigravity access if terms were violated. No need to disable the entire account.

> just revoked antigravity access

That's exactly what they did, plus Gemini CLI and Code Assist, which are the same product in different formats.

Re: Addressing Antigravity Bans and Reinstating Access

#25

Still no clarification if they block your whole Google account or just Gemini?

Not the entire Google account.

> bans for Antigravity usage also blocked access to Gemini CLI and Gemini Code Assist.

Disclosure: I work at Google, but not on anything related to this.

Re: Addressing Antigravity Bans and Reinstating Access

#26
What I don’t understand about policy violations is why Google never warns the user before banning. A simple alert or email would reduce so much frustration on the part of users and so much overhead for Google.

ToS change frequently and it’s not really fair to assume the user knows what is and is not correct use of tokens.

Re: Addressing Antigravity Bans and Reinstating Access

#27
post #11
post #8

Way too risky to use Google services like this tied to your primary account. There’s too much risk of cross damage. Imagine losing access to your Gmail because some Gemini request flags you as an undesirable. The digital death sentence of losing access to your email with a company that notoriously has no way for the average human to contact a human is not worth the risk.

This wasn't due to some random Gemini request. Users were using sketchy antigravity auth plugins to use their antigravity tokens on things like OpenClaw, clearly against ToS. It's great that Google is giving these users a second chance.

>It's great that Google is giving these users a second chance.

I hope this is sarcasm. A permaban as the first action is never a good idea.

Re: Addressing Antigravity Bans and Reinstating Access

#28
post #6

Over the past week, A week? Try at least 16 days https://discuss.ai.google.dev/t/account-restricted-without-w... The danger here is they'll ban you with no specific reason, fill out the form and you get an automatic unban and then something else automatically flags and you're banned the second time permanently. Support bot will then say "you were warned, read the TOS" and you get to guess what you did wrong. You'll n…

People are crazy to use Google as the core of their online identity.

Re: Addressing Antigravity Bans and Reinstating Access

#29

What I don’t understand about policy violations is why Google never warns the user before banning. A simple alert or email would reduce so much frustration on the part of users and so much overhead for Google. ToS change frequently and it’s not really fair to assume the user knows what is and is not correct use of tokens.

Not just Google. This seems to be the default for most tech giants. I was banned on Facebook for an unknown reason, not provided any explanation, and given zero recourse. Had to resort to reaching out to a friend who worked there.

Re: Addressing Antigravity Bans and Reinstating Access

#30

I still kinda wish that the subscriptions would just allow you to use the tokens however you wish. I get that they rely on people not using all of their quota. But e.g. with open code it doesn't really matter if I use antigravity or gemini-cli the usage should be about the same. What they are actually trying to force you to do is to pay for the tokens that you don't use in their applications to increase their revenue…

[deleted]
Post reply on HN