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

Let me guess you have to be an Australian citizen (inmate?) to have the right to sue and then you won't have standing?

You have to be onshore to get the case in front of Admnistrative Tribunal (ACT)

There is a difference between banned and you can't just pump it into the next water stream.

I hope Google has a database with the creation timestamp for every API key they issued.

You can see the creation date even on the GCloud dashboard. But this information isn't helpful in recovering from this issue, if they're interested in recovering correctly, because there's no guarantee that even keys created before the launch of Gemini didn't have Gemini access added to the keys intentionally. There are also likely public keys created after the launch of Gemini that also erroneously received the Gemini grant. The key creation date is ultimately useless; what it comes down to is whether the key's usage is intentional or malicious, which is impossible for Google to determine without involving the customer.

If there's one thing Google is good at, it's logging.

I think Google has a database with everything. EVERYTHING.

They should limit the new features to new API keys that explicitly opt-in instead of fucking over every user who trusted their previous documentation that these keys are public information.

Isn't it standard practice to harden permissions on API keys? Like, if I were a bootstrapped startup maybe I'd take shortcuts and let an API key have a * permission but not for anything that could rack up thousands of dollars in bills for the customer. But at googles scale that just seems irresponsible.

LRO because the bridge has to forward the real frames. TSO because it’s fairly useless now.

The bridge driver gained features (vlan filtering) not performance.

You're not supposed to skip to the conclusion.

What conclusion? This is the Always Sunny corkboard.

that's how you should be reading scientific journals

The post is about a microcontroller that sips a fraction of a Watt under sane conditions. Cooling its CPU cores is not a problem for real-world applications. You have to bypass the internal voltage regulator crank up the voltage even more before heat becomes an issue.

This some harmless stupid fun.

They're really useful for tugs and other specialty applications that need the ability to have differential thrust in arbitary directions with lots of thrust at low speed, but loose to Azipods on faster and larger ships.

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

Search: