Hacker News Reader

Comment by KennyFromIT | Hacker News Reader

Messages like these are so sad to read. The world will never realize how many people are working tirelessly behind the scenes to keep society moving forward.

Cheers to all of the silent (and sometimes not so silent) people that continue to give of themselves to make this world a more wonderful place in their own little way. You all are awesome and we literally couldn't go on with our way of life without you.

View on HN

I call this "Postel decentralisation": everyone thinks there's some kind of system or institution making everything work, but in fact there's just a guy doing it all on his own.

> but in fact there's just a guy doing it all on his own

"Sometimes magic is just someone spending more time on something than anyone else might reasonably expect." -Teller

Interestingly, you seem to be the only person on the World Wide Web to ever have used that phrase (three times over three years?), but it's such a perfect description of such a common phenomenon that I'm pretty sure its propagation could save hours of time in typing for nerds on the Web.

Ironic, that. I'm happy to be the one person trying to coin this phrase.

I'd be wary of colliding with Postel's Law, which I depend on much more often than I'd like. But otherwise agree!

I think that's intentional? Postel's Law is about robustness, as is the "decentralisation" formulation of it.

Relevant: http://ccs.mit.edu/papers/CCSWP197/CCSWP197.html

Postel picked up the role of number coordinator because it needed to be done.

Also see RFC 2468, written in remembrance of Jon Postel.

https://tools.ietf.org/html/rfc2468

In reality it works nothing like this though. People like to think that all of these companies and downstream projects depend on this maintainer, but realistically they would have no problem switching to a fork or doing it internally.

Using his work as-is from upstream is just the path of least resistance. If nobody picks up dhcpd maintenance companies will have no problem carrying forks and more than likely the open source community will quickly converge around a future implementation.

This isn’t comparable to some sole manufacturer or anything like that. It’s similar instead to someone publishing blueprints for basic things and everyone using them because of time saved because redoing them from scratch is tedious and wouldn’t have much of a point.

That's both true and wrong at the same time.

Sure all the big companies that relied on dhcpcd will rewrite it. But still the loss of one opensource project has a major impact on the economy. You mention the part of time saved by the company. Sure, but that goes longer than that.

For instance, in Android, since Android 6, they stopped using dhcpcd and decided to use their own DHCP client. 5 releases later, Android's DHCP client still don't support storing leases (or any feature that has less than 20% usage really). Sure that's just one packet, but the most user-deployed OS in the world has an additional RTT when connecting to WiFi, because of using internal DHCP client rather than a FLOSS-driven one.

Let's do back of the napkin computation: This adds like 0.5s when connecting. I'd say that personnally I'm connecting manually to WiFi (and thus wait for WiFi to connect) maybe once a week. K, worldwide I'd say once a month. There are 3B active Android devices. I'd say mean salary in those 3B is 1USD/h. If my computation is correct ( ((3*1000*1000*1000)*0.5*12)/3600 ), that makes a society cost of Android NOT using dhcpcd of 5M$ per year.

Now, let's go to the mirror successful part of dhcpcd, still at Google. Chromebooks are using dhcpcd as their DHCP client. Considering what happened on Android, I'll assume that if Chromebooks weren't using dhcpcd, they wouldn't use leases either. There are maybe 100M Chromebooks worldwide, but they are mostly centered in the US where salary is higher, but Chromebooks are mostly for students, so let's make it 5USD/h. But on a Chromebook you connect "manually" to WiFi every day (every time you open your laptop pretty much). That means that the existence of dhcpcd is a gain for society of 25M$ per year ( ( ((100*1000*1000)*0.5*365)/3600)*5 ).

So, yes, if nobody picks up dhcpcd maintenance, companies will have no problem carrying on. It doesn't mean that we, as a society wouldn't have lost a lot.

PS: I'm definitely not trying to put a price on Roy Marple's life. But if someone would try, it would be incredibly high.

