Ask HN: Is it just me or has Gemini enshittified in the last three weeks?
A user of the Gemini Pro plan has reported increased rate-limiting issues over the past few weeks. This change coincides with a new user interface and the introduction of the Gemini 3.5 Preview model. The user expresses concern that compute resources may be shifting away from Gemini, which was previously their preferred model for quick answers.
- ▪The user has been on the Gemini Pro plan for nine months.
- ▪They have noticed a significant increase in rate-limiting since early May.
- ▪The changes seem to align with the release of the Gemini 3.5 Preview model.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Ycombinator |
| Canonical URL | https://news.ycombinator.com/item?id=48269407 |
| Publication time | Mon, 25 May 2026 17:31:34 +0000 |
| Retrieval time | 2026-05-25T17:37:39.277Z |
| Last seen | 2026-05-25T17:37:39.277Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | q3E0M7BVBmiu |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
As someone who's been using the Gemini Pro plan for the past 9 months, I noticed a massive jump in the amount of rate-limiting I'm getting from Gemini since around the beginning of May.It seems to coincide with the updated UI and the release of the Gemini 3.5 Preview model.For the better part of this year, Gemini was my go-to model for answering simple questions quickly. The google search plug-in made it super easy to ask, and it seemed to have endless capacity for research and complex answers on the $20/month plan. Meanwhile, I used Claude very sparingly, and saved most of my Pro plan for Claude Code tokens. Now I find that I'm rate-limited by Gemini harder than Claude.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.