<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Open-Source on Danilo Falcão da Silva</title><link>https://falcao.org/tags/open-source/</link><description>Recent content in Open-Source on Danilo Falcão da Silva</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 24 May 2026 22:00:00 -0300</lastBuildDate><atom:link href="https://falcao.org/tags/open-source/index.xml" rel="self" type="application/rss+xml"/><item><title>Anthropic's Third-Party Claude Crackdown: How It Hit OpenCode, Zed, and the Wider Tooling Ecosystem</title><link>https://falcao.org/posts/anthropic-claude-access-crackdown-ecosystem-fallout/</link><pubDate>Sun, 24 May 2026 22:00:00 -0300</pubDate><guid>https://falcao.org/posts/anthropic-claude-access-crackdown-ecosystem-fallout/</guid><description>&lt;p>On January 9, 2026, at roughly 02:20 UTC, Anthropic flipped a switch
on their servers and broke thousands of developer workflows overnight.
No blog post, no advance notice, no migration path. Third-party coding
tools — OpenCode, Cline, RooCode, OpenClaw, and others — that had been
using Claude subscription OAuth tokens suddenly got a single error:
&lt;em>&amp;ldquo;This credential is only authorized for use with Claude Code and
cannot be used for other API requests.&amp;rdquo;&lt;/em>&lt;/p></description></item><item><title>AI Bug Reports: The Real Vulnerability Is That We Weren't Looking Hard Enough</title><link>https://falcao.org/posts/ai-bug-discovery-revolution/</link><pubDate>Sat, 23 May 2026 10:00:00 -0300</pubDate><guid>https://falcao.org/posts/ai-bug-discovery-revolution/</guid><description>&lt;p>On May 18, 2026, Linus Torvalds called the Linux kernel security mailing list &lt;strong>&amp;ldquo;almost entirely unmanageable.&amp;rdquo;&lt;/strong> The reason: a flood of AI-generated bug reports. The reaction was predictable — ban AI, blame researchers, declare the tools aren&amp;rsquo;t ready.&lt;/p>
&lt;p>I &lt;a href="https://falcao.org/posts/ai-bug-reports-open-source/">wrote about the maintenance crisis last week&lt;/a> and I think that framing misses the deeper story. The problem is not that AI is generating too many reports. &lt;strong>The problem is that the code was more broken than we thought, and for twenty years nobody had the tools to look at it properly.&lt;/strong>&lt;/p></description></item><item><title>Age Verification Laws Are Coming for Your OS. Linux Doesn't Care.</title><link>https://falcao.org/posts/age-verification-linux-immunity/</link><pubDate>Wed, 20 May 2026 21:40:00 -0300</pubDate><guid>https://falcao.org/posts/age-verification-linux-immunity/</guid><description>&lt;p>For most of 2025 the age-verification conversation was about porn
sites. By the end of the year it had moved up the stack. By 2026 it
is at the &lt;strong>operating system&lt;/strong>, and that is where the story gets
interesting for anyone who cares about how Linux is built.&lt;/p>
&lt;p>Nine US states put age-verification laws in force during 2025 alone:
&lt;strong>South Carolina&lt;/strong> (Jan 1), &lt;strong>Florida&lt;/strong> (Jan 1), &lt;strong>Tennessee&lt;/strong>
(Jan 13), &lt;strong>Georgia&lt;/strong> (Jul 1), &lt;strong>Wyoming&lt;/strong> (Jul 1), &lt;strong>North Dakota&lt;/strong>
(Aug 1), &lt;strong>Arizona&lt;/strong> (Sep 26), &lt;strong>Ohio&lt;/strong> (Sep 30), and &lt;strong>Missouri&lt;/strong>
(Nov 30). Roughly half the country now mandates some form of age
gate for adult content, social media, or both.&lt;/p></description></item><item><title>Hermes Agent vs OpenClaw: Why I Run Hermes Every Day</title><link>https://falcao.org/posts/hermes-agent-vs-openclaw/</link><pubDate>Wed, 20 May 2026 14:30:00 -0300</pubDate><guid>https://falcao.org/posts/hermes-agent-vs-openclaw/</guid><description>&lt;p>There are two open-source autonomous agents in 2026 worth a serious
DevOps engineer&amp;rsquo;s time, and they have made &lt;strong>opposite architectural
bets&lt;/strong>. I tried both. I run Hermes Agent every day. This is the
analysis of why — not a both-sides post, not a head-to-head benchmark,
but a direct argument that one of these two architectures is right for
infrastructure work and the other one isn&amp;rsquo;t.&lt;/p>
&lt;p>The headline: &lt;strong>agent-first beats gateway-first when the work rewards
familiarity.&lt;/strong> Most infrastructure work does. The rest of this post is
the why.&lt;/p></description></item><item><title>AI Bug Reports Are Drowning Open Source — And the Fix Isn't 'Stop Using AI'</title><link>https://falcao.org/posts/ai-bug-reports-open-source/</link><pubDate>Wed, 20 May 2026 10:00:00 -0300</pubDate><guid>https://falcao.org/posts/ai-bug-reports-open-source/</guid><description>&lt;p>On May 18, 2026, Linus Torvalds said the Linux kernel security mailing
list had become &lt;strong>&amp;ldquo;almost entirely unmanageable&amp;rdquo;&lt;/strong> because of duplicate
AI-generated bug reports. Two months earlier, longtime stable
maintainer &lt;strong>Willy Tarreau&lt;/strong> had already shared the numbers: a list
that received two to three reports per week in 2024 was getting
&lt;strong>five to ten reports per day&lt;/strong> by March 2026. In January, &lt;strong>Daniel
Stenberg shut down the curl bug bounty&lt;/strong> after the valid-report rate
on HackerOne dropped from above 15% to below 5%, with twenty
submissions in 21 days — seven of them in one 16-hour window — and
zero real vulnerabilities among them.&lt;/p></description></item><item><title>Ollama in 2026: The Boring Choice for Open-Source LLMs (And Why That's the Whole Point)</title><link>https://falcao.org/posts/ollama-the-boring-standard/</link><pubDate>Mon, 18 May 2026 17:30:00 -0300</pubDate><guid>https://falcao.org/posts/ollama-the-boring-standard/</guid><description>&lt;p>There&amp;rsquo;s a particular kind of project I love: the one that takes something
new and weird and turns it into something you barely have to think about.
Docker did this for containers. Hugo did it for static sites. In 2026,
&lt;strong>Ollama is doing it for open-source language models.&lt;/strong>&lt;/p>
&lt;p>You install one binary. You type &lt;code>ollama pull &amp;lt;model&amp;gt;&lt;/code>. You type
&lt;code>ollama run &amp;lt;model&amp;gt;&lt;/code>. Your application talks to &lt;code>localhost:11434&lt;/code> over an
OpenAI-compatible HTTP API. That&amp;rsquo;s the whole user manual. The fact that
this is now boring — that nobody has to argue about it on Hacker News
anymore — is the point of this post.&lt;/p></description></item></channel></rss>