This assumes behavior on both sides of the implementation and has nothing to do with open source.

> Sure all the big companies that relied on dhcpcd will rewrite it.

Unlikely. dhclient works just fine and carrying a fork of dhcpd will work just fine.

You’re missing my point. When you work on open source and end up with millions to billions of users, everything you do ends up having a huge monetary impact (guess how much Roy’s bugs have cost the economy in lost time). However, that’s just a side effect of software, not you being some unsung hero.

Tons of people need software that does X. Once one or two people have an open source solution to X, people can just use that and move on. That’s a good thing but it doesn’t mean that those one or two people are critical to anything. If they quit, fail, whatever, downstream dependencies will just swap and move on.

Well, they do depend, in the sense of it's listed in their dependencies.

Yes, they could change. But that would be something that had to be chosen, it's not automatic. I'm reminded of openssl: while it wasn't even unmaintained, it was "undermaintained" to the extent of critical security holes, and both the effort to fork it and simplify and the effort to replace with modern from-scratch versions have been a bit fraught.

(Perhaps the real rule as to who the "maintainer" of something like this is "who has to panic when a security hole is reported")

“I always wondered why somebody doesn't do something about that. then I realized I was somebody.”

There's always a relevant XKCD https://xkcd.com/2347/

What does "Postel" refer to?

Presumably Jon Postel, who co-authored many RFCs foundational to the internet such as TCP, IP and DNS. As a single person he was very involved in the internet's architecture.

Today, the "Internet Assigned Numbers Authority" refers to an organization. But for many years it didn't refer to an organization, it was Jon Postel's title.

Upvoted – but don’t forget Joyce K. Reynolds. There’s a lovely anecdote of how the IANA operated in the early 90s in “The story of getting SSH port 22”: https://www.ssh.com/ssh/port

No disrespect toward Ms. Reynolds, certainly! But Mr. Postel had been in that role for 11 years before Ms. Reynolds joined him (1972-1983). Though it turns out that my history is a little fuzzy on the name itself; though Mr. Postel had been in the role for many years, the earliest reference to the name "IANA" that I can find is from 1988. Regardless of whether they were using the name "IANA" in 1972-1983, Mr. Postel was the sole authority during those years, and many of those who were around then would later refer to him as having been the IANA during that time.

Thanks for the historical insight. I hadn’t realised that Jon Postel’s work went that far back. I only came across the Internet in the late nineties – and though I’m aware of the existence of DARPAnet, I don’t really think of the Internet as being a “thing” until the eighties (when most of the common protocol standards I’ve read were written) so I should really find a good book on the subject.

Sadly, I don't have a solid book recommendation about the early Internet.

But, my favorite Internet history book of all time is "IPng: Internet Protocol Next Generation" edited by Scott O. Bradner and Allison Mankin. It's about the development of what would become IPv6, and each chapter is written by a different engineer who was involved in the process. Some chapters were written for the book, and some chapters were publications/reports from the process.

Beautifully worded.

Jon

i mean, even within institutions, it's usually just some person hacking away behind the scene. what else would it be?

A rulebook that says who should be hacking away when, and how/when/from where to get and/or produce more of those people. That long-lived superstructure is what NASA calls a "mission." It's what ensures someone will still be around (with the right expertise, budget, connections, and tools) to fix a satellite when it breaks 50 years later.

It's the closest, or at least one of the closest, things to altruism in this field.

Nadia Eghbal's work and writing about this subject was eye opening for me.

I heard her on a podcast[1] talking about her book Work in Public[2] and loved it, is that the work and writing you're referencing?

If not, are there other pieces you'd recommend?

[1]: https://a16z.com/2020/08/01/working-in-public-communities-op... [2]: https://www.amazon.com/dp/0578675862/

Her first big piece on this was https://www.fordfoundation.org/work/learning/research-report... which i still find better than the book at making the point.

Reply on news.ycombinator.com