Live data from Hacker News

Google restricting Google AI Pro/Ultra subscribers for using OpenClaw

discuss.ai.google.dev

651–660 of 752 posts

Re: Google restricting Google AI Pro/Ultra subscribers for using OpenClaw

#651
post #547

Earlier quoted context omitted.

More limited features, like lack of model selection, more restricted use of “thinking” models.

>>> a significant % of users are profitable to serve, especially the "chat" users who don't use dev tools and have short context window conversations. > More limited features, like lack of model selection, more restricted use of “thinking” models. Yeah, but... do the "chat" users actually care about any of that? Would they even notice a difference? My point is that, if all you're doing is chat, there's no value in an…

Exactly. The free version is good enough for the vast majority of casual users. According to estimates about 2%-5% of ChatGPT users pay for the service. And people who do pay are looking to get their money's worth.

Re: Google restricting Google AI Pro/Ultra subscribers for using OpenClaw

#652

So purely from a hacker perspective, I'm amused at the whining . Like, a corporation had a weakness you could exploit to get free/cheap thing. Fair game. Then someone shares the exploit with a bunch of script kiddies, they exploit it to the Nth degree, and the company immediately notices and shuts everyone down. Like, my dudes, what did you think was going to happen? You treasure these little tricks, use them cautiou…

> you could exploit to get free/cheap thing

$249/mo isn't cheap

Re: Google restricting Google AI Pro/Ultra subscribers for using OpenClaw

#653

Earlier quoted context omitted.

There certainly are jurisdictions where tv providers are legally required to offer channels a la carte.

Not in the US…

Sure, but we're generally talking here about companies that don't operate only in the US. :)

e.g. the CRTC has regulations around a la carte offerings since the past decade: https://crtc.gc.ca/eng/television/program/alacarte.htm

> TV service providers must offer channels both individually and in packages of up to 10 channels.

Re: Google restricting Google AI Pro/Ultra subscribers for using OpenClaw

#654
post #555

Earlier quoted context omitted.

Firefox is financed by Google and makes them survive (but yes, clearly the only realistic alternative that is not Chromium-based)

They pay to be made the default search engine, true. I'm not aware of there being anything beyond that

[deleted]

Re: Google restricting Google AI Pro/Ultra subscribers for using OpenClaw

#655
post #555

Earlier quoted context omitted.

Firefox is financed by Google and makes them survive (but yes, clearly the only realistic alternative that is not Chromium-based)

They pay to be made the default search engine, true. I'm not aware of there being anything beyond that

The claim that is often repeated in discussions is that Firefox is completely dependent on that money and can't survive without it.

Re: Google restricting Google AI Pro/Ultra subscribers for using OpenClaw

#656

Earlier quoted context omitted.

You make it sound like a significant amount is going to Kreml but I assume the API cost for using Yandex from Kagi is neglectable and only a fraction of that goes to the Russian government. Isn't this more of a symbolic thing to request not cooperating with Russian companies?

For some people it doesn’t matter how negligible. And it’s better to know and make up their own mind.

I think that "it's better to know" only really holds up if the scope / context is also included. To put it in concrete terms, I'd amend your statement like this:

Kagi indirectly funds the Kremlin's regime by paying for Yandex API access.

Re: Google restricting Google AI Pro/Ultra subscribers for using OpenClaw

#657

Earlier quoted context omitted.

Terms of Service that span multiple pages of legalese and require an attorney to parse, for something that is either 'free' or a few $ per month, and can result in loss of service across multiple product lines, AND has binding lopsided arbitration requirements, is not only draconian, it is unconscionable . Look at how messed up this is: Google Attorneys, paid hundreds of $/hour, spending hours and hours putting toget…

> Terms of Service that span multiple pages of legalese and require an attorney to parse, for something that is either 'free' or a few $ per month, and can result in loss of service across multiple product lines, AND has binding lopsided arbitration requirements, is not only draconian, it is unconscionable. In the general case, I broadly agree, but in this specific case: 1. This wasn't a term buried 2/3rds in a 200 p…

Oh, do you mean the terms in Section 6 of the Additional Terms of Service, in which Section 2, four paragraphs before Section 6, exhorts one to read "... carefully, starting with the Universal Terms ...", which is 23 pages long when printed?

'the plans for the destruction of your house were on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying 'Beware of the Leopard'

Re: Google restricting Google AI Pro/Ultra subscribers for using OpenClaw

#658

Earlier quoted context omitted.

How about giving the user a big warning to not do that and then block the account if the user continues. This total blocks are crazy. Especially for people who use their Google account for 20+ years or something.

Nothing new. 10 years ago my (now 20+ year) google account was compromised for a whole 5 minutes. It was used by shady bots, and instantly banned. No warnings, no nothing. Trying to figure out what had happened was a challenge in itself. Getting through to customer support was impossible. 5 years later I tried to get my account opened up, filled out some forms, and by some miracle it was. My biggest takeaway from thi…

Google will happily screw over users with 2FA as well. A few years ago I was out of state for the funeral of someone very close to me. I lost my phone and then needed to get into my email urgently. I didn't have my computer or any other devices with me and no way to get to them. Fortunately I had actually planned ahead for something like this and added my partners phone number as a 2FA method. So I tried to login with that and Google refused!

Google said that because I had more secure 2FA methods configured it wouldn't allow my to use one of the methods that I had very intentionally configured for exactly this scenario. My opinion of the company was already pretty low but I was still shocked that they would simply discard my security settings without any warning or override option. They made one of the worst trips of my life even more miserable. Google hates their own users so much.

Re: Google restricting Google AI Pro/Ultra subscribers for using OpenClaw

#659

So the timeline is basically * User uses Google oauth to integrate their open claw * user gets banned from using Google AI services with no warning * user still gets charged If you go backwards, getting charged for services you can't access is rough. I feel sorry for those who are deeply integrated into Google services or getting banned on their main accounts. It's not a great situation. Also, getting banned without…

> Why did openclaw allow Google anti gravity logins?

There's a good chance the plugin was written by gemini, why did it allow that?

Re: Google restricting Google AI Pro/Ultra subscribers for using OpenClaw

#660
post #580

Earlier quoted context omitted.

There is consensus on r/gemini that the window is a matter of hours now, not 24h. I subscribe to the AI Pro plan. I knew of a published limit of 100 Pro prompts per day, but before this month it seemed they were relaxed about it. I have now started to be rate limited on Pro when nowhere near that quota, due to too many prompts within a short time window (probably due to short prompts and not aggregating my questions)…

I don't know why you rely on some Reddit consensus when you can just open Gemini CLI and enter /stats to get the confirmation that you get 200 Pro requests per 24h, and the counter starts when you do your first request. Unless there is something I'm missing

If it was a daily quota issue, I would have been notified and unable to use more Pro requests until the 24hr period had reset.

This was a temporary rate limit and it told me to try again at a specified time which wasn’t far away. That’s different.

However, it could have been because of a temporary capacity issue. I hope so.

Post reply on HN