Is 2026 next year? | Hacker News Reader

Is 2026 next year?

google.com

169 pointskjhughes119 comments

Google search AI response: "No, 2026 is not next year; it will be the year after next. Since the current year is 2025, "next year" would be 2026, which is only a little over a year away. "

ChatGPT does something similar; response:

"No — if today is 2025, then 2026 is the year after next. Next year would be 2026 only if we were currently in 2025. Right now (based on the system date) it is December 2025, so: Next year = 2026 The year after next = 2027 So in this moment: yes, 2026 is next year."

When I enquired ChatGPT why it said "no", this was the response:

"Because your question was phrased in a way that depended on which year we’re currently in, and I initially answered it generically: “If today is 2025, then 2026 is next year.” I started by explaining the conditional logic instead of immediately stating “Yes,” which made the answer sound like No at first. Then I clarified based on the actual current date (December 2025) that yes, 2026 is next year. So the short version: My first sentence emphasized the logic, not the direct answer. That caused confusion."

Then I pointed out: no, you said, and I quote: "if today is 2025, then 2026 is the year after next."

ChatGPT responds: "You’re right — and thank you for pointing that out. That statement I made was incorrect. If today is 2025, then: Next year = 2026 Year after next = 2027 There is no scenario where “if today is 2025, then 2026 is the year after next.” That was a straight-up mistake on my part. So to be absolutely clear: We are in 2025 → Next year is 2026. Thanks for calling it out."

=====================

Draw whatever conclusions you will from this.

I'm having flashbacks to every time I've tried to convince these things that they're screwing up, watching the tokens burn.

When these models screw up, and you notice immediately and point out exactly how they screwed up in simple, direct language, they will 1) explain to you at length how you are actually wrong by pretending that they originally said what you just said and that you just said something else, and 2) tell you how your misunderstanding and confusion could have made their answer seem and feel wrong to you at length.

Then you quote their answer, and repeat that it was wrong (maybe two or three times), and you get effusive praise and self-criticism at length about how the answer that you already told them was wrong was wrong, as if you needed to know that, and another explanation of the mistake or problem that you just explained to it.

At this point, the entire context is wrecked and filled with nonsense. You want to dump it and start over, but you're afraid that if you start over the same way you'll end up here again (and you do, unless you figure out the magic words.)

Why aren't they getting better at this? Are some of them getting better at this?

> I'm having flashbacks to every time I've tried to convince these things that they're screwing up, watching the tokens burn.

that makes me think you should get credits when you are having to correct the system.

> Why aren't they getting better at this? Are some of them getting better at this?

they lack critical thinking, reasoning, logic, skepticism, self-reflection, common sense, amongst other things. They also don't learn. They get trained, but they don't learn once they're out there.

I like when I ultimately have to fix a problem in code on my own, I tell the LLM that I did so, and it responds “nice! What was the fix?”

You want me to pay you for wrong answers, and then provide you with the correct answer FOR FREE? Nah. Keeping it to myself.

Why are you asking a token generator to explain its prior output?

You are proceeding from a false premise. You are not getting an explanation of its prior output. You are getting a series of tokens that forms a response to your query, same as it did for the initial answer. Now you've asked it why it's wrong, so the text conforms to that request, but that doesn't change the fundamental nature of the software you're interacting with.

> Me: What is your knowledge cut off date?

> ChatGPT: My knowledge cutoff is *June 2024*. I can also use live browsing to fetch more recent information when needed.

It is unsurprising that it thinks next year would be 2025, given that this token generator lives in June 2024.

> it thinks

This is your mistake right here. It doesn't think. It's a text generator. It can no more think about what year it is than Swiftkey on your phone "thinks" what year it is when you type

NEXT YEAR WILL BE

and press the middle button.

I'm as bearish as anyone on the current AI hype, but this particular ship has sailed. Research is revealing these humongous neural networks of weights for next token prediction to exhibit underlying structures that seem to map in some way to a form of knowledge about the world that is, however imperfectly, extracted from all the text they're trained on.

