Paul Miller
paulmillr.com · Personal blog · on HN since 2012
Paul Miller is a developer who writes about cryptography, JavaScript libraries, Telegram, and iOS networking.
What HN saysHN commenters link his Telegram post as background and cite his cryptography work, including a post on deterministic signatures.
15HN people shared it
4linked it in comments
13stories submitted
516story points
2 years agolast shared
2012people per year2026
Most-shared posts
- 1Deterministic signatures are not your friends3 people · 3 points · first shared 2025 · discussion on HN
- 2iOS 14, Big Sur and DNS over HTTPS/TLS3 people · 2 points · first shared 2020 · discussion on HN
- 3The story of Telegram or “Why you shouldn’t listen to Hacker News”2 people · 22 points · first shared 2013 · 18 comments on HN
- 4Chokidar 3: How to save 32TB of traffic every week with one NPM package (2019)2 people · 9 points · first shared 2019 · discussion on HN
- 5Noble-secp256k1: Learning fast elliptic-curve cryptography in JavaScript2 people · 7 points · first shared 2020 · discussion on HN
- 6Using Dark Mode in CSS with MacOS Mojave1 people · 344 points · first shared 2018 · 124 comments on HN
- 7Probability of acceptance of pull requests1 people · 127 points · first shared 2013 · 56 comments on HN
- 8MyNewPassport1 people · 1 points · first shared 2015 · discussion on HN
- 9Noble Cryptography1 people · 1 points · first shared 2023 · discussion on HN
- 10Simple description of popular software licenses1 people · first shared 2012
What HN people wrote when they linked it
matthewdgreen · 2025-03-28
On the one hand this is true. Particularly the quantum stuff is mostly pointless. On the other hand, failure to incorporate fresh entropy into systems — turning them deterministic - is one of the rising crypto bug classes. The best solutions will mix the two.
Recent example: https://paulmillr.com/posts/deterministic-signatures/
judge2020 · 2020-12-08
iOS and MacOS technically have this (requires a profile[0]) but Microsoft will probably drag their feed on this for the next 2 years with the amount of enterprise customers they have to keep happy; and, given that the network adapter config is still based on Aero controls, they're probably in no rush to add more configuration options before upgrading it to Metro controls.
0: https://paulmillr.com/posts/encrypted-dns/
vincvinc · 2015-01-22
Here's a start of what you need to know;
http://paulmillr.com/posts/the-story-of-telegram/
JoshTriplett · 2012-02-01
First of all, let me start with the disclaimer that no summary substitutes for reading the licenses in question. The MIT and BSD licenses require almost no effort to understand. The GPL (v2 or v3) makes for fairly easy reading, and seems intentionally written in a way that non-lawyers can easily understand and apply. The same mostly goes for the LGPL and Apache licenses, though the use cases for the latter don't become immediately evident at first glance.
For a quick overview of the most popular licenses, I really like this diagram: http://paulmillr.com/posts/simple-description-of-popular-software-lice…
That diagram rather effectively captures the most important differences between the licenses: copyleft of various strengths (GPL versus LGPL versus BSD/MIT), the added protections in the GPLv3 and LGPLv3 versus the v2 licenses, the rationale for the Apache license rather than MIT/BSD, and the subtle difference between BSD3 and BSD2 that you mostly don't need to care about.
If you want a more extensive analysis, I'd suggest reading the FSF's license list, which provides a rather comprehensive list, including specific issues with various licenses, and links to more information about common license features: https://www.gnu.org/licenses/license-list.html
One critically important disclaimer about that list: ignore everything it says about the GFDL (GNU "Free" Documentation License) and stay far away from that license. Always license your documentation under the same…