Hacker Newsnew | past | comments | ask | show | jobs | submit | totaa's commentslogin

Google Vertex



> Long-running tasks like batch mode completions and agent sessions may incur overages beyond your project spend cap.

> Billing data processing times can be delayed in AI Studio, up to around 10 minutes. You may experience overages beyond your project cap if billing data hasn't processed before more charges are accrued.

https://ai.google.dev/gemini-api/docs/billing#project-spend-...

That's a soft cap, not a hard cap


I spent two hours the other day trying to figure out how to manage spend on gcp, i gave up and used openrouter and cloudflare.


AI studio added it recently, Vertex not.


the question is will we experience resource constraints before we get there? what if the step up to post-scarcity is gated by a compute level just out of our reach?


human ingenuity will solve this


Or we'll have ecological collapse.


NFTs will solve this


any extensions / third-party tools to visualise this?


surely openvpn being pre-installed on most routers means it's provided to an significant portion?


It is the server that you connect to that is covered by this amendment; they don't care how you connect.


Sure, but openvpn itself doesn't become a "service" just because of that.


i don't think so, it is not provided as a service. if you provide vpn service people can connect to from their router then you need to do age verification before giving them a key/password to connect to the server


brainfuck


I implemented a graph database for my agentic project in postgres. Not top-tier query performance but made an MVP work!


can you share your workflow?


more can lead to smarter in the short term.

brute force


Gemma 3n E4B has been crazy good for me - fine tune running on Google Cloud Run via Ollama, completely avoiding token based pricing at the cost of throughput limitations


What kind of applications are you using it for?


congrats on the first blog post, been using Go+Templ+HTMX when implementing my first startup

I think at least some of these issues can be avoided with a different UI/UX to avoid passing temporal/unsaved data between screens.

looking forward to the next instalment!


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: