<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: GrantMoyer</title><link>https://news.ycombinator.com/user?id=GrantMoyer</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 20 Nov 2026 23:47:24 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=GrantMoyer" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by GrantMoyer in "Gemini 4 Neon is the new #1 on the Models Engineering Index"]]></title><description><![CDATA[
<p>For probably most people, 200$ per month is already a no brainer, just in the other direction.</p>
]]></description><pubDate>Fri, 20 Nov 2026 05:10:50 +0000</pubDate><link>https://news.ycombinator.com/item?id=50570426</link><dc:creator>GrantMoyer</dc:creator><comments>https://news.ycombinator.com/item?id=50570426</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50570426</guid></item><item><title><![CDATA[New comment by GrantMoyer in "Many of Amazon’s Black Friday and Cyber Monday “deals” offered no savings"]]></title><description><![CDATA[
<p>I have a bone to pick with Amazon. I believe their return process is intentionally obtuse to get customers to give up and eat the cost of Amazon's poor quality control.<p>I bought a 15$ music CD sold and shipped by Amazon. They sent me wrong CD. The listing says it's the edition with a bonus track, but they sent me the edition without a bonus track.<p>I'd like to have them send me the right item, so I look at the return process on the website, but there's no option for "you sent me the wrong thing"; the closest is "the item is defective", but that option specifically says they'll send me the same item after they recieve my return, which is exactly what I don't want. There is no "something else" option.<p>I look for a support email where I can make a request with the full details. The support website is a labyrinth, and there is no support email.<p>There is a chat option, so I use chat support and explain the situation. The support person says I have to wait 48 hours after recieving the item to begin a return, I point out that's contrary to Amazon's return policy. The support person doubles down and refuses to start a return.<p>There's no support phone number, but there's an option to request they call me. I make the request and am called by an automated phone system. It eventually connects me to a human support person. I describe the problem to the support person over the phone, and he redirects me to a different support person. I describe the issue again to the new support person, including that the "defective item" option on the website says I'll be sent the same item. He explains that he cannot resolve my situation, so he reccomends that I file a return through the website with the "defective item" option anyway, but he can't guaruantee they'll send me the right item. He never mentions the supposed 48 hour cooldown period.<p>I file the return through the website, and drop off the item for return shipping the same day. A month and a half later, I recieve the replacememt item. It's the same wrong item.<p>I request another callback from Amazon again the next day. When I get to a human support person, I explain that I was sent the wrong item, then sent the same wrong item again as a replacement. I'm transfered to a "specialist". I confirm that I recieved the wrong item and replacement again. I'm told I need to upload a photo of the wrong item to a link they will send me by email. Immediately after the call, I take a photo and upload it at the link.<p>12 days later, I haven't heard back. I request a callback for the third time. I explain the situation, and that I called 1 or 2 weeks ago and submitted documentation. I'm told a return is the only option; Amazon will not send me the item I ordered. I double check that there's no way to have the correct item sent, since I just want the CD I ordered, and the support person confirms it's not possible. The support person opens a return, and I drop the item off for return shipping the same day. 12 days layer, Amazon refunds the money to my account.<p>Overall, the process took over two months, a chat session, three phone calls, and Amazon paying for shipping both ways two times, all for a 15$ CD, and in the end the problem wasn't even resolved. Any sane company would have resolved the problem on the first contact with support with a simple "oh yeah, oops, we sent the wrong item. We'll send you the right one." I have not ordered anything from Amazon since.</p>
]]></description><pubDate>Mon, 16 Nov 2026 18:06:24 +0000</pubDate><link>https://news.ycombinator.com/item?id=50520714</link><dc:creator>GrantMoyer</dc:creator><comments>https://news.ycombinator.com/item?id=50520714</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50520714</guid></item><item><title><![CDATA[New comment by GrantMoyer in "Do House members' stock trades beat the market? A test of 8,900 trades"]]></title><description><![CDATA[
<p>Plus the S&P 500 is not "the market". It's a subset of the total US market that usually performs pretty close to the total US market, but a few percent difference either direction in performance isn't unusual, especially over less than a year.<p>And I don't think equal weighted S&P 500 is sufficiently motivated.</p>
]]></description><pubDate>Sun, 15 Nov 2026 22:27:52 +0000</pubDate><link>https://news.ycombinator.com/item?id=50511521</link><dc:creator>GrantMoyer</dc:creator><comments>https://news.ycombinator.com/item?id=50511521</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50511521</guid></item><item><title><![CDATA[New comment by GrantMoyer in "Brave Search API now accepts agentic payments via the x402 protocol"]]></title><description><![CDATA[
<p>I had something like 30¢ of interest income from one bank this year. I entered it on the free fillable form for my federal taxes, but it rounded it to zero.<p>I looked through the instructions on the forms, and they say you may round to the nearest dollar. In theory, I think you'd need to compute capital gains (sell price - purchase price) at each transfer, but I expect in practice they'd almost all round to zero since USDC is supposed to be equal to the value of the US dollar.</p>
]]></description><pubDate>Fri, 13 Nov 2026 15:21:18 +0000</pubDate><link>https://news.ycombinator.com/item?id=50484844</link><dc:creator>GrantMoyer</dc:creator><comments>https://news.ycombinator.com/item?id=50484844</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50484844</guid></item><item><title><![CDATA[New comment by GrantMoyer in "We need more goat sacrifices"]]></title><description><![CDATA[
<p>Isn't trying a plausible sociological intervention then measuring its effectiveness a win regardless of how effective it ended up being? Either way, we know more about what's likely to work for future interventions. It's the scientific method.<p>These interventions target very complex systems. It's not unexpected that we need to try a bunch of things that don't work before we find something that does, to the extent that <i>most</i> of the things we try are ineffective, right?<p>Edit: I wrote the above before reaching the end of the article. By the end, the article reaches a similar conclusion, albiet with less science and more mysticism.<p>Maybe that means it's a good article, leading me to reach its conclusion before taking the stance itself. On the other hand, the article's leading sections gave such a strong impression that the author thought something needs to be drastically changed about the current system — the opposite stance from its conclusion — on seemingly shakey grounds, that I almost didn't finish reading it. I'm not sure what to think, aside from please leave innocent goats alone.</p>
]]></description><pubDate>Wed, 11 Nov 2026 16:18:39 +0000</pubDate><link>https://news.ycombinator.com/item?id=50455142</link><dc:creator>GrantMoyer</dc:creator><comments>https://news.ycombinator.com/item?id=50455142</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50455142</guid></item><item><title><![CDATA[New comment by GrantMoyer in "Unlocking any car from X brand in most of the world"]]></title><description><![CDATA[
<p>Many cars use loose tolerance wafer locks[1] which are vulnerable to "raking". Picking a lock involves setting each tumbler individually by feel, and requires significant skill. Raking, on the other hand, is basically just rapidly jiggling a bumpy stick in the lock until all the tumblers bounce around enough to get caught on the edge of the cylinder and the lock opens. It's fairly low-skill, and can be quick enough that it looks almost like using a key[2]. (picking for comparison [3])<p>Lots of pin tumbler locks like you would find in a door on a house are also vulnerable to raking. It's easy to mitgate; you just use some bumpy pins (security pins) that are more likely to get caught in way that won't let the lock open than will, but lock manufacturers just … don't.<p>[1]: <a href="https://en.wikipedia.org/wiki/Wafer_tumbler_lock" rel="nofollow">https://en.wikipedia.org/wiki/Wafer_tumbler_lock</a><p>[2]: <a href="https://www.youtube.com/watch?v=oztjRNKKTwE" rel="nofollow">https://www.youtube.com/watch?v=oztjRNKKTwE</a><p>[3]: <a href="https://www.youtube.com/watch?v=g0c1UAeuKlw" rel="nofollow">https://www.youtube.com/watch?v=g0c1UAeuKlw</a></p>
]]></description><pubDate>Tue, 10 Nov 2026 00:41:50 +0000</pubDate><link>https://news.ycombinator.com/item?id=50434568</link><dc:creator>GrantMoyer</dc:creator><comments>https://news.ycombinator.com/item?id=50434568</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50434568</guid></item><item><title><![CDATA[New comment by GrantMoyer in "Unlocking any car from X brand in most of the world"]]></title><description><![CDATA[
<p>> Also take a look at how easily a professional could gain access to your home if they wanted to.<p>Or an amateur with a mallet, a key blank, a file, and an o-ring.<p><a href="https://en.wikipedia.org/wiki/Lock_bumping" rel="nofollow">https://en.wikipedia.org/wiki/Lock_bumping</a></p>
]]></description><pubDate>Mon, 09 Nov 2026 08:01:11 +0000</pubDate><link>https://news.ycombinator.com/item?id=50422509</link><dc:creator>GrantMoyer</dc:creator><comments>https://news.ycombinator.com/item?id=50422509</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50422509</guid></item><item><title><![CDATA[New comment by GrantMoyer in "Vivaldi 8.3 for Desktop: make bad ads sad"]]></title><description><![CDATA[
<p>The problem is that the choice isn't seeing ads v.s. paying for the content. Instead, the choice is seeing ads v.s. overpaying for the content, then seeing ads anyway when the service decides to indroduce ads back to the paid subscription. By overpaying, I mean compared to what the service itself values its content at when it serves it for free with ads.<p>How many people would sign up for a 15$ per month subscription to read one article with no ads? How many would pay 1¢ once to read the article with no ads? How many would sign up for one 15$ per month subscription to see no ads anywhere?<p>I realize we don't have the infrastructure to make high volume 1¢ payments, and probably not for lack of trying, but I just don't think the core problem is that people only want stuff for 0¢ and not almost 0¢.</p>
]]></description><pubDate>Thu, 05 Nov 2026 15:25:21 +0000</pubDate><link>https://news.ycombinator.com/item?id=50380267</link><dc:creator>GrantMoyer</dc:creator><comments>https://news.ycombinator.com/item?id=50380267</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50380267</guid></item><item><title><![CDATA[New comment by GrantMoyer in "Incident with Pull Requests, Git Operations and Issues"]]></title><description><![CDATA[
<p>Point of clarification: do you work at GitHub?</p>
]]></description><pubDate>Wed, 04 Nov 2026 14:39:41 +0000</pubDate><link>https://news.ycombinator.com/item?id=50366157</link><dc:creator>GrantMoyer</dc:creator><comments>https://news.ycombinator.com/item?id=50366157</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50366157</guid></item><item><title><![CDATA[New comment by GrantMoyer in "The $6.3B Binance hack was pulled off in just 20 minutes"]]></title><description><![CDATA[
<p>I think one of the primary motivations for cryptocurrency was that legal ≠ moral. Therefore, I think cryptocurrency's best use cases are all explicitly <i>illegal</i>.<p>For example, you can donate to Sci-Hub with cryptocurrency. Sci-Hub has an ideological mission which is widely supported, but it runs afoul of copyright law and is illegal in nearly every country and sanctioned in many. You cannot donate to Sci-Hub with fiat currency.<p>Unfortunately, I agree that in practice >99% of cryptocurrency's use is for scams.</p>
]]></description><pubDate>Fri, 30 Oct 2026 15:18:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=50305151</link><dc:creator>GrantMoyer</dc:creator><comments>https://news.ycombinator.com/item?id=50305151</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50305151</guid></item><item><title><![CDATA[New comment by GrantMoyer in "Your Phone Is About to Stop Being Yours: 70 Days Until Lockdown"]]></title><description><![CDATA[
<p>Firstly, TFA has a bright red banner describing the opt-out mechanism. It's probably the second most attention-grabbing element on the page, after the countdown. Secondly, initially Google didn't mention any plans for an opt-out at all[1]. That was was only ceded after pushback[2].<p>[1]: <a href="https://web.archive.org/web/20260312134021/https://developer.android.com/developer-verification/guides/faq" rel="nofollow">https://web.archive.org/web/20260312134021/https://developer...</a><p>[2]: <a href="https://web.archive.org/web/20260328133800/https://developer.android.com/developer-verification/guides/faq#advanced-flow" rel="nofollow">https://web.archive.org/web/20260328133800/https://developer...</a></p>
]]></description><pubDate>Fri, 23 Oct 2026 17:23:24 +0000</pubDate><link>https://news.ycombinator.com/item?id=50212431</link><dc:creator>GrantMoyer</dc:creator><comments>https://news.ycombinator.com/item?id=50212431</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50212431</guid></item><item><title><![CDATA[New comment by GrantMoyer in "Disney Raising Prices Days After Confirming Ads Will Now Show Up on Every Tier"]]></title><description><![CDATA[
<p>> Somewhere, that line exists where the company would financially benefit, I just wish they'd actually define it.<p>The line <i>doesn't</i> exists. It's most profitable for the company to repeatedly:<p>1. Have an ad-supported tier and a no-ads tier<p>2. Wait for most people to move to the no-ads tier<p>3. Introduce ads into the no-ads tier<p>4. Wait for people to get sick of ads<p>5. Introduce a new, higher cost no ads tier<p>There is no threshold where it's more profitable for the company to never introduce ads at that price point.</p>
]]></description><pubDate>Fri, 23 Oct 2026 13:37:39 +0000</pubDate><link>https://news.ycombinator.com/item?id=50208783</link><dc:creator>GrantMoyer</dc:creator><comments>https://news.ycombinator.com/item?id=50208783</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50208783</guid></item><item><title><![CDATA[New comment by GrantMoyer in "JPEG XL vs. AVIF for web use-cases"]]></title><description><![CDATA[
<p>The benchmark[1] (HN discussion [2]) I read from about 2.5 years ago came to roughly the opposite conclusion. JPEG XL dominated practically all other image formats on compressed size and encoding time.<p>Superficially, that benchmark and this one seem to be taking similar measurements. They both measure encoded size versus encoding time versus perceptual quality metrics, although they present the data on plots with different axes. I haven't tried to reproduce the results of either, but I have no reason to doubt either benchmark.<p>I wonder what accounts for the difference. Maybe the libavif encoder got a lot better in the last 2.5 years. The older benchmark uses libjxl v0.10.0 and libavif v1.0.3, while the newer one uses libjxl v0.12.0 and libavif v1.4.2. Or maybe it's the set of images used. The older benchmarks aggregates results for small test sets of images, while the newer benchmark tests individual images. The newer benchmark does find an image where libjxl wins on file size (the weasel), but it still loses on encoding time, whereas in the older benchmark libjxl almost always won on both. Or maybe it's the hardware (M3 Pro vs. M4 Pro).<p>[1]: <a href="https://cloudinary.com/blog/jpeg-xl-and-the-pareto-front" rel="nofollow">https://cloudinary.com/blog/jpeg-xl-and-the-pareto-front</a><p>[2]: <a href="https://news.ycombinator.com/item?id=39559281">https://news.ycombinator.com/item?id=39559281</a></p>
]]></description><pubDate>Sat, 17 Oct 2026 17:35:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=50133148</link><dc:creator>GrantMoyer</dc:creator><comments>https://news.ycombinator.com/item?id=50133148</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50133148</guid></item><item><title><![CDATA[New comment by GrantMoyer in "Meta’s new commercial terms will allow the scraping of news sites: experts"]]></title><description><![CDATA[
<p>I regularly fully read and try to understand paper contracts before signing them. Every time, it's clear that no time was set aside for me to read the contract, and the other party expected me to sign the contract within a few seconds of first receiving it. Often, I get the sense that the other party is annoyed or frustrated that I take time to read the contract before agreeing to it.<p>I've read that contracts fundamentally require a "meeting of the minds", where two parties come to a mutual understanding of an agreement. At the same time, overwhelming people are expected to not read and understand contracts they agree to. I don't understand how these two facts don't combine to mean the vast majority of written contracts are not legally binding, but apparently judges don't share my confusion.</p>
]]></description><pubDate>Fri, 16 Oct 2026 12:59:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=50117835</link><dc:creator>GrantMoyer</dc:creator><comments>https://news.ycombinator.com/item?id=50117835</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50117835</guid></item><item><title><![CDATA[New comment by GrantMoyer in "Do dentists know what they're doing?"]]></title><description><![CDATA[
<p>It alienates me, because I cannot relate to it. To me, it reads like the author is going around, running some sort of flowchart for every woman they briefly interact with, like:<p><pre><code>  [Are they hot?] -No> <Ignore>
         |
        Yes
         v
  [Are they wearing a ring?] -Yes> <Ignore>
         |
         No
         v
         …
