logankilpatrick

in the core Gemini API, we have a huge error code refactor to make sure it is as intuitive as humanly possible.

We made the bet 2 years ago to build AI Studio on top of the Google Cloud infra. One of the real challenges is that Google is extremely global, we support devs in hundreds of countries with dozens of different billing methods and the like. I wish the problem space was simple but on the first day I joined Google we kicked off the efforts to make sure we could bring billing into AI Studio, so January cannot come soon enough : )

The Gemini app UI has gotten much better in the last few months and a huge amount of other work underway to make it even better!

if I can be of help, pls lmk, Lkilpatrick@google.com

okay fine updated my bio : )

First off, apologies for the bad first impression, the team is pushing super hard to make sure it is easy to access these models.

- On permission issue, not sure I follow the flow that got you there, pls email me more details if you are able too and happy to debug: Lkilpatrick@google.com

- On overall friction for billing: we are working on a new billing experience built right into AI Studio that will make it super easy to add a CC and go build. This will also come along with things like hard billing caps and such. The expected ETA for global rollout is January!

Could have made it 500, but who has time for that :)

We are working on fixing this and showing the critical ones in AIS. I agree it is crazy there is 700+ items here. Real pain in the neck to deal with.

This is correct, "When you activate a Cloud Billing account, all use of Gemini API and Google AI Studio is a "Paid Service" with respect to how Google Uses Your Data, even when using Services that are offered free of charge, such as Google AI Studio and unpaid quota of Gemini API."

we will have a dashboard in AI Studio very soon! Then will work to drive down delay.

you can do so with the AI SDK from Vercel, open router, etc or just sending raw http requests

We added it to the docs. The downside of the OAI compat endpoint is we have to design the API twice, once for our API, then once through the OAI compat layer which makes it slower sometimes to have certain features, especially if we diverge at all.

This is documented for AI Studio here: https://ai.google.dev/gemini-api/docs/openai#thinking

Pls ping me if you run into any production issues, will raise right away to the team. We have massive at scale products operating on AI Studio, so we are set up to ensure stability.

The startup credits are fully compatible with AI Studio, they are not specific to Vertex.

We are working hard to improve this across ai.google.dev (Gemini API), Hang tight!

Huge win for developers!

Good news: We are back up and everything should be working as expected. We are monitoring closely to ensure you have full service. We plan to publish a public postmortem to explain what happened and how we'll prevent similar issues in the future.

Apologies for the downtime ♥

Really apologize for the disruption, unrelated to the events of this week and also not related to the voice rollout. The team is working fast on a fix! Hang tight.

Unrelated, just the normal challenges of running a service with 100M weekly active users. Sorry for the disruption and hang tight!

Apologies for the disruption, would love to hear feedback in the meantime on the Assistants API and how you are liking it!

Hey folks! The team is aware and working on a fix. Should be resolved shortly, you can follow along on: https://status.openai.com/incidents/n254wyd7nml7

As I mentioned in the Reddit thread, the more examples and shared links the better, general feedback is good, but concrete examples work best!

PSA: we will continue to support Codex access via our Researcher Access Program. If you are not already part of it, we encourage you to apply in order to maintain access to Codex. Looking forward to seeing what you are working on!

https://openai.com/form/researcher-access-program

Please put them in touch with me if possible. RelationalAI has similar GC issues which they are the core Julia developers are working hard to resolve.

I have also seen zero postings for Julia roles in cyber security companies so it is likely that they aren't tapping into the community which is why they can't find people.

The fact that Chris R and the whole SciML ecosystem are using / building on it. Lots of resources going into it and usage in real world places like Pfizer and Moderna.

Look at GenieCloud, they are essentially building the Django ecosystem in Julia, it will be huge if they are successful.

When I worked at Beacon biosignals briefly in 2020, they had Simon Danish (the creator of Makie there full time deploying plots/makie in the browser).

One point 2, you should check out Julius Tech which is bridging the multi language future using Julia through their graph computing tool. Other companies like RelationalAI are building on top of Julia but also have their own new language called Rel.

I am interested to hear if folks think a 2.0 release would make Julia more appealing.

Wow, who would have thought?