<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: betree</title><link>https://news.ycombinator.com/user?id=betree</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 03 Sep 2026 07:55:20 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=betree" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by betree in "A third of Perplexity's citations don't contain the number they're cited for"]]></title><description><![CDATA[
<p>100% my experience with this service. The intent is good, but it seems they're still in the "fake it until you make it" stage.</p>
]]></description><pubDate>Wed, 02 Sep 2026 15:57:46 +0000</pubDate><link>https://news.ycombinator.com/item?id=49538234</link><dc:creator>betree</dc:creator><comments>https://news.ycombinator.com/item?id=49538234</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49538234</guid></item><item><title><![CDATA[New comment by betree in "Use Task Runners for Common Coding Tasks"]]></title><description><![CDATA[
<p>Historically, I did it the other way around: have some autogenerated shell commands (dev, test, pull...etc) on my local machine that detect which language the project in the current folder is using, and calls commands accordingly.
I did it this way because, in my case, it was challenging to consolidate multiple projects across multiple organizations under a single tool.<p>It's public, but I realize I haven't pushed my local updates for a while now.
<a href="https://github.com/Betree/dev-commander" rel="nofollow">https://github.com/Betree/dev-commander</a></p>
]]></description><pubDate>Mon, 03 Aug 2026 19:51:03 +0000</pubDate><link>https://news.ycombinator.com/item?id=49160569</link><dc:creator>betree</dc:creator><comments>https://news.ycombinator.com/item?id=49160569</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49160569</guid></item><item><title><![CDATA[My burner email blocklist blocked me]]></title><description><![CDATA[
<p>Article URL: <a href="https://benjamin.piouffle.com/blog/burner-email-blocklists/">https://benjamin.piouffle.com/blog/burner-email-blocklists/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=48846941">https://news.ycombinator.com/item?id=48846941</a></p>
<p>Points: 49</p>
<p># Comments: 56</p>
]]></description><pubDate>Thu, 09 Jul 2026 14:54:34 +0000</pubDate><link>https://benjamin.piouffle.com/blog/burner-email-blocklists/</link><dc:creator>betree</dc:creator><comments>https://news.ycombinator.com/item?id=48846941</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48846941</guid></item><item><title><![CDATA[Show HN: Movement-based captcha – temporal reasoning to foil AI vision]]></title><description><![CDATA[
<p>I built a proof-of-concept captcha that uses motion rather than distortion or object recognition. Solution characters move along a shared path with coordinated momentum; noise characters may follow shapes too but out of sync. You observe, identify the group by how it moves, type the code.<p>Rationale: static captchas are increasingly solved by vision models. Temporal reasoning over multiple frames is harder and more expensive for frame-by-frame AI analysis.<p>Client-side only, solution is visible in memory. Accessibility caveats apply (motion, vestibular, seizures).<p>Curious what the HN crowd thinks.<p>Demo: <a href="https://betree.github.io/movement-captcha" rel="nofollow">https://betree.github.io/movement-captcha</a></p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=46988165">https://news.ycombinator.com/item?id=46988165</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Thu, 12 Feb 2026 12:50:14 +0000</pubDate><link>https://github.com/Betree/movement-captcha</link><dc:creator>betree</dc:creator><comments>https://news.ycombinator.com/item?id=46988165</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46988165</guid></item><item><title><![CDATA[New comment by betree in "OpenCollective Shutting Down"]]></title><description><![CDATA[
<p>Title is misleading, Open Collective is not shutting down. See the other thread for more details: <a href="https://news.ycombinator.com/item?id=39540919">https://news.ycombinator.com/item?id=39540919</a>.</p>
]]></description><pubDate>Wed, 28 Feb 2024 21:24:47 +0000</pubDate><link>https://news.ycombinator.com/item?id=39543612</link><dc:creator>betree</dc:creator><comments>https://news.ycombinator.com/item?id=39543612</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=39543612</guid></item></channel></rss>