A Serious Breach of Developer Trust and Stability
discuss.ai.google.dev
A Serious Breach of Developer Trust and Stability
1–5 of 5 posts
Re: A Serious Breach of Developer Trust and Stability
#2Re: A Serious Breach of Developer Trust and Stability
#3The current HN link is to page 3 of that discussion, of which I assume the highlighted comment is from this user who provides a possible reason for that redirection:
> It literally didn`t handhold and gave critical honest feedback, even under wrong assumptions. Where all other models were just parroting what they thought the user wants to hear.
Re: A Serious Breach of Developer Trust and Stability
#4The OP of the thread is pointing out that Google's "gemini-2.5-pro-preview-03-25" model was "suddenly and silently" redirecting to "gemini-2.5-pro-preview-05-06", confusing and frustrating "developers, benchmark maintainers, and researchers" who thought they were using one model but were actually being served another. The current HN link is to page 3 of that discussion, of which I assume the highlighted comment is fr…
Re: A Serious Breach of Developer Trust and Stability
#5The OP of the thread is pointing out that Google's "gemini-2.5-pro-preview-03-25" model was "suddenly and silently" redirecting to "gemini-2.5-pro-preview-05-06", confusing and frustrating "developers, benchmark maintainers, and researchers" who thought they were using one model but were actually being served another. The current HN link is to page 3 of that discussion, of which I assume the highlighted comment is fr…
Sorry, I wasn't aware the page parameter when pasting the link so don't read anything into that, I have not personally posted in that thread. But I strongly support H_Express in his case that dated models should not suddenly be redirected to another endpoint
I do enjoy seeing a Google page load about 30 scripts from AWS Cloudfront, though :)