<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gemma on René Welches</title><link>https://blog.renewelches.com/tags/gemma/</link><description>Recent content in Gemma on René Welches</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 15 Jun 2026 10:43:15 -0400</lastBuildDate><atom:link href="https://blog.renewelches.com/tags/gemma/index.xml" rel="self" type="application/rss+xml"/><item><title>Back to the Future: Bringing Ollama Date-Blind Models to the Present</title><link>https://blog.renewelches.com/2026/06/13/open-webui-current-date-filter/</link><pubDate>Sat, 13 Jun 2026 10:00:00 +0000</pubDate><guid>https://blog.renewelches.com/2026/06/13/open-webui-current-date-filter/</guid><description>&lt;p&gt;A while back I wrote about &lt;a href="https://blog.renewelches.com/2026/05/26/local-ai-stack-mac-mini-proxmox/"&gt;my local AI stack&lt;/a&gt; — Ollama on a Mac mini, Open WebUI on a Proxmox LXC, SearXNG keeping web search private. It mostly just works. Then one day I noticed something strange.&lt;/p&gt;
&lt;p&gt;I asked Gemma 4 to research a topic with web search — something that had just been published that same day in a blog post. The search results came back, full of 2026 dates, and instead of using them Gemma 4 pushed back: it accused me of &lt;em&gt;testing&lt;/em&gt; it, as if I&amp;rsquo;d planted fake future-dated content to see whether it would fall for it. As far as Gemma was concerned it was still some day in 2024, so the actual present looked like a setup. Meanwhile Ministral, running on the same Ollama instance through the same Open WebUI, knew exactly what day it was.&lt;/p&gt;</description></item></channel></rss>