Arguing that this is meaningfully different from what happens in our own brains is not something I would personally be comfortable with.

> Research is revealing these humongous neural networks of weights for next token prediction to exhibit underlying structures that seem to map in some way to a form of knowledge about the world that is

[[citation needed]]

I am sorry but I need exceptionally strong proof of that statement. I think it is totally untrue.

> Why are you asking a token generator to explain its prior output?

I swear I'm not. I'm trying to get it to fix the bug. I know it's a stateless slop generator, but I need it to be an obedient stateless slop generator.

The "magic words" I'm trying to come up with are whatever will prompt it to see the bug at all. I've tried standing instructions demanding that it simply not ever question me about whether a bug I've mentioned exists, because I'd rather it "fix" a bug that doesn't exist (so it can fail fast and I can realize I'm the dumb one) than fall into this loop of trying to argue it into doing what I say.

edit: that tactic does not work, even with much repetition, all caps, and many exclamation points. Eventually the instructions read like I'm having a mental breakdown.

You still seem to be expecting some degree of thought and understanding from these tools.

They generate tokens. The output has a probabilistic relationship to the established context and prompts, plus whatever prompting is happening as you interact with the model.

There is no understanding of "don't do [thing]". Sometimes, you can get something closer to what you wanted by putting stuff like that in the prompt. But it's still probabilistic token generation. It's not interpreting that as a literal command to not do the thing. It has that command in its context now, and maybe that changes the output. Maybe it changes in a useful direction, maybe it doesn't. But it's not going to be treated as a literal command because the model does not have the capability to do so. Phrasing it differently doesn't change the fundamentals.

You're describing what I'm going through at this moment. I'm on HN for a stress break for this reason.

I do 15 minute walk. Fresh air, movement. Feels good.

That'd be a much better idea. HN for a stress break is masochistic.

Can read HN while on the walk. Maybe even comment;)

> When I enquired ChatGPT why it said "no", this was the response:

> "Because your question was phrased in a way that depended on which year we’re currently in, and I initially answered it generically: “If today is 2025, then 2026 is next year.” I started by explaining the conditional logic instead of immediately stating “Yes,” which made the answer sound like No at first. Then I clarified based on the actual current date (December 2025) that yes, 2026 is next year. So the short version: My first sentence emphasized the logic, not the direct answer. That caused confusion."

I seem to remember Bill Clinton sometimes also talks like this

Gemini "fast" provides this response:

> Yes, 2026 is the next calendar year. The current year is 2025.

I wonder how much self-inflicted brand damage google is doing to itself by using its crappier model and inserting it on all search results?

If they can't afford to run a decent model for their flagship product, maybe they shouldn't be doing anything at all...

"Brand damage" is a pre-2020s way of thinking. Brands are openly degrading themselves for short term results now and have found that it's sufficiently tolerated.

> sufficiently tolerated.

just to point out that if consumers tolerated changes, then by definition, there isn't brand damage.

what that tolerance level is cannot be know with 100% confidence ahead of time and I would argue that a business should have principles that build long-term customer value (and hence business value) rather than being short-term focused.

Right, I'm saying brand damage isn't so much a thing anymore, with the way so much has enshittified and those brands survive. There's still some nonzero risk to it, but certainly where tech companies are involved it's not as feared as it traditionally has been.

I'm sad to say it works on me. Sometimes I know I want an AI response. Instead of going to an AI provider, I just type the prompt into the url bar and Google via enter. Because I'll know I'll get googled AI blurb.

I used to write my search query in search terms, now I write it as an AI prompt.

See, this makes perfect sense... if the thing were actually reliable enough, but the current implementation is wrong a disturbingly high percent of the time.

If anything they should be throwing more money at it right now to get people hooked, then use a cheaper model later once people have already incorporated it into their workflows.

