Hacker News new | ask | show | jobs
by _drg9 138 days ago
The quota we needed increased far beyond the usual was the YouTube API. The startup was a media editing and publishing tool, with a feature to upload videos to YouTube on your behalf. Uploading a video requires a ton of quota, which they gave us.

Regardless, dropping all quotas to 0 effectively killed our GCP account.

1 comments

Interesting. I guess we’ve learned an important lesson in not building businesses around APIs that don’t have an SLA…
That was just a feature of the product to be helpful. Not a core function at all.
If you werent willing to pay for an SLA, and they clearly werent going to offer one to you… why is it surprising if literally no promises were made in writing?

Why would they intentionally lose money on your private commercial activity without even that?

> werent willing to pay for an SLA

According to who?

> no promises were made in writing

Most big businesses won't promise anything. That doesn't make their actions reasonable.

> Why would they intentionally lose money

You made this up.

Also if they were losing money on some feature, they could change the quota for just that feature.

Are you confused?

Clearly I was not asking for random role play on how another HN user may answer a direct question.

I'm calling out your "questions" as containing a bunch of unsupported claims about the situation on top of weird assumptions about how things have to work. It was not an answer, and your questions as written don't deserve answers.
How many services have meaningful SLAs for extreme downtime?

Github and (parts of) AWS will give you a small discount at 0.1% downtime, a bigger discount at 1% downtime, and AWS will refund the whole month for 5% downtime. But beyond that they don't care. If a particular customer gets no service at all then their entire $0 gets refunded and that's it.