Hacker Newsnew | past | comments | ask | show | jobs | submit | divbzero's commentslogin

This xkcd is featured as the maintainer’s user icon on GitHub:

https://github.com/millert


and it's also the inspiration for the logo of sudo https://www.sudo.ws/

“Machine Room Temperature” from Todd C. Miller’s website:

https://www.millert.dev/therm/

Server exhaust fan temperature was typically 94°F (ranged 92°F to 96°F) over the previous week and has climbed to 97°F.


But, on the whole, the server seems to be doing well enough for something near the top of HN. The website is served by nginx and appears to be mostly static pages.

This anecdote from history feels timely given the recent shift of Apple’s iWork suite (Pages, Numbers, Keynote) from being bundled with Macs to being a freemium subscription.

https://www.macrumors.com/2026/01/28/apple-updates-keynote-n...


Instead of trying to think of just any animal, I found it easier to add a constraint…

1. Animal that starts with A

2. Animal that starts with B

3. Animal that starts with C

(I also appreciated the easter eggs: “Are you Australian?” and “You listed both dingos and dogs, so I gave you the benefit of the doubt, but there's disagreement on whether the dingo is its own species of canid, a subspecies of grey wolf, or simply a breed of dog.”)


Without considering if it’s a distinct species, a dingo is descended from the same wolf population as dogs.

They are feral dogs. IE wolf -> domesticated dog -> became wild again.


What comes after C?

I went by groups and families of animals.

In another half century, will this sound like “How compilers impact the formation of assembly coding skills” sounds today?

Hinges on whether this new high level -> low level transformation becomes reliable enough to build watertight abstractions on top of it. If AI code becomes good enough that you don't have to worry about the low-level representation 99.9...% of the time, absolutely. But we're pretty far from that at the moment and it's impossible to say where things will be in another 50 years.

What we could do is increase the number of IP addresses available. Just imagine if we enlarged the IP address space from 32 bits to 128 bits: Every device on the Internet could have a unique IP address!

That sounds apocalyptic. What if street addresses were unambiguous? Think of the security implications. Anyone could just walk into your house. Much better to just have "local street 10 b" etc.

You could install a door. Then again, who am I telling people what to do.

Interesting idea! But I think such upgrade would take years, if not decades, to get widely adopted.

Or maybe a century.

The thing is, this upgrade you two are praising is designed to satisfy the original article's needs and no one else's.

Why do all those devices need to talk to each other btw? It's never specified. Is it a user need or a data collection/spyware need?

In a world where security articles make the news saying that you could obtain access to something IF the attacker already has local root and IF the moon is in a quarter phase and IF the attacker is physically present in the same room as the machine and this means the sky is falling...

... we should be questioning why disparate devices on unrelated home networks need to talk to each other.


Peer-to-peer requires that devices from different home networks talk to each other. Gaming, audio/video chat, screen sharing, file sharing (torrents), etc.

The whole idea of the internet from the beginning is that devices can talk with each other.


The need is real. You are a service provider. You need to manage equipment at customer sites. You need to access them simultaneously. But all the customers are using the same subnet... If Bell gave out cellphones with the same phone number, how can you call anybody? But they still do. Many devices have cloud access, but every manufacturer is different. It is a nightmare at scale.

There are completely legitimate usecases that are not "spyware" related for true end-to-end connectivity

For security there is still the firewall


The issue is that we DO NOT want every device to have a publicly routable IP address. It does make sense for some machines, but you probably don't want your your Internet-of-Shit devices to have public IPs. Of course you can firewall the devices, but you are always one misconfiguration or bug away from exposing devices that should not be exposed, when a local network is a more natural solution for what is supposed to remain local in the first place.

- NAT is not a firewall. A firewall is a firewall. - NAT is not better than a firewall. - NAT does not replace a firewall.

And we could represent the addresses with hex numbers separated by : instead of decimal numbers separated by .

That’d be kinda inconvenient with respect to the port number syntax in URLs, though.

I heard there's some people working on a system that allows you to use names, but it seems to be very poorly designed and cause of a lot of outages.

We did. It's called IPv6. It's 20 years old and still not usable universally. At the high end, like enterprise or telcos, it's fantastic. But at the grass roots level of residential and small businesses, it's still a nightmare.

I think that was the joke

They should have left it as “Amazon 5-Star” with nearly 5-star products.

The local Amazon Fresh is closed this afternoon with a sign reading:

  We are closed
  for the
  remainder of 
  the day.

  We apologize for any
  inconvenience. Please come
  back tomorrow during our
  normal business hours.

The extant Tower of Hercules is based on the original plans for Pharos. The Tower of Hercules stands 55 meters tall—half the height of Pharos—and has remained intact for about 2,000 years.

https://en.wikipedia.org/wiki/Tower_of_Hercules


Wow, thanks for sharing this

> Primary sources:

> Maskelyne’s notes: https://doi.org/10.1098/rstl.1775.0050

> Hutton’s notes: https://doi.org/10.1098/rstl.1778.0034

> Cavendish’s notes on his own experiment: https://doi.org/10.1098/rstl.1798.0022

I got to reproduce Cavendish’s experiment when I was a student. Love that we can easily read the primary source today, archived and indexed by DOI.


> Using the stars as a reference, Maskelyne’s team found that the plumb lines on either side of the mountain pointed just 0.0152 degrees apart.

I'm really interested in knowing how they could get such a precise measurement (even accounting for errors), especially in the field (outdoor). There's no figure depicting the apparatus they used, I wonder how it looked like.

Sometimes, I just ponder at how ignorant I am. If I was tasked with the same assignment, I'd definitely fail and this was performed 250 ago!


Maybe something similar to a vernier caliper.

From Wikipedia:

> The first caliper with a secondary scale, which contributed extra precision, was invented in 1631 by the French mathematician Pierre Vernier (1580–1637).[1] Its use was described in detail in English in Navigatio Britannica (1750) by mathematician and historian John Barrow.[2] While calipers are the most typical use of vernier scales today, they were originally developed for angle-measuring instruments such as astronomical quadrants.

https://en.wikipedia.org/wiki/Vernier_scale

So it would have been a contemporaneous technique with that initial angle measurement, and the use of a Vernier scale for angular measurements would have itself been common.


They had a vertical 'Zenith Telescope' that looked at the same star from two locations. They measured how far from vertical it shifted in the magnified field of view. https://en.wikipedia.org/wiki/Ramsden_surveying_instruments#... Similar instrumends measured the wobble of the Earth's axis. https://en.wikipedia.org/wiki/International_Latitude_Service

I'd love to know what a sufficiently high precision plumb bob is like. Is it very tall? How on Earth does one calibrate it?

Broadly speaking, you want it as tall as possible, usually we're talking a few stories high, so 20m or so.

Without the attracting masses on either side you can set it swinging and measure the period, which lets you compute the restoring force in the wire.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: