<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: cbrews</title><link>https://news.ycombinator.com/user?id=cbrews</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Tue, 07 Jul 2026 23:36:42 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=cbrews" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by cbrews in "Immich 3.0"]]></title><description><![CDATA[
<p>If you can get all the images into a filesystem (on a NAS or similar server share), you can use the External Libraries feature in Immich (<a href="https://docs.immich.app/features/libraries/" rel="nofollow">https://docs.immich.app/features/libraries/</a>).  This allows it to crunch through the media files via an async import job (a bit more reliable than having to directly upload via the web api).<p>In my setup, I exclusively use the external libraries feature, pointed at a read-only share from my NAS mounted onto my Immich server. (The external libraries are set to resynchronize to the database every few hours).  This means I can manage all my media assets myself without worrying about Immich accidentally corrupting them, and if I eventually move off Immich, I just have a single folder of media files organized by date to port around.<p>The only downside is that I don't directly upload any media files directly to Immich, but that's okay.  I have Syncopoli sync files from my phones (on a scheduled cadence) to an intermediary server which organizes and cleans exif data from media files before dropping it into its permanent home on my NAS share.  No manual steps to get photos from my phone to my Immich instance!</p>
]]></description><pubDate>Thu, 02 Jul 2026 23:00:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=48768483</link><dc:creator>cbrews</dc:creator><comments>https://news.ycombinator.com/item?id=48768483</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48768483</guid></item><item><title><![CDATA[New comment by cbrews in "Ask HN: What's the current best local/open speech-to-speech setup?"]]></title><description><![CDATA[
<p>Thanks for sharing this! I'm going to put this on my list to play around with. I'm not really an expert in this tech, I come from the audio background, but recently was playing around with streaming Speech-to-Text (using Whisper) / Text-to-Speech (using Kokoro at the time) on a local machine.<p>The most challenging part in my build was tuning the inference batch sizing here.  I was able to get it working well for Speech-to-Text down to batch sizes of 200ms.  I even implement a basic local agreement algorithm and it was still very fast (inferencing time, I think, was around 10-20ms?).  You're basically limited by the minimum batch size, NOT inference time.  Maybe that's a missing "secret sauce" suggested in the original post?<p>In the use case listed above, the TTS probably isn't a bottleneck as long as OP can generate tokens quickly.<p>All this being said a wrapped model like this that is able to handle hand-offs between these parts of the process sounds really useful and I'll definitely be interested in seeing how it performs.<p>Let me know if you guys play with this and find success.</p>
]]></description><pubDate>Fri, 23 Jan 2026 23:49:06 +0000</pubDate><link>https://news.ycombinator.com/item?id=46739544</link><dc:creator>cbrews</dc:creator><comments>https://news.ycombinator.com/item?id=46739544</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46739544</guid></item><item><title><![CDATA[New comment by cbrews in "HealthEquity to Replace Passwords with Passkeys"]]></title><description><![CDATA[
<p>Apparently, following a recent serious data breach[0], HealthEquity is moving forward with an authentication change to deprecate username/password entirely in favor of Passkeys (webauthn resident key implementation).<p>This struck me as a bit of "news" given the security posture being taken here.  I haven't seen any other institution force adoption of Passkeys as the primary authentication mechanism to access their services; I've mostly seen 2FA/MFA implementations with Passkeys as an optional/additional authentication mechanism.  Like many folks here[1], I've been hesitant to fully adopt passkeys as a primary authentication mechanism until the credential exchange specification[2] (which allows users to export/import keys from one credential storage platform to another) is finalized and better supported across the different credential stores.<p>From this page:<p><pre><code>  Can I opt out of using a passkey?
  No. Once passkey login is rolled out to your account, you’ll need to use it to access your benefits—either through the mobile app or on the web. Traditional login options won’t be available.
</code></pre>
[0] <a href="https://www.healthequity.com/breach" rel="nofollow">https://www.healthequity.com/breach</a><p>[1] <a href="https://news.ycombinator.com/item?id=42548719">https://news.ycombinator.com/item?id=42548719</a><p>[2] <a href="https://fidoalliance.org/specifications-credential-exchange-specifications/" rel="nofollow">https://fidoalliance.org/specifications-credential-exchange-...</a></p>
]]></description><pubDate>Tue, 29 Jul 2025 21:14:27 +0000</pubDate><link>https://news.ycombinator.com/item?id=44728328</link><dc:creator>cbrews</dc:creator><comments>https://news.ycombinator.com/item?id=44728328</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44728328</guid></item><item><title><![CDATA[HealthEquity to Replace Passwords with Passkeys]]></title><description><![CDATA[
<p>Article URL: <a href="https://www.healthequity.com/library/replacing-passwords-with-passkeys">https://www.healthequity.com/library/replacing-passwords-with-passkeys</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=44728245">https://news.ycombinator.com/item?id=44728245</a></p>
<p>Points: 6</p>
<p># Comments: 1</p>
]]></description><pubDate>Tue, 29 Jul 2025 21:04:40 +0000</pubDate><link>https://www.healthequity.com/library/replacing-passwords-with-passkeys</link><dc:creator>cbrews</dc:creator><comments>https://news.ycombinator.com/item?id=44728245</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44728245</guid></item><item><title><![CDATA[New comment by cbrews in "2021 IETF Working Group Sessions"]]></title><description><![CDATA[
<p>The 2021 IETF (Internet Engineering Task Force) working group sessions are ongoing this week, discussing many of the new proposals coming out of the working groups for internet protocol changes.<p>Even without being registered for the conference, you can stream the audio in real-time by connecting to the audio stream directly:<p><pre><code>  <audio controls>
    <source src="https://icecast-ietf.conf.meetecho.com:8443/room6.mp3" type="audio/mpeg">
  </audio></code></pre></p>
]]></description><pubDate>Mon, 08 Nov 2021 14:40:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=29149707</link><dc:creator>cbrews</dc:creator><comments>https://news.ycombinator.com/item?id=29149707</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29149707</guid></item><item><title><![CDATA[2021 IETF Working Group Sessions]]></title><description><![CDATA[
<p>Article URL: <a href="https://datatracker.ietf.org/meeting/112/agenda">https://datatracker.ietf.org/meeting/112/agenda</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=29149687">https://news.ycombinator.com/item?id=29149687</a></p>
<p>Points: 3</p>
<p># Comments: 1</p>
]]></description><pubDate>Mon, 08 Nov 2021 14:37:49 +0000</pubDate><link>https://datatracker.ietf.org/meeting/112/agenda</link><dc:creator>cbrews</dc:creator><comments>https://news.ycombinator.com/item?id=29149687</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29149687</guid></item></channel></rss>