<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: lrvick</title><link>https://news.ycombinator.com/user?id=lrvick</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Tue, 23 Jun 2026 15:57:32 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=lrvick" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by lrvick in "Three of our worst VC stories"]]></title><description><![CDATA[
<p>Sure, you can keep paying $200/mo to Anthropic forever, and accept heavy censorship on the types of tasks you can do (e.g. malware research), accept no privacy, and accept rate limiting and the requirement of internet access at all times.<p>Or buy $2400 of GPU today to get you something close to get you within 10% of Opus 4.6 on coding benchmarks, that pays for itself in 1 year, AND you can work with private code and data offline as you like with no censorship or restrictions.<p>The value proposition of Anthropic is comically bad to anyone that understands how to insert PCI-E cards into a motherboard and install linux.</p>
]]></description><pubDate>Mon, 08 Jun 2026 00:07:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=48439948</link><dc:creator>lrvick</dc:creator><comments>https://news.ycombinator.com/item?id=48439948</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48439948</guid></item><item><title><![CDATA[New comment by lrvick in "Three of our worst VC stories"]]></title><description><![CDATA[
<p>Qwen3.6 27b is ~10% worse than Opus 4.6 to be fair (though at a fraction of the size), but in exchange you get to run offline with complete privacy, no rate limiting, no refusals from any task, be it malware research or otherwise. Also my favorite reason: controlling the means of production.<p>Those are all well worth being a month behind frontier models.</p>
]]></description><pubDate>Mon, 08 Jun 2026 00:02:34 +0000</pubDate><link>https://news.ycombinator.com/item?id=48439919</link><dc:creator>lrvick</dc:creator><comments>https://news.ycombinator.com/item?id=48439919</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48439919</guid></item><item><title><![CDATA[New comment by lrvick in "Three of our worst VC stories"]]></title><description><![CDATA[
<p>Not really much to write up.<p>Insert 2-4 $1200 r9700 GPUs in a Linux 7.0.0+ machine with 64GB+ of DDR4-5 memory, fire up llama.cpp, and connect with any OpenAI compatible tools.<p>A free public anonymous LLM like BigPickle can easily set up the software for you if in doubt.</p>
]]></description><pubDate>Sun, 07 Jun 2026 23:51:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=48439855</link><dc:creator>lrvick</dc:creator><comments>https://news.ycombinator.com/item?id=48439855</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48439855</guid></item><item><title><![CDATA[New comment by lrvick in "Three of our worst VC stories"]]></title><description><![CDATA[
<p>Yeah, first "real" startup and we were absolutely desperate for some seed cash. Mistakes were made.<p>These days I have significantly higher self respect, always have multiple income and funding sources, and a lot more protective of my time.</p>
]]></description><pubDate>Sat, 06 Jun 2026 18:41:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=48427706</link><dc:creator>lrvick</dc:creator><comments>https://news.ycombinator.com/item?id=48427706</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48427706</guid></item><item><title><![CDATA[New comment by lrvick in "Three of our worst VC stories"]]></title><description><![CDATA[
<p>Being capable of sshing to servers to maintain things sure was.</p>
]]></description><pubDate>Sat, 06 Jun 2026 18:31:47 +0000</pubDate><link>https://news.ycombinator.com/item?id=48427613</link><dc:creator>lrvick</dc:creator><comments>https://news.ycombinator.com/item?id=48427613</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48427613</guid></item><item><title><![CDATA[New comment by lrvick in "Three of our worst VC stories"]]></title><description><![CDATA[
<p>In the end my co-founders and investors wanted to sell to a single specific political party exclusively. I chose not to participate as it did not align with my goals, and started a small IT company instead. The original project was dead within a couple months of me leaving given no one else had any idea what ssh was.</p>
]]></description><pubDate>Sat, 06 Jun 2026 08:30:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=48422721</link><dc:creator>lrvick</dc:creator><comments>https://news.ycombinator.com/item?id=48422721</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48422721</guid></item><item><title><![CDATA[New comment by lrvick in "Three of our worst VC stories"]]></title><description><![CDATA[
<p>Maybe 2 months. I have mostly used the Qwen series, and currently running Qwen3.6 27B for programming and debugging and Qwen3.6 35B for speed and research. Both punch way way above their weight and replaced Qwen3.5 122B for me. Qwen 3.6 27B even is, for my workloads, preferable over Big Pickle (GLM-4.6) which is the only  large third party model I have used extensively for reference and comparison as it is free and requires no signup or PII via OpenCode. My go to agent solution though is Charm Crush.</p>
]]></description><pubDate>Sat, 06 Jun 2026 08:25:56 +0000</pubDate><link>https://news.ycombinator.com/item?id=48422691</link><dc:creator>lrvick</dc:creator><comments>https://news.ycombinator.com/item?id=48422691</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48422691</guid></item><item><title><![CDATA[New comment by lrvick in "Three of our worst VC stories"]]></title><description><![CDATA[
<p>Buy a few GPUs so you can skip the Claude subscription, and never have to worry about rate limits, privacy, or refusals. Will pay for itself with a small team in a few months.<p>I mostly work on custom from scratch Linux operating systems and packages across dozens of languages.<p>I do 100% of my AI work today using two AMD r9700 pro GPUs on a 10yo pc I pulled out of an old arcade machine.<p>AI subscriptions only make sense for people who cannot build a basic home computer.</p>
]]></description><pubDate>Sat, 06 Jun 2026 06:32:46 +0000</pubDate><link>https://news.ycombinator.com/item?id=48422018</link><dc:creator>lrvick</dc:creator><comments>https://news.ycombinator.com/item?id=48422018</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48422018</guid></item><item><title><![CDATA[New comment by lrvick in "Three of our worst VC stories"]]></title><description><![CDATA[
<p>I once had a VC ask to meet my founders and I for his morning breakfast at a run down diner in texas. So we fly out from Florida pitch deck in hand, and meet him at his booth.<p>We pull out the deck, he says "Do not need that. How many paying customers do you have?"<p>Given we were at MVP stage and were running a public sentiment analysis driven social media search engine using our published academic AI work (15 years ago) we said "None yet. The capital to build the paid portion of our product, which is popular, is why we are here."<p>As he eats his eggs he goes "Come back when you have a hundred or more paying customers" and sent us packing .<p>Not even a 5 minute interaction with people he asked to fly out to pitch him, and were not even allowed to pitch.<p>I expect rejection by default at an early stage, but that one was particularly mean.<p>It will forever remain my go to example of a meeting that could have been an email.<p>One excited investor we did find for another project ended up being the now famous con man "Michael Prozer" who got on who wants to marry a millionaire using forged bank records and proceeded to get actual capital based on this lie until he was arrested for fraud.<p>My opinion of VCs is still... recovering. The bar is in hell.</p>
]]></description><pubDate>Sat, 06 Jun 2026 06:16:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=48421925</link><dc:creator>lrvick</dc:creator><comments>https://news.ycombinator.com/item?id=48421925</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48421925</guid></item><item><title><![CDATA[New comment by lrvick in "Uber's $1,500/month AI limit is a useful signal for AI tool pricing"]]></title><description><![CDATA[
<p>This is madness. I bought my daily driver GPUs for $3k, and they run often 24/7 solving complex bugs and problems for me that would have previously taken months to fix. No rate limits, no censorship or refusal to work on security issues, and complete privacy. Also even when my internet is down they keep on working.<p>Stop giving Anthropic money and figure out how to take the same money to buy some GPUs, and physically insert them into workstations. It is not that hard, I promise.</p>
]]></description><pubDate>Fri, 05 Jun 2026 08:45:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=48409776</link><dc:creator>lrvick</dc:creator><comments>https://news.ycombinator.com/item?id=48409776</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48409776</guid></item><item><title><![CDATA[New comment by lrvick in "Are we self-sovereign PKI yet?"]]></title><description><![CDATA[
<p>So 0.1% of the internet is protected by Ed25519 signatures because of this move. Meanwhile PGP has had Ed25519 support for years, with hardware security key support.<p>OpenBSD does fantastic work, but you and I both know it will never have any significant adoption on the web at this point.<p>Try to convince an actual Linux distro running any significant portion of the web they should stop using Ed25519 via PGP smartcards and use Ed25519 via signify exposing their keys to system memory (and thus malware) instead, with no key discovery protocol, for unspecified reasons.<p>Would love to see a threat modeling case for that.<p>At this point you have shown your hand. You hate PGP so much you would make security for everyone worse to get rid of it. There is no reasonable threat model to support your position.</p>
]]></description><pubDate>Fri, 29 May 2026 07:19:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=48320077</link><dc:creator>lrvick</dc:creator><comments>https://news.ycombinator.com/item?id=48320077</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48320077</guid></item><item><title><![CDATA[New comment by lrvick in "Are we self-sovereign PKI yet?"]]></title><description><![CDATA[
<p>At this point I can only conclude you are a troll, but if you are actually serious, I challenge you to prove it. I put in the work in the community for my side of this debate.<p>I would suggest you pick one of the mainline Linux distros that relies on PGP and make a detailed RFC with a plan to downgrade their security to your non standard minisign/ssh solution with private keys exposed in system memory as you propose, and make a convincing case why it is worth it and what advantages they get for doing so.<p>Let me know if you do. I am sure it will be a great case study.</p>
]]></description><pubDate>Fri, 29 May 2026 01:26:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=48317844</link><dc:creator>lrvick</dc:creator><comments>https://news.ycombinator.com/item?id=48317844</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48317844</guid></item><item><title><![CDATA[New comment by lrvick in "Are we self-sovereign PKI yet?"]]></title><description><![CDATA[
<p>> PGP is a bunch of theatre there and distros should use minisign instead.<p>Okay so drop the IETF standard, web of trust, smartcard support, and external key discovery mechanisms to prove the whole keychain was not swapped out with a fake one, and just have everyone generate minisign keys exposed to system memory  with no trust link backwards, and then sign things with probably the same algorithms. But then we cannot sign commits or code reviews with minisign because non standard, so i guess use ssh keys for those, and then maintain multiple keychains for each person.<p>Minisign is strictly worse in every way. Your camp will never convince Linux maintainers to switch with this pitch.<p>Many of us actually do verify the web of trust, extensively. I have many Linux maintainers in my own keychain independent from their usage in linux distros. Minisign has no such key distribution and accountability system.</p>
]]></description><pubDate>Thu, 28 May 2026 23:24:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=48316943</link><dc:creator>lrvick</dc:creator><comments>https://news.ycombinator.com/item?id=48316943</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48316943</guid></item><item><title><![CDATA[New comment by lrvick in "Are we self-sovereign PKI yet?"]]></title><description><![CDATA[
<p>I could name a few off the top of my head, some of which have audited my teams work, but I do not want to put specific people on blast. Most cryptographers I know tend to prefer math to internet controversy and I do not blame them.<p>That said protonmails lead cryptographer has been quite public about his support of the refresh and helping lead some efforts <a href="https://proton.me/blog/openpgp-crypto-refresh" rel="nofollow">https://proton.me/blog/openpgp-crypto-refresh</a><p>I have dozens of more examples of high risk orgs with cryptography teams relying on PGP I am compiling for my post right now. Added a bunch of extra ones just for you.<p>Honestly from my side of the table, it is the anti-pgp camp that appears to be the loud minority. The world quietly runs on "dead" PGP technology so deeply that any calls for a complete replacement without any compatibility or trust transition path are clearly under-researched and should not be taken seriously.<p>I have a hard time imagining many cryptographers deeply aware of the impossibility of any rapid transition away from PGP would suggest we abandon the migration to secure modern ciphers now.<p>A lot of people would like to -eventually- move away from openssl too, myself among them, but not updating to openssl 4 and beyond in the short term would be a world burn kind of move.</p>
]]></description><pubDate>Thu, 28 May 2026 08:42:34 +0000</pubDate><link>https://news.ycombinator.com/item?id=48306329</link><dc:creator>lrvick</dc:creator><comments>https://news.ycombinator.com/item?id=48306329</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48306329</guid></item><item><title><![CDATA[New comment by lrvick in "Are we self-sovereign PKI yet?"]]></title><description><![CDATA[
<p>So you are saying that the solution is that we go to the majority of active and reputable PGP keyholders, Linux maintainers, and tell them to stop signing the binaries that run the internet, and just yolo, because that worked so well for NPM?<p>I really hope I am misunderstanding you.</p>
]]></description><pubDate>Thu, 28 May 2026 03:41:34 +0000</pubDate><link>https://news.ycombinator.com/item?id=48304211</link><dc:creator>lrvick</dc:creator><comments>https://news.ycombinator.com/item?id=48304211</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48304211</guid></item><item><title><![CDATA[New comment by lrvick in "Are we self-sovereign PKI yet?"]]></title><description><![CDATA[
<p>Ah yes. That post. People send it to me all the time. It is my favorite.<p>It proposes that dissidents and security researchers from all countries from a wide range of backgrounds and beliefs on privacy, should all just accept the terms of service of their pick of two US based surveillance capitalism mega-corporations, trust they do not have any insiders or vulns, then reveal their identity to cell carriers in most countries, to get signal up and running, whose terms of service they must also accept, and then with the help of two corporations and their proprietary software supply chains, they can then submit an encrypted security vulnerability.<p>I legitimately laugh every time at the US corpo-brained takes in posts like these.<p>TL;DR: "Just let the US tech giants handle all identity and communication for the whole internet. What could go wrong? Super secure companies with great uptime like Microsoft GitHub can sign our commits for us and of course Google and Apple pinky swears to disobey executive orders to serve tampered updates of Signal to select devices. It will be fine."<p>The people that use their PGP keys to sign and securely distribute damn well near every binary that powers the internet are mostly in Europe, and not big fans of letting centralized and mostly proprietary US institutions control their online identity, let alone trusting them to not use a supply chain attack to read their private security correspondence. I for one have found a pile of serious vulns, including in GnuPG, and I do not have a Signal account and never will as I disagreed with the terms of service of Apple Google and Signal. Anyone that does not want plaintext disclosures would be wise to publish PGP keys for people like me. Thankfully most major tech firms still do, even if only to appease non US citizens and my fellow decorpoed americans.<p>Encrypted email is the only neutral decentralized and IETF standard comms tool we have. I say that as also a big fan of Matrix and would love to see it or something decentralized like it standardized but right now email is the standard so the snowdens and security researchers of the world should use PGP with modern ciphers and learn how to do it offline when doing high risk comms.<p>Even so, on the other side of this, having setup bug bounty programs for many orgs, the PGP encrypted/signed submissions from reputable folks were always the really spicy shit I would not want anywhere near a modern smartphone, and I would always decrypt them offline with a smartcard for good reason. I would not even consider being party to a bug bounty program that does not publish a PGP key to be maximally inclusive, even if they hate PGP.<p>Also re tarsnap. It does not even support smartcards, so just shove your private key for your entire filesystem in system memory, and back it up to a conventional password manager I guess? WTF.<p>Meanwhile with PGP you generate a key on a smartcard, you provide the public key to duplicity, and you can do backups without ever exposing your private key.<p>The alternatives suggested are strictly worse by any metric, and fail to understand the threat models of existing solutions.</p>
]]></description><pubDate>Thu, 28 May 2026 03:07:49 +0000</pubDate><link>https://news.ycombinator.com/item?id=48303947</link><dc:creator>lrvick</dc:creator><comments>https://news.ycombinator.com/item?id=48303947</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48303947</guid></item><item><title><![CDATA[New comment by lrvick in "Are we self-sovereign PKI yet?"]]></title><description><![CDATA[
<p>> Is your pitch that the people who call out problems with PGP don’t have suggested replacements for workflows?<p>Yep. I have read every single blog post I can find from critics. Most several times. As have most people that work on this stuff. Some were partly relevant when they were posted and even less relevant today. All of them completely missed the boat on the problems PGP solves that none of the alternative do, or have any serious suggestions for migration paths or standards changes.<p>I will be quoting most of those posts in a blog post in the next couple weeks on <a href="https://distrust.co" rel="nofollow">https://distrust.co</a>.<p>Most of them have corporate alternatives to sell you which have no chance of adoption by standards bodies.</p>
]]></description><pubDate>Thu, 28 May 2026 01:09:03 +0000</pubDate><link>https://news.ycombinator.com/item?id=48302975</link><dc:creator>lrvick</dc:creator><comments>https://news.ycombinator.com/item?id=48302975</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48302975</guid></item><item><title><![CDATA[New comment by lrvick in "Are we self-sovereign PKI yet?"]]></title><description><![CDATA[
<p>They are compatible enough. It is a firefox vs internet explorer situation.<p>If you want to use shiny new ciphers, expect to have limited reach to those on legacy tools. Tradeoffs each user can make for themselves.<p>That is not an OpenPGP problem, that is just the nature of distributed systems.</p>
]]></description><pubDate>Thu, 28 May 2026 01:05:27 +0000</pubDate><link>https://news.ycombinator.com/item?id=48302943</link><dc:creator>lrvick</dc:creator><comments>https://news.ycombinator.com/item?id=48302943</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48302943</guid></item><item><title><![CDATA[New comment by lrvick in "Are we self-sovereign PKI yet?"]]></title><description><![CDATA[
<p>New software that is compatible with any keys generated with good-enough ciphers from the last decade. Compatibility wins.<p>If we are going to play the appeal to authority game, I could just as easily challenge you to find any willing to publicly point out any serious issues with the current PQ focused OpenPGP standards with implementations using libraries by accomplished cryptographers. I am sure they would appreciate constructive feedback. Encourage them to join the specification process and recommend specific alternatives and migration paths.<p>I also wonder if we could find any that would not scrap TLS DNS and a lot of IETF protocols that run the internet today if they could. Decentralized protocols are messy but anything that tries to replace them without first taking the time to understand the current uses and migration path has no hope of success, and that is brutally difficult political work full of careful compromises.<p>Famous cryptographers have long advocated for things like tcpcrypt, and I even agree with them, but it will probably never happen. Too disruptive. We are still rolling out IPv6 FFS. When faced with an established global internet, compatible lower disruption migration steps are the only way forward as most experienced security engineers would begrudgingly agree.<p>Cryptographers should absolutely focus on the security of the ciphers, but when it comes to applications, and human privacy and security goals, and human to human trust bootstrapping protocols, the conversation has to get a lot wider. It is normally dominated by security engineers like us close to the hands on use cases, and the people doing the hard work in the working groups and tool development circles that understandably wish to quietly read different takes from a safe distance.</p>
]]></description><pubDate>Thu, 28 May 2026 00:47:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=48302798</link><dc:creator>lrvick</dc:creator><comments>https://news.ycombinator.com/item?id=48302798</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48302798</guid></item><item><title><![CDATA[New comment by lrvick in "Are we self-sovereign PKI yet?"]]></title><description><![CDATA[
<p>GnuPG is not the final say for PGP any more than IE6 was the final say for the web. Migrating off IE6 took a while and so will migrating legacy systems off GnuPG. New users of PGP are thankfully mostly using new gen reasonably secure tools.<p>Just like IE6, GnuPG abandoned the global standardization processes and in doing so forced an expensive migration to successors.<p>Global changes on the internet take decades in part because of all the people far removed from the process spreading outdated information and demanding we give up on standards and move the whole world to centralized solutions that do not even solve the same problems, like Java Applets, Adobe Flash, or Signal.<p>Meanwhile those standardizing and rolling out longer term solutions roll their eyes and keep doing the work.</p>
]]></description><pubDate>Wed, 27 May 2026 23:24:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=48302161</link><dc:creator>lrvick</dc:creator><comments>https://news.ycombinator.com/item?id=48302161</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48302161</guid></item></channel></rss>