It also improves the rush hours by enlarging the time range. Most jobs start at 9am or later, so if kids also started at 9am or later the morning rush hour (for traffic but also public transportation) would be even worse.
School ends at 3pm so that the teachers, who work a 9-5 like you, get two hours after class to grade homework and prepare lessons for the next school day.
I'm sure we're in agreement that, at least in UK, there's been better pubs for 200+ years. I don't know why to go to a chain-pub with some mega-factory beer when the old-local serves a fine bitter from the same county. Am I old?
Yes it's a bit of a generayional shift. In the 2000s when I moved the UK it was all real ale. If you wanted to drink a pinecone of an IPA the Utobeer option above seemed like the only option.
But I'm a millenial. Liking IPAs is a millennial trope and younger people like less intense flavours.
Friend, this reads like that situation where your paycheck prevents you from seeing clearly - I forget the exact quote. Sam doesn't play a straight game and neither does the administration - there are more than a few examples.
Re: Reading,
I don't see any xAI names on the list (currently 643) and only Google and OpenAI are selectable company options. And this page on HN is only calling out xAI.
They are very much not a part of the initiative. Their involvement is and will be non-existent. Unless of course, you want their lay staff to make some noise?
Really? I make multiple GCP projects per app. One project for the (eg) Maps API, one for Drive, one for Mail, one for $THING. Internal corp-services might have one project with a few APIs enabled - but for the client-app that we sell, there are many projects with one or two APIs enabled only.
If you ever have to enable public OAuth on such a project, you'll need to provide a list of all the API projects in use with the application, and Google Trust and Safety will pressure you to merge them together into a single GCP project. I've been through it.
You can do what you're describing but it's not the model Google is expecting you to use, and you shouldn't have to do that.
It seems what happened here is that some extremely overzealous PM, probably fueled by Google's insane push to maximize Gemini's usage, decided that the Gemini API on GCP should be default enabled to make it easier for people to deploy, either being unaware or intentionally overlooking the obvious security implications of doing so. It's a huge mistake.
Why would they encourage more resource use, increasing their cost?
Gemini should have had it's own API key separate from their traditionally public facing API IDs (which they call keys) and API keys should default to being tightly scoped to their use case rather than being unrestricted.
Who cares if you have three API keys for three services.
Quite frankly putting any API information in things like url params or client side code just doesn't sit right with me. It breaks the norm in a way that could be, and is now security concern.
It's like when management does something stupid and then engineering works overtime to keeps the system working. Of course management learns nothing and all outside observers don't even notice something went wrong.
There is a limit to how much engineers working overtime can do to offset management stupidity and when you reach the limit the bottom falls out. Of course then everybody blames the engineers...
I'm certain there is a way to verify age without compromise of privacy or identity. I'm sure it's possible to build some oAuth like flow that could allow sites to verify both human-ness and age. The systems and corporations that gate that MUST (in the RFC sense) be separate from the systems and corporations that want the verification.
Do we need laws to make this happen? What methods can be used to aid adoption? Do site operators really want to know the humanness and ages or are those just masks on adding more surveillance?
reply