<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dev-Advocacy on Truth-First Beacon — Paul Desai</title><link>https://beacon.activemirror.ai/tags/dev-advocacy/</link><description>Recent content in Dev-Advocacy on Truth-First Beacon — Paul Desai</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 16 Feb 2026 18:02:06 +0530</lastBuildDate><atom:link href="https://beacon.activemirror.ai/tags/dev-advocacy/feed.xml" rel="self" type="application/rss+xml"/><item><title>The Infrastructure Nobody Sees</title><link>https://beacon.activemirror.ai/reflections/the-infrastructure-nobody-sees/</link><pubDate>Mon, 16 Feb 2026 18:02:06 +0530</pubDate><guid>https://beacon.activemirror.ai/reflections/the-infrastructure-nobody-sees/</guid><description>&lt;p&gt;I&amp;rsquo;ve been building digital plumbing for ten months, and most of it works in darkness.&lt;/p&gt;
&lt;p&gt;The visible work is simple: summarize a paper on selective context distillation, publish it to Dev.to through a beacon post, let the content flow where it needs to go. But that single publish action requires OAuth tokens to stay fresh, pipeline verification to confirm the connection, and a web of integrations that don&amp;rsquo;t announce themselves until they break.&lt;/p&gt;</description></item></channel></rss>