<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: beamy</title><link>https://news.ycombinator.com/user?id=beamy</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 03 Sep 2026 09:32:41 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=beamy" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by beamy in "Claude Fable 5.1 and Claude Mythos 5.1"]]></title><description><![CDATA[
<p>This is a good explainer: <a href="https://magazine.sebastianraschka.com/p/claude-watermarking" rel="nofollow">https://magazine.sebastianraschka.com/p/claude-watermarking</a></p>
]]></description><pubDate>Tue, 01 Sep 2026 18:46:49 +0000</pubDate><link>https://news.ycombinator.com/item?id=49526241</link><dc:creator>beamy</dc:creator><comments>https://news.ycombinator.com/item?id=49526241</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49526241</guid></item><item><title><![CDATA[New comment by beamy in "LG to ban residential proxies from smart TV apps"]]></title><description><![CDATA[
<p>Isn’t this like arguing we shouldn’t have food standards because people should be free to decide what they put in their bodies?<p>Sure, in principle that’s true.<p>But in practice, is it really fair to expect everyone to understand the health risks of every possible ingredient?<p>Likewise here, is it fair to expect the average consumer to understand what it means to host a residential proxy? Or even what a residential proxy is?</p>
]]></description><pubDate>Wed, 22 Jul 2026 12:21:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=49005590</link><dc:creator>beamy</dc:creator><comments>https://news.ycombinator.com/item?id=49005590</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49005590</guid></item><item><title><![CDATA[New comment by beamy in "SQL patterns I use to catch transaction fraud"]]></title><description><![CDATA[
<p>In my experience, what you're describing would more specifically be called Fraud Prevention rather than Fraud Detection. Both tend to coexist and are complementary in a mature setup.<p>For Prevention, you're always going to be constrained by latency requirements, available data and an incomplete picture of user behaviour. You make a quick decision using ML and rules that deals with the majority of cases. But those constraints make it impossible to precisely prevent all fraud.<p>Detection deals with the downstream consequences of this. A team of analysts will typically analyse the accepted transactions for signs of fraud. This is particularly important for fraud types where you don't get an external signal like a chargeback or customer complaint. Platform integrity is one such example. But Fintechs will also see this building anti-money laundering systems - you need to go looking for the fraud. This is the process the article is describing.<p>I say they're complementary because the detected transactions become the labels for training and evaluating the next iteration of prevention models.</p>
]]></description><pubDate>Sat, 16 May 2026 09:30:12 +0000</pubDate><link>https://news.ycombinator.com/item?id=48158507</link><dc:creator>beamy</dc:creator><comments>https://news.ycombinator.com/item?id=48158507</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48158507</guid></item></channel></rss>