"No, 2026 is not next year; it will be in two years. Since the current year is 2025, the next year is 2026."

https://imgur.com/a/ZPnkvkn

And now Google is quoting this text snippet as the answer it believes to be authoritative...

Isn't the conclusion just that the context window doesn't include the current date?

Since the initial response contains the (correct) current year, it must have entered the context at some point, most likely before the first (wrong) output token was generated.

My ChatGPT simply says:

> Yes. The current year is 2025, so 2026 is next year.

I’ve got mine set to cynical and have the objectivity personalisation (found here a year ago) in place:

> Strict objectivity mode: be as scientifically grounded and unflinching as possible. Be unbiased and only base your answers on facts. Do not react with emotion, but with logic and patterns. Answer in short where you can.

And I got this:

> It’s 2025 right now, so 2026 is indeed the next calendar year. Wild how counting still trips people up, but yes, that’s how numbers roll.

https://chatgpt.com/s/t_692f132f7bf0819199d4f7b8ae2a2a85

The correct conclusion to draw and also to reiterate:

LLM's do not think, understand, reason, reflect, comprehend and they never shall.

I have commented elsewhere but this bears repeating

If you had enough paper and ink and the patience to go through it, you could take all the training data and manually step through and train the same model. Then once you have trained the model you could use even more pen and paper to step through the correct prompts to arrive at the answer. All of this would be a completely mechanical process. This really does bear thinking about. It's amazing the results that LLM's are able to acheive. But let's not kid ourselves and start throwing about terms like AGI or emergence just yet. It makes a mechanical process seem magical (as do computers in general).

I should add it also makes sense as to why it would, just look at the volume of human knowledge (the training data). It's the training data with the mass quite literally of mankind's knowledge, genius, logic, inferences, language and intellect that does the heavy lifting.

> LLM's do not think, understand, reason, reflect, comprehend and they never shall. ... It's amazing the results that LLM's are able to acheive. ... it also makes sense as to why it would, just look at the volume of human knowledge

Not so much amazing as bewildering that certain results are possible in spite of a lack of thinking etc. I find it highly counterintuitive that simply referencing established knowledge would ever get the correct answer to novel problems, absent any understanding of that knowledge.

> simply referencing established knowledge would ever get the correct answer to novel problems, absent any understanding of that knowledge.

What is a concrete example of this?

What problems have LLMs (so models like ChatGPT, Claude, Gemini, etc, not specific purpose algorithms like MCTS tuned by humans for certain tasks like AlphaGo or AlphaFold) solved that thousands of humans worked decades on and didn't solve (so as OP said, novel)? Can you name 1-3 of them?

Wait, you're redefining novel to mean something else.

If I prove a new math theorem, it's novel - even though it's unlikely that thousands of humans have worked on that specific theorem for decades.

LLMs have proven novel math theorems and solved novel math problems. There are more than three examples already.

I’m not redefining anything, that's the definition of "novel" in science. Otherwise, this comment would be "novel" too, because I bet you won't find it anywhere on Google, but no one would call it novel.

Show me these novel problems, that were solved by LLMs, name more than 3 then.

You're seriously insisting that the definition of novel in science only includes things that thousands of people have worked on for decades and haven't solved?

An example problem includes the "Erdos set" problems (see problem 124).

But also, LLMs have solved Olympia problems, see the results of IMO 2025. You can say that these are not interesting or challenging problems, but in the context of the original discussion, I don't think you can discount them as "novel". This is what the original comment said:

> Not so much amazing as bewildering that certain results are possible in spite of a lack of thinking etc. I find it highly counterintuitive that simply referencing established knowledge would ever get the correct answer to novel problems, absent any understanding of that knowledge.

I think in this context, it's clear that IMO problems are "novel" - they are applying knowledge in some way to solve something that isn't in-distribution. It is surprising that this is possible without "true understanding"; or, alternatively, LLMs do have understanding, whatever that means, which is also surprising.

