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

Addressing Antigravity Bans and Reinstating Access

github.com

Post reply on HN
Print view View original

151–160 of 230 posts

Re: Addressing Antigravity Bans and Reinstating Access

#151

Post by JoshTriplett »

sir0010010 wrote: post #98
JoshTriplett wrote: post #74

Earlier quoted context omitted.

That's a service that doesn't want your business. If you care, message them about it I've never once run into a service with such a restriction, but I can imagine someone being that short-sighted. I have seen services that only support "log in with Google or Facebook", which is comparably terrible.

I've run into services that will flag specific tlds as invalid.

I have heard of that, yeah. It's still busted, but marginally more understandable if they're dealing with a lot of scams. For instance, `.xyz` and some others have bad reputations. I've never seen something that'll reject an arbitrary self-owned `.org`, by way of example.

Re: Addressing Antigravity Bans and Reinstating Access

#152

Post by danielheath »

aliljet wrote: post #45
tjoff wrote: post #38

Earlier quoted context omitted.

Use a custom domain and don't use google for email. And if you do use your gmail address just forward it and start to transition to something else. With time everything of importance has been transferred.

How do you even pull away from a Gmail address? I'm nearly twenty years into that service. Getting banned would be absolutely devastating...

I switched to my own domain ages ago; it only took 2-3 years to stop getting relevant mail to the old one (I put a forwarding rule in place and just used the new one for everything).

Imported all my past mail on day one, forwarding meant I had one inbox only, and I only sent mail from the new domain. A few gentle “please stop using my old address” conversations with family.

Re: Addressing Antigravity Bans and Reinstating Access

#153

Post by bilalq »

tjoff wrote: post #38
koolba wrote: 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.

Use a custom domain and don't use google for email. And if you do use your gmail address just forward it and start to transition to something else. With time everything of importance has been transferred.

This has its own risk factors. If your domain renewal lapses due to credit card expiry or something and you fail to notice, it's catastrophic. This is just not realistic advice for the average person.

Re: Addressing Antigravity Bans and Reinstating Access

#154

Post by ShroudedNight »

plagiarist wrote: post #75
gruez wrote: post #49

Earlier quoted context omitted.

>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. This is almost as realistic as "I wish netflix or youtube allowed me to use VLC to watch their content".

I do wish that though. I have given up on streaming services, I am not paying for this bullshit experience. We used to have all the content unlimited on one service for like $10/mo. I can accept prices increasing with inflation but society should not accept such a backslide in service quality.

I would take things somewhat further: I'd be happy to pay the equivalent of $20 2015 dollars for this service if it were comprehensive. Unfortunately, that might allow for a consumer surplus to occur in the viewing experience and the motion picture industry ties with maybe nVidia for peak pathological hostility to retail consumer surplus.

Re: Addressing Antigravity Bans and Reinstating Access

#156

Post by cyberax »

bilalq wrote: post #153
tjoff wrote: post #38

Earlier quoted context omitted.

Use a custom domain and don't use google for email. And if you do use your gmail address just forward it and start to transition to something else. With time everything of importance has been transferred.

This has its own risk factors. If your domain renewal lapses due to credit card expiry or something and you fail to notice, it's catastrophic. This is just not realistic advice for the average person.

Not really? You just jump in and fix the domain name. You have 75 days before a lapsed domain is released into general availability.

Sure, you'll likely miss some emails, but otherwise it's safe.

Re: Addressing Antigravity Bans and Reinstating Access

#157

Post by meling »

What’s my remedy when Google’s product (Gemini 3.1 pro high) makes a “grave” mistake? This is unrelated to the bans that’s been happening recently, but wanted to share …

This morning I asked Gemini to “save” its output to a local file. However it did more than that … it committed the file (along with several unrelated staged changes that was not ready to be committed) and even pushed the changes to GitHub. I’ve never asked any model to commit, let alone push… I’m not impressed; actually a bit disappointed that it would do this without any warning up front. This happened in Antigravity.

Re: Addressing Antigravity Bans and Reinstating Access

#158

Post by cyberax »

gruez wrote: post #49
jascha_eng wrote: post #5

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…

>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. This is almost as realistic as "I wish netflix or youtube allowed me to use VLC to watch their content".

> This is almost as realistic as "I wish netflix or youtube allowed me to use VLC to watch their content".

This is exactly what should be happening. There's no reason to limit the client apps for things like _paid_ Netflix or Youtube Premium.

Re: Addressing Antigravity Bans and Reinstating Access

#159

Post by sowbug »

bilalq wrote: post #153
tjoff wrote: post #38

Earlier quoted context omitted.

Use a custom domain and don't use google for email. And if you do use your gmail address just forward it and start to transition to something else. With time everything of importance has been transferred.

This has its own risk factors. If your domain renewal lapses due to credit card expiry or something and you fail to notice, it's catastrophic. This is just not realistic advice for the average person.

You can usually purchase 10 years up front. But then you should set a reminder for every 3 years or so to keep topping up, or else you'll forget how to even sign into the registrar.

You're right that having a vanity domain for your primary email address isn't for the faint of heart. There isn't any realistic advice for the average person because it's not for the average person.

Re: Addressing Antigravity Bans and Reinstating Access

#160

Post by sowbug »

NicuCalcea wrote: post #22
gman83 wrote: 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.

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

This would be a great job for an AI agent. Even better if a few million such agents collectively refused to agree to unconscionable terms.
Post reply on HN