221–230 of 326 posts
Earlier quoted context omitted.
[flagged]
I did. Specifically the part about "When you enable the Gemini API". This doesn't take into account that people may have had years old forgotten about other services they use.
Earlier quoted context omitted.
> First of all, Google is a shell of the company it used to be. Isn't that squarely at odds with Google's supposed AI prowess? Is the rot really so severe that their advances in AI (including things they've yet to make public) are insufficient to overcome it? Or are the capabilities of Gemini and AI systems in general being oversold?
> Or are the capabilities of Gemini and AI systems in general being oversold? I pretty much sure that if anyone asked Gemini "Is it good idea to retroactively opt-in new services into for old API keys?" it would suggest it's bad idea. Problem is that no one asked.
Earlier quoted context omitted.
I should have said if you recover it in your damages , which every competent attorney will push for.
Legal fees are not something you are usually legally entitled to. Your attorney can push for whatever illegal thing they can think of, it doesn't mean you will get it.
It is not illegal to include legal fees in damages.
Earlier quoted context omitted.
I did. Specifically the part about "When you enable the Gemini API". This doesn't take into account that people may have had years old forgotten about other services they use.
Either way it requires action, there is nothing to presume about that
Earlier quoted context omitted.
Either way it requires action, there is nothing to presume about that
Fair enough. It's a reasonable expectation of someone that enabled Google maps 15 years ago that enables Gemini 6 months not to understand the fundamentals of how Google treats their keys. If it wasn't explained on the enabling Gemini screen, what do you expect the user to do.
Many people wanted to be able to set a spending limit on google cloud account for many years but they were unable to implement anything, always suggesting a workaround by hosting a Cloud Run function which would remove billing from a project via API https://docs.cloud.google.com/billing/docs/how-to/disable-bi...
1. You never know how much a single API request will cost or did cost for the gemini api
2. It takes anywhere between 12-24 hours to tell you how much they will charge you for past aggregate requests
3. No simple way to set limits on payment anywhere in google cloud
4. Either they are charging for the batch api before even returning a result, or their "minimal" thinking mode is burning through 15k tokens for a simple image description task with 5. Incomplete batch requests can't be retrieved if they expire, despite being charged.
6. A truly labyrinthine ui experience that makes modern gacha game developers blush
All I have learned here is to never, ever use a google product.
Earlier quoted context omitted.
I should have said if you recover it in your damages , which every competent attorney will push for.
Legal fees are not something you are usually legally entitled to. Your attorney can push for whatever illegal thing they can think of, it doesn't mean you will get it.
In Google AI Studio, Google documentation encourages to deploy vibecoded apps with an open proxy that allow equivalent AI billing abuse - giving the impression that the API key were secure because it is behind a proxy. Even an app with 0 AI features exposes dollars-per-query video models unless the key is manually scoped. Vulnerable apps (all apps deployed from AI Studio) are easily found by searching Google, Twitter…
[flagged]
Many people wanted to be able to set a spending limit on google cloud account for many years but they were unable to implement anything, always suggesting a workaround by hosting a Cloud Run function which would remove billing from a project via API https://docs.cloud.google.com/billing/docs/how-to/disable-bi...
At scale, distributed API routing shouldn't call accounting transactions, that expands the availability risk surface and adds latency to all valid requests for no reason (other than helping the minority of companies/users who want their product to stop working when it is popular). Distributed “shared nothing” API handling should make usage available to accounting, and the API handling orchestrator should have a hook…