<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Svelte on Daniel &#39;f0o&#39; Preussker</title>
    <link>https://f0o.dev/tags/svelte/</link>
    <description>Recent content in Svelte on Daniel &#39;f0o&#39; Preussker</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 23 May 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://f0o.dev/tags/svelte/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Rebuilding the Looking Glass: Stateless, High-Performance Network Diagnostics at Scale</title>
      <link>https://f0o.dev/posts/2026/05/rebuilding-the-looking-glass-stateless-high-performance-network-diagnostics-at-scale/</link>
      <pubDate>Sat, 23 May 2026 10:00:00 +0000</pubDate>
      
      <guid>https://f0o.dev/posts/2026/05/rebuilding-the-looking-glass-stateless-high-performance-network-diagnostics-at-scale/</guid>
      <description>&lt;h3 id=&#34;why-are-some-networks-still-running-cgi-in-2026&#34;&gt;Why Are Some Networks Still Running CGI in 2026?&lt;/h3&gt;
&lt;p&gt;Seriously, why are some networks still running CGI scripts from 1997 on core production edge routers? Every single time I have to troubleshoot a BGP route flap at 3 AM and load up some ancient, timeout-ridden Perl looking glass, a small part of my soul dies.&lt;/p&gt;
&lt;p&gt;Most public looking glasses are outdated CGI or raw PHP scripts. They parse user inputs insecurely, lack any form of caching, and put a heavy CPU load on core routers during diagnostics.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
