<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security,open-Source,ai,bug-Bounty,engineering on Thiago Avelino</title><link>https://avelino.run/tags/securityopen-sourceaibug-bountyengineering/</link><description>Recent content in Security,open-Source,ai,bug-Bounty,engineering on Thiago Avelino</description><generator>Hugo</generator><language>en-us</language><copyright>© Avelino</copyright><lastBuildDate>Tue, 17 Nov 2026 08:18:40 -0300</lastBuildDate><atom:link href="https://avelino.run/tags/securityopen-sourceaibug-bountyengineering/index.xml" rel="self" type="application/rss+xml"/><item><title>Every app has a hole. The reports got better.</title><link>https://avelino.run/every-app-has-a-hole-the-reports-got-better/</link><pubDate>Tue, 17 Nov 2026 00:00:00 +0000</pubDate><guid>https://avelino.run/every-app-has-a-hole-the-reports-got-better/</guid><description>&lt;p&gt;Every non-trivial system has holes. I have been a CTO long enough, and I have maintained open source long enough, to treat that as a starting point, not a scandal. The work is to assume they are there, give people a way to tell you, and fix what you can reproduce.&lt;/p&gt;
&lt;p&gt;What changed is the cost. A capable student with a model can turn ordinary recon into a writeup you can act on in an afternoon. The reports landing in a CTO inbox look different now. That is good for users. It is also more work for the person who has to read them.&lt;/p&gt;</description></item></channel></rss>