<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: connorlanigan</title><link>https://news.ycombinator.com/user?id=connorlanigan</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 13 Jul 2026 08:28:21 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=connorlanigan" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by connorlanigan in "Show HN: Cryptographically random strings with zero clicks"]]></title><description><![CDATA[
<p>Whenever I need random data for something (as a password, a token, a seed, a server-side secret...) and google for a generator, I always end up on random.org, entering the same configuration, clicking the same checkboxes and clicking the same button. This takes an unnecessary amount of time.<p>I built this website that uses secure defaults and immediately presents you with a string of random data generated locally in your browser. It uses the Web Crypto API [1] for obtaining strong randomness. It's running on Cloudflare to be as fast as possible.<p>[1] <a href="https://developer.mozilla.org/en-US/docs/Web/API/Web_Crypto_API" rel="nofollow">https://developer.mozilla.org/en-US/docs/Web/API/Web_Crypto_...</a></p>
]]></description><pubDate>Thu, 15 Aug 2019 08:48:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=20703619</link><dc:creator>connorlanigan</dc:creator><comments>https://news.ycombinator.com/item?id=20703619</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=20703619</guid></item><item><title><![CDATA[Show HN: Cryptographically random strings with zero clicks]]></title><description><![CDATA[
<p>Article URL: <a href="https://random.connorlanigan.com">https://random.connorlanigan.com</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=20703612">https://news.ycombinator.com/item?id=20703612</a></p>
<p>Points: 3</p>
<p># Comments: 3</p>
]]></description><pubDate>Thu, 15 Aug 2019 08:48:15 +0000</pubDate><link>https://random.connorlanigan.com</link><dc:creator>connorlanigan</dc:creator><comments>https://news.ycombinator.com/item?id=20703612</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=20703612</guid></item><item><title><![CDATA[New comment by connorlanigan in "The PGP Problem"]]></title><description><![CDATA[
<p>The safety number is only partly per-conversation. If you compare safety numbers of different conversations, you'll discover that one half of them is always the same (which half that is changes depending on the conversation). This part is the fingerprint of your personal key.<p>The Signal blog states that "we designed the safety number format to be a sorted concatenation of two 30-digit individual numeric fingerprints." [1]<p>The way I understand it, you could simply share your part of the number on your website, but Moxie recommends against it, since this fingerprint changes between reinstalls.<p>[1] <a href="https://signal.org/blog/safety-number-updates/" rel="nofollow">https://signal.org/blog/safety-number-updates/</a></p>
]]></description><pubDate>Wed, 17 Jul 2019 11:10:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=20458204</link><dc:creator>connorlanigan</dc:creator><comments>https://news.ycombinator.com/item?id=20458204</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=20458204</guid></item></channel></rss>