<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Web-Analytics on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/web-analytics/</link>
    <description>Recent content in Web-Analytics on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 21 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/web-analytics/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>UAParser.js vs Matomo DeviceDetector vs uap-python in 2026: Parsing User Agents When Chrome Lies About Its Version</title>
      <link>https://www.pistack.xyz/posts/2026-10-21-user-agent-parsing-libraries-uaparserjs-devicedetector-uap-python/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-21-user-agent-parsing-libraries-uaparserjs-devicedetector-uap-python/</guid>
      <description>&lt;p&gt;Open Chrome 130 today and read its User-Agent string. It claims to be Chrome &lt;strong&gt;110.0.0.0&lt;/strong&gt;, on Windows 10 even if you run Windows 11, and it has claimed that for over two years. Chrome froze the UA version in 2023, Firefox froze platform details, and Safari reports a version that maps only loosely to the real WebKit build. Every analytics dashboard built on user-agent parsing is therefore reporting deliberately degraded data — and most teams never noticed, because the strings still parse successfully.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
