alt Hacker NewsYou can run an entire apartment block off of a single sim card/phone line. The (technical) problem is that you are purchasing an insufficient amount of bandwidth. It goes without saying that a limited bandwidth integrated over a finite service period comes out to a limited amount of data, so the term is misleading.
If google has no obligation to provide the service tier, then they should stop providing it instead of providing it under false terms.
This is like if everyone in a city decided to take baths instead of showers, so the municpal water supply decided to ban baths instead of properly segmenting their service based on usage.
Service providers don't have the right to discriminate what their service is used for.
Replies
> Service providers don't have the right to discriminate what their service is used for.
They frequently do have those rights, though. It's up to the paying customer to either pay for a different tier or move to a competitor who offers the tier they need.
You are never going to get a court to agree that service providers cannot offer different tiers, or segment their offerings.
Lmao no. You cannot use your common sim card for that. It's for an individual and they will cut your service and justifiably so, if they figure out that's what you're using it for.
If you buy a sim card built for that purpose sure, but then you'll be paying...biz prices!
This isn't really that hard to figure out people. So much outrage in comments on this. Self entitlement to the max from people who really haven't lifted a finger to stop the corporate overlords anyway.
I don't think that's an apt metaphor. You bought one general water supply, like an API user. If they sold a "no baths" cheaper option I'd be fine with them banning baths to those customers.
Google's API does let you use any client.
The gemini/antigravity clients are a different (subscription) service. When you reverse engineer the clients and use their internal auth/apis you will typically have very different access patterns to other clients (eg: not using prompt caching), and this is likely showing up in their metrics.
This isn't unusual. A bottomless drink at a restaurant has restrictions: it's for you to drink, not to pass around to others at the table (unless they buy one too). You can't pour it into bottles to take large quantities home, etc. And it's priced accordingly: if sharing/bottling was allowed the price would have to increase.