Comment by kshacker
20 hours ago
Not trying to excuse google but wonder why that happens. I have had my own issues with ChatGPT memory but that's more like it forgets the context and spits out something gibberish at a later invocation counter to what it said earlier in the thread. But that's because it is buggy.
Rewriting history requires computes which is more malicious. Why would someone burn compute to rewrite your stuff given that rewrites are not free? Once again not defending google trying to think through what's going on.
Maybe they use some kind of response caching to save resources and the original pointer is now pointing to a newer response to the same question? Still would be an insane way to do that for a history log unless they're trying to memory hole previous instances of past poor performances or wrong think.
My best guess is that when they changed the model backing "Gemini" they regenerated the conversations.
I can't think of any reason it would make sense to do that, though.