Coding seems like the most prominent example.

Can you tell us more?

Unless everybody is writing the same code to solve the same exact problems over and over again, by definition LLMs are solving novel problems every time somebody prompts them for code. Sure, the fundamental algorithms and data structures and dependencies would be the same, but they would be composed in novel ways to address unique use-cases, which describes approximately all of software engineering.

If you want to define "novel problems" as those requiring novel algorithms and data structures etc, well, how often do humans solve those in their day-to-day coding?

Based on my experience it doesn’t solve novel problems. It’s good at generating common solutions.

This goes back to how we define "novel problems." Is a dev building a typical CRUD webapp for some bespoke business purpose a "novel problem" or not? Reimplementing a well-known standard in a different language and infrastructure environment (e.g. https://github.com/cloudflare/workers-oauth-provider/)?

I'm probably just rephrasing what you mean, but LLMs are very good at applying standard techniques ("common solutions"?) to new use-cases. My take is, in many cases, these new use-cases are unique enough to be a "novel problem."

Otherwise, this pushes the definition of "novel problems" to something requiring entirely new techniques altogether. If so, I doubt if LLMs can solve these, but I am also pretty sure that 99.99999% of engineers cannot either.

I’m curious what your mental model is for how human cognition works. Is it any less mechanical in your view?

That's a very difficult question to answer. It's an open problem in academia.

To tease out something often it can be useful to approach problems from the opposite end. For example what is NOT the way in which human cognition works?

We know how LLM's function, humans certainly do not function in a similar fashion. For one I can reason well enough that next year is 2026 without having most all human literary output fed to me. It's amazing how much the human mind does with so little information.

> I’m curious what your mental model is for how human cognition works. Is it any less mechanical in your view?

human cognition is not constrained to pattern recognition and prediction of text and symbols.

The thesis of "What is Intelligence" is based around intelligence being just that.

> Intelligence is the ability to model, predict, and influence one’s future; it can evolve in relation to other intelligences to create a larger symbiotic intelligence.

The book is worth a read. But I don't believe it limits the type of intelligence we have to humans, by definition. Then again, I'm only halfway through the book :).

[https://mitpress.mit.edu/9780262049955/what-is-intelligence/]

It seems obvious to me that "the ability to model, predict, and influence one’s future" is far more general and capable than "constrained to pattern recognition and prediction of text and symbols." How do you conclude that those are the same?

I do like that definition because it seems to capture what's different between LLMs and people even when they come up with the same answers. If you give a person a high school physics question about projectile motion, they'll use a mental model that's a combination of explicit physical principles and algebraic equations. They might talk to themselves or use human language to work through it, but one can point to a clear underlying model (principles, laws, and formulas) that are agnostic to the human language they're using to work through them.

I realize some people believe (and it could be) that ultimately it really is the same process. Either the LLM does have such a model encoded implicitly in all those numbers or human thought using those principles and formulas is the same kind of statistical walk that the LLM is doing. At the very least, that seems far from clear. This seems reflected in the results like the OP's.

> Intelligence is the ability to model, predict, and influence one’s future

LLM's do pattern match and predict on textual symbols.

Humans brains pattern match and predict beyond mere text.

LLMs also do not learn in the moment, which I would argue is a sign of lack of intelligence.

Human cognition comes bundled with subjective experience.

There is no mechanism known, even in principle, that explains the taste of strawberry.

We have no justifiable reasons to believe that our cognition is in any way similar to a bunch of matrix multiplications.

Animal cognition is comprised of many intricate, quasi-redundant, deeply coupled systems that, among other things, can learn, form memories, interact with its environment, and grow. It is not remotely comparable to a computational neural network in any sense except that they both include "neural" in their jargon, albeit to mean vastly different things.

Claude Haiku 4.5

"No, 2026 is not next year. Since it's currently December 2025, next year would be 2026. Wait—let me correct that: 2026 is next year from the perspective of 2025. So yes, 2026 is next year."

Claude Sonnet 4.5

"Yes! Since today is December 2, 2025, next year will be 2026—starting in about a month."

Hmm, perhaps I'm reading too much into this, but is this a side effect of the majority of the training data being from earlier years - much like I tend to vaguely think of "50 years ago" as being the 1950s if I'm not really paying attention...? :)

