<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: phlip9</title><link>https://news.ycombinator.com/user?id=phlip9</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sat, 29 Aug 2026 02:22:28 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=phlip9" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[Show HN: Lexe – Self-Custodial Lightning Nodes in TEEs, Python and Rust SDKs]]></title><description><![CDATA[
<p>Lexe is next-generation Bitcoin infrastructure: self-custodial wallets and SDKs that are easy to use, always online, and hosted for free. Your keys are protected by secure enclaves, allowing your node to stay online 24/7 and receive payments reliably.<p>New in this release:<p>- First ever public release of Lexe Wallet on the App Store and Google Play<p>- Human Bitcoin Addresses (BIP 353): receive Bitcoin at ₿yourname@lexe.app<p>- Python and Rust SDKs, published to PyPI and crates.io<p>- Open source node, app, and SDKs published at <a href="https://github.com/lexe-app/lexe-public" rel="nofollow">https://github.com/lexe-app/lexe-public</a></p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47532761">https://news.ycombinator.com/item?id=47532761</a></p>
<p>Points: 5</p>
<p># Comments: 3</p>
]]></description><pubDate>Thu, 26 Mar 2026 16:47:45 +0000</pubDate><link>https://blog.lexe.app/public-launch/</link><dc:creator>phlip9</dc:creator><comments>https://news.ycombinator.com/item?id=47532761</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47532761</guid></item><item><title><![CDATA[New comment by phlip9 in "QUIC for the kernel"]]></title><description><![CDATA[
<p>I'm hoping we get there too with io_uring. It looks like the last few kernel release have made a lot of progress with zero-copy TCP rx/tx, though NIC support is limited and you need some finicky network iface setup to get the flow steering working<p><a href="https://docs.kernel.org/networking/iou-zcrx.html" rel="nofollow">https://docs.kernel.org/networking/iou-zcrx.html</a></p>
]]></description><pubDate>Thu, 31 Jul 2025 22:50:09 +0000</pubDate><link>https://news.ycombinator.com/item?id=44751088</link><dc:creator>phlip9</dc:creator><comments>https://news.ycombinator.com/item?id=44751088</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44751088</guid></item><item><title><![CDATA[New comment by phlip9 in "Show HN: Whirlwind – Async concurrent hashmap for Rust"]]></title><description><![CDATA[
<p>Benches look promising! My main concern is validating correctness; implementing good concurrency primitives is always challenging. Have you looked into testing against a purpose-built concurrency model checker like tokio-rs/loom [1] or awslabs/shuttle [2]? IMO that would go a long way towards building trust in this impl.<p>[1] <a href="https://github.com/tokio-rs/loom">https://github.com/tokio-rs/loom</a>
[2] <a href="https://github.com/awslabs/shuttle">https://github.com/awslabs/shuttle</a></p>
]]></description><pubDate>Tue, 05 Nov 2024 19:10:49 +0000</pubDate><link>https://news.ycombinator.com/item?id=42054331</link><dc:creator>phlip9</dc:creator><comments>https://news.ycombinator.com/item?id=42054331</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42054331</guid></item><item><title><![CDATA[New comment by phlip9 in "Asterinas: OS kernel written in Rust and providing Linux-compatible ABI"]]></title><description><![CDATA[
<p>Super cool project. Looks like the short-term target use-case is running a Linux-compatible OS in an Intel TDX guest VM with a significantly safer and smaller TCB. Makes sense. This way you also postpone a lot of the HW driver development drudgery and instead only target VM devices.</p>
]]></description><pubDate>Tue, 15 Oct 2024 23:19:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=41854116</link><dc:creator>phlip9</dc:creator><comments>https://news.ycombinator.com/item?id=41854116</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41854116</guid></item><item><title><![CDATA[New comment by phlip9 in "Adapting Plan 9's listen to GNU Guix"]]></title><description><![CDATA[
<p>Exactly, it should use a separator. Consider a more realistic example, like http280 or h3443. Totally ambiguous.</p>
]]></description><pubDate>Tue, 15 Oct 2024 21:25:53 +0000</pubDate><link>https://news.ycombinator.com/item?id=41853284</link><dc:creator>phlip9</dc:creator><comments>https://news.ycombinator.com/item?id=41853284</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41853284</guid></item><item><title><![CDATA[New comment by phlip9 in "Orphaning bcachefs-tools in Debian"]]></title><description><![CDATA[
<p>Maintenance is much more practical when you use the versions upstream tests in their CI and not whatever mishmash of ancient/silently incompatible deps that each distro separately decides to combine together.</p>
]]></description><pubDate>Sat, 31 Aug 2024 19:22:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=41411210</link><dc:creator>phlip9</dc:creator><comments>https://news.ycombinator.com/item?id=41411210</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41411210</guid></item><item><title><![CDATA[New comment by phlip9 in "Eza: A modern, maintained replacement for ls"]]></title><description><![CDATA[
<p>Can definitely recommend eza (prev. exa). I've used it as an ls replacement for a long time with zero problems. If anyone's using nix home-manager, here's my config for inspiration:<p><pre><code>    programs.eza = {
      enable = true;

      # In list view, include a column with each file's git status.
      git = true;
    };

    programs.bash.shellAliases = {
      ks = "eza";
      sl = "eza";
      l = "eza";
      ls = "eza";
      ll = "eza -l";
      la = "eza -a";
      lt = "eza --tree";
      lla = "eza -la";
    };</code></pre></p>
]]></description><pubDate>Mon, 22 Jul 2024 18:36:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=41038031</link><dc:creator>phlip9</dc:creator><comments>https://news.ycombinator.com/item?id=41038031</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41038031</guid></item><item><title><![CDATA[Atomicless Per-Core Concurrency]]></title><description><![CDATA[
<p>Article URL: <a href="https://mcyoung.xyz/2023/03/29/rseq-checkout/">https://mcyoung.xyz/2023/03/29/rseq-checkout/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=40947045">https://news.ycombinator.com/item?id=40947045</a></p>
<p>Points: 21</p>
<p># Comments: 2</p>
]]></description><pubDate>Fri, 12 Jul 2024 16:28:02 +0000</pubDate><link>https://mcyoung.xyz/2023/03/29/rseq-checkout/</link><dc:creator>phlip9</dc:creator><comments>https://news.ycombinator.com/item?id=40947045</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=40947045</guid></item><item><title><![CDATA[New comment by phlip9 in "The sad state of property-based testing libraries"]]></title><description><![CDATA[
<p>Agreed. A while back I played around with fuzzcheck [1], which let's you write coverage-guided, structure-aware property tests, but the generation is smarter than just slamming a fuzzer's `&[u8]` input into `Arbitrary`. It also supports shrinking, which is nice. Don't know that I would recommend it though. It seemed difficult to write your own `Mutator`s. It also looks somewhat unmaintained nowadays, but I think the direction is worth exploring.<p>[1]: <a href="https://github.com/loiclec/fuzzcheck-rs/">https://github.com/loiclec/fuzzcheck-rs/</a></p>
]]></description><pubDate>Fri, 05 Jul 2024 01:41:29 +0000</pubDate><link>https://news.ycombinator.com/item?id=40879317</link><dc:creator>phlip9</dc:creator><comments>https://news.ycombinator.com/item?id=40879317</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=40879317</guid></item><item><title><![CDATA[New comment by phlip9 in "Show HN: Brioche – A new Nix-like package manager"]]></title><description><![CDATA[
<p>Congrats on the release! I love the focus on devex w/ typescript and autocomplete. That's probably one of my biggest pain points with Nix -- writing any non-trivial package always requires a ripgrep adventure through nixpkgs. Finding the right poorly documented and poorly discoverable derivation attributes is always such a chore.<p>What are your plans for cross-compilation or heavy package customization? One of nixpkgs coolest party tricks imo is that you can just change the stdenv and get a musl static binary or cross-compiled binary.</p>
]]></description><pubDate>Mon, 03 Jun 2024 19:34:20 +0000</pubDate><link>https://news.ycombinator.com/item?id=40566621</link><dc:creator>phlip9</dc:creator><comments>https://news.ycombinator.com/item?id=40566621</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=40566621</guid></item><item><title><![CDATA[New comment by phlip9 in "Viking 7B: open LLM for the Nordic languages trained on AMD GPUs"]]></title><description><![CDATA[
<p>Interesting thought. Maybe an LLM would build deeper insight with only one training language. On the other hand, the model might overfit with just one language -- maybe multilingual models generalize better?</p>
]]></description><pubDate>Wed, 15 May 2024 23:14:10 +0000</pubDate><link>https://news.ycombinator.com/item?id=40373494</link><dc:creator>phlip9</dc:creator><comments>https://news.ycombinator.com/item?id=40373494</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=40373494</guid></item><item><title><![CDATA[New comment by phlip9 in "A simple, (as-of-yet unidentified) asymmetric Authenticated Key Exchange"]]></title><description><![CDATA[
<p>I don't know much about the TKey, but it looks like they have some kind of remote attestation protocol available? (<a href="https://github.com/tillitis/tkey-verification/tree/main/cmd/tkey-verification">https://github.com/tillitis/tkey-verification/tree/main/cmd/...</a>). That's usually how you avoid TOFU.<p>(1) the tillitis CA certifies your TKey device platform. You can now trust that it's running a specific firmware version with some platform pubkey.<p>(2) Your custom software is running and derives a keypair from it's derived secret + program binary hash.<p>(3) Somehow your custom software's pubkey gets locally certified by the platform's pubkey from (1). (not sure what this looks like w/ the TKey)<p>You now have a chain of trust from (1) the tillitis CA -> (3) the TKey device platform pubkey @ some specific firmware version -> (2) your custom software pubkey @ some specific version.<p>Now that we have a trusted pubkey for our service, I would open a secure channel to it via Noise IK or something (<a href="https://noiseexplorer.com/patterns/IK/" rel="nofollow">https://noiseexplorer.com/patterns/IK/</a>). The TKey platform definitely looks a bit anemic so getting this working might be a challenge...</p>
]]></description><pubDate>Wed, 27 Mar 2024 05:37:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=39835986</link><dc:creator>phlip9</dc:creator><comments>https://news.ycombinator.com/item?id=39835986</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=39835986</guid></item><item><title><![CDATA[New comment by phlip9 in "Rep and Ren: A new approach to CLI find, replace, and renaming"]]></title><description><![CDATA[
<p>This looks pretty neat! I especially like how well it composes with other tools.<p>Wonder how well it compares with fastmod [0]? That's what I've been using for large scale codemods/refactors. ripgrep is ofc insanely fast so ripgrep+ren would probably fare favorably.<p>[0]: <a href="https://github.com/facebookincubator/fastmod/">https://github.com/facebookincubator/fastmod/</a></p>
]]></description><pubDate>Sat, 30 Dec 2023 17:21:53 +0000</pubDate><link>https://news.ycombinator.com/item?id=38816860</link><dc:creator>phlip9</dc:creator><comments>https://news.ycombinator.com/item?id=38816860</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=38816860</guid></item><item><title><![CDATA[New comment by phlip9 in "Mozilla sccache: ccache with cloud storage"]]></title><description><![CDATA[
<p>sccache only caches if builds are run from the same absolute path, so indeed different home dirs won't work</p>
]]></description><pubDate>Sun, 24 Dec 2023 18:45:07 +0000</pubDate><link>https://news.ycombinator.com/item?id=38755575</link><dc:creator>phlip9</dc:creator><comments>https://news.ycombinator.com/item?id=38755575</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=38755575</guid></item><item><title><![CDATA[New comment by phlip9 in "CIA: All Foreign Governments"]]></title><description><![CDATA[
<p>They're listed separately as West Bank and Gaza Strip</p>
]]></description><pubDate>Wed, 08 Nov 2023 21:16:21 +0000</pubDate><link>https://news.ycombinator.com/item?id=38197176</link><dc:creator>phlip9</dc:creator><comments>https://news.ycombinator.com/item?id=38197176</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=38197176</guid></item><item><title><![CDATA[New comment by phlip9 in "Winsorized mean"]]></title><description><![CDATA[
<p>A related example out in the wild:<p>Rust's `cargo bench` "winzorizes" the benchmark samples before computing  summary statistics (incl. the mean).<p><a href="https://github.com/rust-lang/rust/blob/master/library/test/src/bench.rs#L150">https://github.com/rust-lang/rust/blob/master/library/test/s...</a></p>
]]></description><pubDate>Wed, 18 Oct 2023 19:03:06 +0000</pubDate><link>https://news.ycombinator.com/item?id=37933177</link><dc:creator>phlip9</dc:creator><comments>https://news.ycombinator.com/item?id=37933177</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=37933177</guid></item><item><title><![CDATA[New comment by phlip9 in "Let's Build a FIPS-Validated Rust Crypto Library"]]></title><description><![CDATA[
<p>100% on board and super happy that `ring` is finally getting some love again (and funding!)<p>For context: the ring repo's been a bit inactive lately and the v0.17 release looked like it stalled out. Thankfully there's been a burst of activity in the past several weeks so I'm feeling a lot better.</p>
]]></description><pubDate>Fri, 22 Sep 2023 23:34:49 +0000</pubDate><link>https://news.ycombinator.com/item?id=37619149</link><dc:creator>phlip9</dc:creator><comments>https://news.ycombinator.com/item?id=37619149</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=37619149</guid></item><item><title><![CDATA[New comment by phlip9 in "Firefox has surpassed Chrome on Speedometer"]]></title><description><![CDATA[
<p>As a serial tab hoarder, Vimium's SHIFT-T tab fuzzy search is what makes it manageable. : )</p>
]]></description><pubDate>Tue, 18 Jul 2023 15:33:49 +0000</pubDate><link>https://news.ycombinator.com/item?id=36774163</link><dc:creator>phlip9</dc:creator><comments>https://news.ycombinator.com/item?id=36774163</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=36774163</guid></item><item><title><![CDATA[New comment by phlip9 in "Tell HN: ChatGPT is fantastic for finding and solving issues in logs"]]></title><description><![CDATA[
<p>Yeah it's pretty awesome! I used GPT-4 last week to fix my corrupted SSD. Granted I already narrowed down the kernel logs to a few suspicious lines, but I just pasted those 10 lines in and asked for a fix. Pasting in GPT's arcane `fsck` incantations and boom -- fixed SSD. Saved me an hour or two of hassle reading man pages and stack overflow posts.</p>
]]></description><pubDate>Thu, 20 Apr 2023 17:13:13 +0000</pubDate><link>https://news.ycombinator.com/item?id=35643075</link><dc:creator>phlip9</dc:creator><comments>https://news.ycombinator.com/item?id=35643075</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=35643075</guid></item><item><title><![CDATA[New comment by phlip9 in "Memory Safe Languages in Android 13"]]></title><description><![CDATA[
<p>I think even heartbleed would be mitigated with (safe) Rust. IIRC heartbleed was caused by a missing bounds check, which allowed attackers to read past the message buffer and leak secrets from nearby memory. Safe Rust would just panic (crash) if you tried to slice past the end of the buffer.</p>
]]></description><pubDate>Sat, 03 Dec 2022 02:29:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=33839836</link><dc:creator>phlip9</dc:creator><comments>https://news.ycombinator.com/item?id=33839836</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=33839836</guid></item></channel></rss>