</code></pre>
I don't even know what that last step would be. It's not going to be sex. The woman is at work and the two don't even know each other.<p>Maybe that's not what the author is thinking. I don't know, because I <i>can't understand</i> what the author is thinking. I'm alienated.</p>
]]></description><pubDate>Thu, 15 Oct 2026 22:43:06 +0000</pubDate><link>https://news.ycombinator.com/item?id=50111411</link><dc:creator>GrantMoyer</dc:creator><comments>https://news.ycombinator.com/item?id=50111411</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50111411</guid></item><item><title><![CDATA[New comment by GrantMoyer in "Do dentists know what they're doing?"]]></title><description><![CDATA[
<p>The comments on women's bodies are not relevant to the narrative, and they alienate readers (women <i>and</i> men). It's bad writing.</p>
]]></description><pubDate>Thu, 15 Oct 2026 12:28:22 +0000</pubDate><link>https://news.ycombinator.com/item?id=50102678</link><dc:creator>GrantMoyer</dc:creator><comments>https://news.ycombinator.com/item?id=50102678</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50102678</guid></item><item><title><![CDATA[New comment by GrantMoyer in "11 year old unsoundness bugs found in Rust borrow checker"]]></title><description><![CDATA[
<p>And even if the theorem prover has no errors, the math behind the theorem prover could be inconsistent according to Gödel's incompleteness theorem. So even in principle, we can never be completely certain about the soundness of Rust, though the more theoretical concerns tend to be dwarfed by basic human error.<p>I think it's a good thing to keep in mind, that the actual implementation of Rust almost certainly isn't sound. Even an "ideal Rust" still has unsafe, which can affect the soundness of even faraway safe code. But I don't think it's nessesarily wrong to talk about Rust as if it were safe. Much of our communication has implicit assumptions, and the way we talk about Rust is no different. It would be exhausting to qualify every discussion of saftey with "assuming the compiler has no bugs", "assuming all unsafe code follows the (not fully specified!) rules", etc.<p>Ultimately it's like any other implementation of theory into practice. The theoretical model of Rust lets us reason about and design an implementation to achieve certain practical goals even though the model is a simplification of reality. In Rust's case, practical use has demonstrated it achieves design goals like reducing bugs and reducing development time (compared to peers like C++) to a substantial degree.</p>
]]></description><pubDate>Tue, 13 Oct 2026 15:24:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=50073195</link><dc:creator>GrantMoyer</dc:creator><comments>https://news.ycombinator.com/item?id=50073195</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50073195</guid></item><item><title><![CDATA[New comment by GrantMoyer in "11 year old unsoundness bugs found in Rust borrow checker"]]></title><description><![CDATA[
<p>It's surprising this bug went unnoticed for so long, but at least it's easy to fix, since it's not a bug with the type system itself; it's just a bug in the compiler. The compiler should always have been rejecting that code according to lifetime rules of Rust's type system, so the fix is to just make it reject the code, rather than having to change the fundamental rules of lifetimes.</p>
]]></description><pubDate>Tue, 13 Oct 2026 12:51:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=50070882</link><dc:creator>GrantMoyer</dc:creator><comments>https://news.ycombinator.com/item?id=50070882</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50070882</guid></item><item><title><![CDATA[New comment by GrantMoyer in "Reducing undefined behavior in the C language"]]></title><description><![CDATA[
<p>Let's take a simple example: writing past the end of an array. Allow me to argue with myself for a moment.<p>> Surely the compiler can just check if each access is valid.<p>Well, sometimes it can, but sometimes it doesn't know how long the array is. What if the array is passed as a pointer?<p>> Maybe each array could be annotated with its size at runtime, and accesses could be checked at runtime too.<p>That works, but it adds runtime cost that may legitimately be too much for some applications, for example, a Gameboy game (set aside that many Gameboy games were written in assembly).<p>> Fine, so we'll make the programmer promise to ensure array accesses are always valid. Maybe they'll make a mistake sometimes, but what's the worst that could happen? Throwing your hands in the air and saying the compiler is allowed to do anything, that's just stupid.<p>Well, maybe it's stupid, but this is one thing that could happen if you accidentally write past the end of an array: <a href="https://www.youtube.com/watch?v=Vjm8P8utT5g" rel="nofollow">https://www.youtube.com/watch?v=Vjm8P8utT5g</a>. I'm sure neither the programmers nor compiler writers intended that.<p>Ultimately, the compiler <i>can't</i> guarantee any behavior if its assumptions are violated. The example may seem contrived, but it demonstrates that, given the right circumstances, the results of the logical contradiction are unbounded. This is a direct consequence of the "Principle of explosion": <a href="https://en.wikipedia.org/wiki/Principle_of_explosion" rel="nofollow">https://en.wikipedia.org/wiki/Principle_of_explosion</a>. On second thought, maybe the runtime costs of array bounds checking are an acceptable trade-off after all.</p>
]]></description><pubDate>Fri, 09 Oct 2026 04:46:33 +0000</pubDate><link>https://news.ycombinator.com/item?id=50016086</link><dc:creator>GrantMoyer</dc:creator><comments>https://news.ycombinator.com/item?id=50016086</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50016086</guid></item><item><title><![CDATA[New comment by GrantMoyer in "Shipping JPEG XL in Chrome"]]></title><description><![CDATA[
<p>Windows has, for a while, had Windows Imaging Component for images (<a href="https://learn.microsoft.com/en-us/windows/win32/wic/-wic-lh" rel="nofollow">https://learn.microsoft.com/en-us/windows/win32/wic/-wic-lh</a>) and Microsoft Media Foundation for video (<a href="https://learn.microsoft.com/en-us/windows/win32/medfound/microsoft-media-foundation-sdk" rel="nofollow">https://learn.microsoft.com/en-us/windows/win32/medfound/mic...</a>). Not sure how widespread actual use is though.</p>
]]></description><pubDate>Wed, 07 Oct 2026 13:31:28 +0000</pubDate><link>https://news.ycombinator.com/item?id=49992602</link><dc:creator>GrantMoyer</dc:creator><comments>https://news.ycombinator.com/item?id=49992602</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49992602</guid></item></channel></rss>