<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: quantum5</title><link>https://news.ycombinator.com/user?id=quantum5</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 19 Aug 2026 13:30:34 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=quantum5" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by quantum5 in "Fixing a bricked Framework laptop"]]></title><description><![CDATA[
<p>Author here. I am not even sure how much damage I can actually claim given that I spent $20 on tools to fix the laptop. If I bought a new board, I might be able to claim that, but filing small claims over $20 is likely not worth anyone's time.<p>The important thing here is awareness and helping anyone affected, not trying to get Framework fined for a tiny sum.</p>
]]></description><pubDate>Tue, 18 Aug 2026 22:04:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=49353393</link><dc:creator>quantum5</dc:creator><comments>https://news.ycombinator.com/item?id=49353393</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49353393</guid></item><item><title><![CDATA[New comment by quantum5 in "Fixing a bricked Framework laptop"]]></title><description><![CDATA[
<p>I checked the pictures of my board, and there are 3 unpopulated headers that I can see. There's also the unpopulated BIOS chip socket, which is similarly cheap. I think I would pay the extra $3 per laptop for better repairability, which is Framework's entire sales pitch anyway.</p>
]]></description><pubDate>Tue, 18 Aug 2026 22:01:20 +0000</pubDate><link>https://news.ycombinator.com/item?id=49353352</link><dc:creator>quantum5</dc:creator><comments>https://news.ycombinator.com/item?id=49353352</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49353352</guid></item><item><title><![CDATA[New comment by quantum5 in "Fixing a bricked Framework laptop"]]></title><description><![CDATA[
<p>Original author here:<p>Thanks for linking the documentation! To be clear, when I wrote "header", I meant something with a connector that can be easily used for this purpose. Soldering on the connector is probably more difficult than the pogo pins that I used.<p>I also can't help but notice the linked connector is less than $1 in bulk on DigiKey and probably cheaper if ordered at Framework's scale.</p>
]]></description><pubDate>Tue, 18 Aug 2026 18:43:25 +0000</pubDate><link>https://news.ycombinator.com/item?id=49350565</link><dc:creator>quantum5</dc:creator><comments>https://news.ycombinator.com/item?id=49350565</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49350565</guid></item><item><title><![CDATA[New comment by quantum5 in "Fixing a bricked Framework laptop"]]></title><description><![CDATA[
<p>> Any other laptop is going to have the same risk of a failed BIOS flash, and will likely require the same degree of manual intervention to fix.<p>What I found from my research while writing the post is that both Dell and HP have BIOS recovery options without having to open the laptop at all, so that's not quite true. I think there's more Framework could have done here to make this a much less painful experience.</p>
]]></description><pubDate>Tue, 18 Aug 2026 18:24:03 +0000</pubDate><link>https://news.ycombinator.com/item?id=49350192</link><dc:creator>quantum5</dc:creator><comments>https://news.ycombinator.com/item?id=49350192</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49350192</guid></item><item><title><![CDATA[New comment by quantum5 in "Fixing a bricked Framework laptop"]]></title><description><![CDATA[
<p>Original author here. I have a Raspberry Pi, but I still recommend the CH347 instead of the Pi since it's $5 on AliExpress and you can buy it at the same time as the pogo pins probe, which you need. The advantage of the CH347 is that you don't need to fiddle around with the pinout and risk frying the chip if you screw up. You can just plug the probe in (via the level shifter) and you are good to go.<p>Also, if you are doing the Raspberry Pi, you'd still need the level shifter since the Pi is a 3.3 V device.</p>
]]></description><pubDate>Tue, 18 Aug 2026 18:21:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=49350136</link><dc:creator>quantum5</dc:creator><comments>https://news.ycombinator.com/item?id=49350136</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49350136</guid></item><item><title><![CDATA[New comment by quantum5 in "Fixing a bricked Framework laptop"]]></title><description><![CDATA[
<p>But the problem isn't buying the specific broken part here? I would have gladly replaced the BIOS chip if they made it socketed or something, but what Framework support told me is to throw away the perfectly working CPU and buy a new one because it happened to be soldered to the same board as the BIOS chip with incorrect data.</p>
]]></description><pubDate>Tue, 18 Aug 2026 18:14:07 +0000</pubDate><link>https://news.ycombinator.com/item?id=49350008</link><dc:creator>quantum5</dc:creator><comments>https://news.ycombinator.com/item?id=49350008</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49350008</guid></item><item><title><![CDATA[New comment by quantum5 in "Fixing a bricked Framework laptop"]]></title><description><![CDATA[
<p>Original author here:<p>> This is only true anecdotally. I have installed this BIOS version just fine on my 7040 series unit. It's not broken, works on my machine, my anecdote is worth exactly the same as theirs.<p>I linked an entire thread where people have had similar bricking issues with this exact update: <a href="https://community.frame.work/t/bios-update-stuck/83416" rel="nofollow">https://community.frame.work/t/bios-update-stuck/83416</a><p>If it's just me, I would chalk it up to a freak accident, but it's not.<p>And in the repair thread, you see it's been happening on and off since last year: <a href="https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598" rel="nofollow">https://community.frame.work/t/success-in-recovering-from-ba...</a><p>This isn't an anecdote at this point, but a pattern. I don't think the BIOS updater is working as intended if every update is like playing Russian roulette.<p>> That said, Framework is already well above industry standard in this regard. There are not many laptops out there with non-soldered RAM and removable WiFi modules.<p>Yes, but they are below industry standard for BIOS flashing issues.<p>> The trouble here is that they invite this criticism upon themselves by offering repairability as a flagship benefit, but the reality is that it's not very practical for 100% of the computer to avoid every possible pitfall with long-term ownership.<p>The part that upsets me isn't that they aren't warrantying this. The problem is that they promised to make a laptop I can fix myself and provide all the documentation to do it with confidence long after the warranty ends. That's why I bought into the ecosystem in the first place.<p>Turns out, they claimed to do better and then does all the anti-repair design anyway for BIOS flashing. They didn't even provide any documentation for fixing it myself, which I would have done gladly and then praised them for having documentation.</p>
]]></description><pubDate>Tue, 18 Aug 2026 18:11:33 +0000</pubDate><link>https://news.ycombinator.com/item?id=49349974</link><dc:creator>quantum5</dc:creator><comments>https://news.ycombinator.com/item?id=49349974</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49349974</guid></item><item><title><![CDATA[New comment by quantum5 in "Fixing a bricked Framework laptop"]]></title><description><![CDATA[
<p>It's not a gimmick when the serious overclocking people do custom VBIOSes. Similarly for miners. That's when you need the recovery switch if things go wrong.</p>
]]></description><pubDate>Tue, 18 Aug 2026 16:31:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=49348219</link><dc:creator>quantum5</dc:creator><comments>https://news.ycombinator.com/item?id=49348219</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49348219</guid></item><item><title><![CDATA[New comment by quantum5 in "Fixing a bricked Framework laptop"]]></title><description><![CDATA[
<p>> I would bet that this story of a failed BIOS update reaches the support anytime soon and they provide a repair guide or maybe a replaceable BIOS chip. Stories like this are somehow sad but at least they help to improve.<p>Original author here. I like your optimism, but I've linked multiple threads on their forums with people doing the same problem going back over a year. I also pieced together most of the stuff from people doing external flashing on the forums. Still, no official guides, no changes as far as I can tell. This post is the most detail repair guide available right now.<p>If something happens after this, it would be because this post got to the top of HN and they have to respond to save face.</p>
]]></description><pubDate>Tue, 18 Aug 2026 16:11:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=49347889</link><dc:creator>quantum5</dc:creator><comments>https://news.ycombinator.com/item?id=49347889</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49347889</guid></item><item><title><![CDATA[New comment by quantum5 in "Fixing a bricked Framework laptop"]]></title><description><![CDATA[
<p>Original author here, and I agree. When overclocking, the most important feature is probably resetting the CMOS with one easy to reach button.<p>I was testing ECC previously in <a href="https://qt.ax/ecc" rel="nofollow">https://qt.ax/ecc</a> and was trying to overclock the RAM to induce faults to confirm ECC was fixing them. Since I was using a cheaper board, I had to use keys to short the CLR_CMOS header and that got old really quick... I didn't ultimately succeed in creating a barely stable overclock that generated a ton of ECC errors, but that was a very awful experience.<p>Having some sort of BIOS recovery is definitely the baseline I'd expect these days, and having two BIOS chips so you can just keep using the device as if nothing had happened is the best solution.</p>
]]></description><pubDate>Tue, 18 Aug 2026 15:23:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=49347046</link><dc:creator>quantum5</dc:creator><comments>https://news.ycombinator.com/item?id=49347046</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49347046</guid></item><item><title><![CDATA[Show HN: TOTP.fyi – debugging tool for app-based 2FA]]></title><description><![CDATA[
<p>This is a tool to debug "app-based 2FA", which almost certainly uses the time-based one-time password (TOTP) algorithm these days. This is the type of 2FA that shows the QR code for your phone to scan, commonly involving apps like Google Authenticator or Authy. The QR code contains a base32-encoded secret and some information about the website and if some other setting is used instead of the default.<p>The way the algorithm works is by dividing the current Unix time by the time step (commonly 30 seconds), and generating an HMAC from that. That's why most codes expire twice every minute at :00 and :30. However, to avoid clock synchronization issues, most websites will allow the codes from one or two time windows in the past or future.<p>This tool takes in the base32 secret and generates a bunch of OTPs, past, present, and future to help test those corner cases. By default, it uses the settings that most websites use: SHA-1, 6 digits, 30 second time steps, but those could be changed in the advanced settings.<p>Another use is when testing 2FA enablement repeated or creating throwaway testing accounts on apps that require 2FA setup, but you don't want to pollute your authenticator app with all the test accounts. You can just paste the secret into this tool and get the codes immediately.<p>You can also use this as a crude "authenticator app" since the secret is stored in the URL hash and you can bookmark that. This is probably more suitable for scripts that create test accounts with 2FA than a long term solution for your important accounts.<p>While it's a bit niche, I built this tool to address the pain points I ran into when testing TOTP, and I hope you'll also find it useful or fun to play around with. You can enter any random base32 string to see it in action. I find it quite fun to reduce the time step to 1 or 2 seconds and watch the codes scroll by with that overengineered animation...<p>This is a simple frontend JavaScript app and the source code is available at <a href="https://github.com/quantum5/totp">https://github.com/quantum5/totp</a>.</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=43105805">https://news.ycombinator.com/item?id=43105805</a></p>
<p>Points: 2</p>
<p># Comments: 0</p>
]]></description><pubDate>Wed, 19 Feb 2025 18:49:45 +0000</pubDate><link>https://totp.fyi/</link><dc:creator>quantum5</dc:creator><comments>https://news.ycombinator.com/item?id=43105805</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43105805</guid></item><item><title><![CDATA[Passkeys, a faster more secure way to log in to the Stripe Dashboard]]></title><description><![CDATA[
<p>Article URL: <a href="https://stripe.com/blog/passkeys-a-faster-more-secure-way-to-log-in-to-the-stripe-dashboard">https://stripe.com/blog/passkeys-a-faster-more-secure-way-to-log-in-to-the-stripe-dashboard</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=40431480">https://news.ycombinator.com/item?id=40431480</a></p>
<p>Points: 2</p>
<p># Comments: 0</p>
]]></description><pubDate>Tue, 21 May 2024 17:45:16 +0000</pubDate><link>https://stripe.com/blog/passkeys-a-faster-more-secure-way-to-log-in-to-the-stripe-dashboard</link><dc:creator>quantum5</dc:creator><comments>https://news.ycombinator.com/item?id=40431480</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=40431480</guid></item><item><title><![CDATA[On BGP Route Selection and High Availability via Anycast]]></title><description><![CDATA[
<p>Article URL: <a href="https://quantum5.ca/2023/12/21/bgp-route-selection-high-availability-anycast/">https://quantum5.ca/2023/12/21/bgp-route-selection-high-availability-anycast/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=38725837">https://news.ycombinator.com/item?id=38725837</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Thu, 21 Dec 2023 19:50:58 +0000</pubDate><link>https://quantum5.ca/2023/12/21/bgp-route-selection-high-availability-anycast/</link><dc:creator>quantum5</dc:creator><comments>https://news.ycombinator.com/item?id=38725837</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=38725837</guid></item><item><title><![CDATA[New comment by quantum5 in "Show HN: How did your computer reach my server?"]]></title><description><![CDATA[
<p>> BGP is the protocol that gives the Internet its shape, and you can’t directly speak it yourself.<p>It's actually surprisingly easy to get an ASN for yourself and speak BGP. If you find building something like this tool interesting, you should give it a try. I wrote an introduction of sorts earlier (<a href="https://qt.ax/asn" rel="nofollow noreferrer">https://qt.ax/asn</a>) if that interests you.</p>
]]></description><pubDate>Tue, 05 Dec 2023 20:40:41 +0000</pubDate><link>https://news.ycombinator.com/item?id=38536626</link><dc:creator>quantum5</dc:creator><comments>https://news.ycombinator.com/item?id=38536626</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=38536626</guid></item><item><title><![CDATA[New comment by quantum5 in "What I wish I knew when I got my ASN"]]></title><description><![CDATA[
<p>The whole BGP process with a private ASN that the ISP strips out and replace with their own ASN on the Internet is how "BYOIP" (bring your own IP) usually works.</p>
]]></description><pubDate>Sat, 14 Oct 2023 17:15:49 +0000</pubDate><link>https://news.ycombinator.com/item?id=37882317</link><dc:creator>quantum5</dc:creator><comments>https://news.ycombinator.com/item?id=37882317</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=37882317</guid></item><item><title><![CDATA[New comment by quantum5 in "What I wish I knew when I got my ASN"]]></title><description><![CDATA[
<p>You don't actually need an ASN to get PI though? You can use PI just fine with BYOIP. Actually... I don't think you are even required to announce them on the Internet.</p>
]]></description><pubDate>Sat, 14 Oct 2023 02:08:19 +0000</pubDate><link>https://news.ycombinator.com/item?id=37877536</link><dc:creator>quantum5</dc:creator><comments>https://news.ycombinator.com/item?id=37877536</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=37877536</guid></item><item><title><![CDATA[New comment by quantum5 in "What I wish I knew when I got my ASN"]]></title><description><![CDATA[
<p>(original author here)<p>Note that ARIN NRPM 4.10 now requires the requested range to be used <i>exclusively</i> for IPv6 transition and not anything else.<p>As for full table, several providers I recommended in the original post are able to do a full table for less than $10/month. You can also join an IX and ask nicely for transit from other members. Some may even offer you free transit the moment you join.</p>
]]></description><pubDate>Fri, 13 Oct 2023 16:06:35 +0000</pubDate><link>https://news.ycombinator.com/item?id=37872121</link><dc:creator>quantum5</dc:creator><comments>https://news.ycombinator.com/item?id=37872121</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=37872121</guid></item><item><title><![CDATA[New comment by quantum5 in "Metric Time"]]></title><description><![CDATA[
<p>I am curious which leap day system you use for the French Republican calendar. Most popular versions of the calendar I see floating around just use the Gregorian leap year system, which I don't like because it yields the wrong results in the year the calendar was in use. Yet, I don't see mental math as a viable option when using the original date-of-equinox method used during the revolution.</p>
]]></description><pubDate>Fri, 13 Oct 2023 01:00:22 +0000</pubDate><link>https://news.ycombinator.com/item?id=37865221</link><dc:creator>quantum5</dc:creator><comments>https://news.ycombinator.com/item?id=37865221</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=37865221</guid></item><item><title><![CDATA[Journey and lessons from running a mirroring service at home]]></title><description><![CDATA[
<p>Article URL: <a href="https://quantum5.ca/2023/05/28/introducing-my-own-mirroring-service-mirror.quantum5.ca/">https://quantum5.ca/2023/05/28/introducing-my-own-mirroring-service-mirror.quantum5.ca/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=36102116">https://news.ycombinator.com/item?id=36102116</a></p>
<p>Points: 27</p>
<p># Comments: 1</p>
]]></description><pubDate>Sun, 28 May 2023 08:10:20 +0000</pubDate><link>https://quantum5.ca/2023/05/28/introducing-my-own-mirroring-service-mirror.quantum5.ca/</link><dc:creator>quantum5</dc:creator><comments>https://news.ycombinator.com/item?id=36102116</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=36102116</guid></item><item><title><![CDATA[ARM Assembly: ∞ Ways to Return (2017)]]></title><description><![CDATA[
<p>Article URL: <a href="https://quantum5.ca/2017/10/19/arm-ways-to-return/">https://quantum5.ca/2017/10/19/arm-ways-to-return/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=34720416">https://news.ycombinator.com/item?id=34720416</a></p>
<p>Points: 66</p>
<p># Comments: 20</p>
]]></description><pubDate>Thu, 09 Feb 2023 06:29:13 +0000</pubDate><link>https://quantum5.ca/2017/10/19/arm-ways-to-return/</link><dc:creator>quantum5</dc:creator><comments>https://news.ycombinator.com/item?id=34720416</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=34720416</guid></item></channel></rss>