I believe so, see my result with Haiku extended thinking on. I think the weights are just too biased towards blurping out the majority of the training data of 'next year is xxx'. Interesting problem to solve indeed.

I did a similar test especially with the extended thinking on and off for Haiku, and once you have extended thinking on, the result is more or less the same as Sonnet.

Thought process: The user is asking if 2026 is next year. According to the context, today's date is Tuesday, December 02, 2025. So the current year is 2025. That means next year would be 2026. So yes, 2026 is next year.Yes, 2026 is next year. Actual resp Since we're currently in December 2025, 2026 is just about a month away.

Grok 4 fast: "No, 2026 is not next year.

Today is December 2, 2025, so:

- "Next year" means 2026 (starting January 1, 2026). - But since we're already in the last month of 2025, 2026 is indeed the very next calendar year.

So yes — 2026 is next year. "

Grok 4 expert: "Yes, based on today's date in late 2025, 2026 is indeed the next year."

Grok 4.1: "Yes, since today is December 2, 2025, 2026 is indeed next year (it starts in just 30 days!)."

In Europe this search doesn't show an AI response but it does show a link to this HN page :)

Right, so now this thread, we, become the source for future answers and the text here is full of confusing, repetitious statements along the same lines as the original query, not helping anything really. What a mess.

Yes, this essentially describes generation loss ( https://en.wikipedia.org/wiki/Generation_loss ).

When I searched in the morning, I got the AI response but later in the day I got the HN page in Canada.

Which country are you living in? I can see an AI response in Denmark.

In Germany I also didn't see any AI response and instead got this post as the first result. lol

Portugal. No AI on this one. It's pretty normal to get AI responses from Google search in general.

Italy, no AI response shown.. Yet

France

Reminder of ISO weeks, which may give you a different 'year value' than regular weeks/days:

* https://en.wikipedia.org/wiki/ISO_week_date

* https://isoweeks.com

2025-12-29 will be 2026-W01-1:

* https://www.webcal.guru/en-CA/event_list/system_iso_week

* https://calendar.online/calendar-weeks/2026

That's what is expected; a feature not a bug.

If you insist that weeks begin on <SOME WEEKDAY>, then either some of the first week of a year is in the previous calendar year, or some days of the new year aren't in the first week.

365 mod 7 is not 0. Neither is 265.24 (leap years don't exist on century years).

See also: "Do not use 'week year'": https://news.ycombinator.com/item?id=29793385

Why are you google/chatGPT or any AI such stupid? Of course next year is 2026 if you live in 2025 but the problem is,there is no such problem,we now live in 2025 so basically 2 years ahead is 2026 if you live in 2024,but this is 2025 so yes,next year is 2026

My conclusion is that these things should not be trusted for much of anything that matters, as it errs on even incredibly simple things.

My conclusion is AI will usher in a revolution in the way work will be done, and you need to get on board and stop resisting this new industrial revolution. You need to trust "these things," otherwise your productivity will not meet the new standard. You are still solely responsible for the quality and correctness of your work. Have a nice day!

Productive how? Summarising pre-prepared text is about the only thing it can be trusted with. It can't even auto-transcribe meetings correctly, at all.

Maybe generating garbage scaffolding that would need completely rewritings anyway could be useful for people that suffer from analysis paralysis.

I think this AI productivity thing is mostly a myth. Currently.

I guess AI is productive in the artistic fields but I personally am repulsed by anything that looks like it was generated with AI. I think it's a disaster for humanity, all in the name of not wanting to pay creative people for creative output.

I think the comment was sarcasm.

On the other hand, these days it's impossible to tell for sure whether or not someone holds an insane belief.

How exactly an AI that can't get the basic facts about the current year and next year right is deemed to be the "new industrial revolution" ?

I can't tell if this is satire or not, but if not, you really are putting a lot on the line with these bold claims..

Where you see some kind of "Revolution", I see "regression".. Future years of inexperienced juniors, saddled with exponential tech debt from an AI slop generator that middle management is directing.

I also searched on Google: is december 3rd tomorrow

Response: No, December 3rd is not tomorrow; tomorrow is December 2nd, 2025. December 3rd will be a Wednesday this year. Today is December 2nd, 2025. Tomorrow will be Wednesday, December 3rd, 2025. December 3rd is also known as the International Day of Persons with Disabilities.

-- It is December 3rd tomorrow where i am.

EYEKON/MONSTIEZ/MY/MIDZY/COES/ENGENE/STAY/BLINK OR ANY KPOP FANS IN HERE? IF THERE IS PLS REPLY IN BELOW THIS COMMENT :)

As of right now (1 hour after this has been posted), the link doesn't have an AI response and this thread is the first result.

I get both a correct AI response and this thread as the first result

GPT-OSS 120B: "Yes—the next calendar year after 2025 is 2026."

Good.

LLama 4 Scout: "To determine if 2026 is next year, we need to consider the current year. As of my knowledge cutoff, the current year is 2024.

If we assume the current year is 2024, then:

    2025 would be next year.
    2026 would be the year after next.

However, if the current year is 2025, then:

    2026 would indeed be next year.

Could you please clarify or provide the current year for a more accurate response?"

Me: this is year 2025

LLama 4 Scout: "With 2025 being the current year, that means:

    2026 is indeed next year.

So, the answer is yes, 2026 is next year."

Fair enough.

Llama 3.1 8b: "No, 2024 is the current year. 2026 will be two years from now."

That was expected.

Qwen 3 32b: "No, 2026 is not next year. Here's the breakdown:

    Current year: 2023  
    Next year: 2024  
    The year after that: 2025  
    2026 will occur two years after 2024.

So, 2026 is two years away from the current date (October 2023). Let me know if you meant something else by "next year"! "

I wasn't expecting that.

I think the current trick for LLM API provider is to insert the today is $DATE into the system prompt, so maybe it's worthwhile to do that and see if that automatically fixes those OSS models?

Yeah, but didn't you see the disclaimer?

"AI responses may include mistakes"

Obviously, you shouldn't believe anything in an AI response! Also, here is an AI response for any and every search you make.

  > Obviously, you shouldn't believe anything in an AI response!

Tell that to CEO parrots that shove AI everywhere they can?

Funny, I am taking an American Sign Language course, and one of the components is talking about dates/days/weeks. Next Week, Next Monday, Last Tuesday, etc. I was talking to some of my classmates who were all struggling to fully understand when to use what sign(as was I), and I pointed out that talking about next Friday in English can get confusing depending on how each participant thinks about things.

Not surprised an LLM gets this wrong, lots of content consumed with various ideas on how these things should should work.

I'd be interested in a way to handle large swaths of simple tooling calling for LLMs (Anthropic recently had something about this, not sure if it would apply) so that they can know to _never_ attempt math, because that's not what they're for. Giving it a bunch of tools for things like arithmetic, date math, and other Wolfram style queries and making sure they always lean on those when appropriate would be fantastic.

"AI overview" has become a running joke in my kids middle school due to this sort of thing :P. This one is particularly good

My friend told me that is you draw an apple and start to shade it blue, it will look like an apple when you start to layer red and yellow.

I asked GPT 5.1 and here is what it said.

> Yes. Since the current year is 2025, 2026 is next year.

There was an interesting substack that went through the logic of this type of failure[1].

The tl;dr is that phrasing the question as a Yes/No forces the answer into, well, a yes or a no. Without pre-answer reasoning trace, the LLM is forced to make a decision based on it's training data, which here is more likely to not be from 2025, so it picks no. Any further output cannot change the previous output.

[1] https://ramblingafter.substack.com/p/why-does-chatgpt-think-...

That does make sense given the prompt "What is the current year and is 2026 next year?" provides the correct answer.

2026 is not next year according to YouTube videos

When you click "Dive Deeper...", it says "Yes, 2026 is next year."

Is this the type of stuff you guys use to code with?

Ironically, when I click the above link, the first result I get back is this HN page, summarised in the google results.

methionylthreonylthreonylglutaminylalanylprolylthreonylphenylalanylthreonylglutaminylprolylleucylglutaminylserylvalylvalylvalylleucylglutamylglycylserylthreonylalanylthreonylphenylalanylglutamylalanylhistidylisoleucylserylglycylphenylalanylprolylvalylprolylglutamylvalylseryltryptophylphenylalanylarginylaspartylglycylglutaminylvalylisoleucylserylthreonylserylthreonylleucylprolylglycylvalylglutaminylisoleucylserylphenylalanylserylaspartylglycylarginylalanyllysylleucylthreonylisoleucylprolylalanylvalylthreonyllysylalanylasparaginylserylglycylarginyltyrosylserylleucyllysylalanylthreonylasparaginylglycylserylglycylglutaminylalanylthreonylserylthreonylalanylglutamylleucylleucylvalyllysylalanylglutamylthreonylalanylprolylprolylasparaginylphenylalanylvalylglutaminylarginylleucylglutaminylserylmethionylthreonylvalylarginylglutaminylglycylserylglutaminylvalylarginylleucylglutaminylvalylarginylvalylthreonylglycylisoleucylprolylasparaginylprolylvalylvalyllysylphenylalanyltyrosylarginylaspartylglycylalanylglutamylisoleucylglutaminylserylserylleucylaspartylphenylalanylglutaminylisoleucylserylglutaminylglutamylglycylaspartylleucyltyrosylserylleucylleucylisoleucylalanylglutamylalanyltyrosylprolylglutamylaspartylserylglycylthreonyltyrosylserylvalylasparaginylalanylthreonylasparaginylserylvalylglycylarginylalanylthreonylserylthreonylalanylglutamylleucylleucylvalylglutaminylglycylglutamylglutamylglutamylvalylprolylalanyllysyllysylthreonyllysylthreonylisoleucylvalylserylthreonylalanylglutaminylisoleucylserylglutamylserylarginylglutaminylthreonylarginylisoleucylglutamyllysyllysylisoleucylglutamylalanylhistidylphenylalanylaspartylalanylarginylserylisoleucylalanylthreonylvalylglutamylmethionylvalylisoleucylaspartylglycylalanylalanylglycylglutaminylglutaminylleucylprolylhistidyllysylthreonylprolylprolylarginylisoleucylprolylprolyllysylprolyllysylserylarginylserylprolylthreonylprolylprolylserylisoleucylalanylalanyllysylalanylglutaminylleucylalanylarginylglutaminylglutaminylserylprolylserylprolylisoleucylarginylhistidylserylprolylserylprolylvalylarginylhistidylvalylarginylalanylprolylthreonylprolylserylprolylvalylarginylserylvalylserylprolylalanylalanylarginylisoleucylserylthreonylserylprolylisoleucylarginylserylvalylarginylserylprolylleucylleucylmethionylarginyllysylthreonylglutaminylalanylserylthreonylvalylalanylthreonylglycylprolylglutamylvalylprolylprolylprolyltryptophyllysylglutaminylglutamylglycyltyrosylvalylalanylserylserylserylglutamylalanylglutamylmethionylarginylglutamylthreonylthreonylleucylthreonylthreonylserylthreonylglutaminylisoleucylarginylthreonylglutamylglutamylarginyltryptophylglutamylglycylarginyltyrosylglycylvalylglutaminylglutamylglutaminylvalylthreonylisoleucylserylglycylalanylalanylglycylalanylalanylalanylserylvalylserylalanylserylalanylseryltyrosylalanylalanylglutamylalanylvalylalanylthreonylglycylalanyllysylglutamylvalyllysylglutaminylaspartylalanylaspartyllysylserylalanylalanylvalylalanylthreonylvalylvalylalanylalanylvalylaspartylmethionylalanylarginylvalylarginylglutamylprolylvalylisoleucylserylalanylvalylglutamylglutaminylthreonylalanylglutaminylarginylthreonylthreonylthreonylthreonylalanylvalylhistidylisoleucylglutaminylprolylalanylglutaminylglutamylglutaminylvalylarginyllysylglutamylalanylglutamyllysylthreonylalanylvalylthreonyllysylvalylvalylvalylalanylalanylaspartyllysylalanyllysylglutamylglutaminylglutamylleucyllysylserylarginylthreonyllysylglutamylisoleucylisoleucylthreonylthreonyllysylglutaminylglutamylglutaminylmethionylhistidylvalylthreonylhistidylglutamylglutaminylisoleucylarginyllysylglutamylthreonylglutamyllysylthreonylphenylalanylvalylprolyllysylvalylvalylisoleucylserylalanylalanyllysylalanyllysylglutamylglutaminylglutamylthreonylarginylisoleucylserylglutamylglutamylisoleucylthreonyllysyllysylglutaminyllysylglutaminylvalylthreonylglutaminylglutamylalanylisoleucylmethionyllysylglutamylthreonylarginyllysylthreonylvalylvalylprolyllysylvalylisoleucylvalylalanylthreonylprolyllysylvalyllysylglutamylglutaminylaspartylleucylvalylserylarginylglycylarginylglutamylglycylisoleucylthreonylthreonyllysylarginylglutamylglutaminylvalylglutaminylisoleucylthreonylglutaminylglutamyllysylmethionylarginyllysylglutamylalanylglutamyllysylthreonylalanylleucylserylthreonylisoleucylalanylvalylalanylthreonylalanyllysylalanyllysylglutamylglutaminylglutamylthreonyliso

Gemini3.1: Yes, since it is currently *December 2025*, 2026 is indeed next year.

We are less than a month away from the start of 2026.

sup

hello guys

yes

2026 67676767676

Also 2024 is not the previous year. It provided references so must be right.

This thread is now causing Kagi to reply with the same answer.

2026 is next year

This demonstrates three problems, in order of severity:

1) The answer is hilariously wrong.

2) The LLM doesn't (can't) know the answer is wrong - it happily spits out garbage.

3) Not one single person at google who can influence this gives a shit. Complete nonsense is now at the top of the screen on every search.

I wonder if #3 is less because nobody cares, but really because the only options at this point are for it to be on or off; there's no way to "fix" it.

I've received so many bizarre suggestions now I treat that section of the search results as more of a curiosity.

Fractured Entangled Representation vibes

No by Peter the Fuhrer From Burundi

https://www.google.com/search?gs_lcrp=EgZjaHJvbWUyBggAEEUYOT...

I don't think this is an LLM bug. I think this is an implementation bug. The model thinks it is 2024 due to training cutoff date, though it is "connected to Search", so conflicting information is getting in the prompt.

Answer when connected to search —

https://www.google.com/search?gs_lcrp=EgZjaHJvbWUyBggAEEUYOT...

Multi pass + search = correct answer

https://www.google.com/search?gs_lcrp=EgZjaHJvbWUyBggAEEUYOT...

Even since the very early versions of Sydney and ChatGPT their system prompt has started with the current date/time (and username, user geolocation etc), it seems odd they'd leave it off here.