HN Hug of death ?

letting the days go by

check the html :)

The review of life choices happens in our heads when we click this link on the main HN page.

(sigh) I'm just thinking those thoughts right now.

also

    ssh funky.nondeterministic.computer

Nice! Dr. Horrible would be proud of this geeky tribute:

  > tracepath -m60 bad.horse
  [...]
  16:  bad.horse                                            81.233ms asymm 10
  19:  he.rides.across.the.nation                           85.365ms asymm 11
  20:  he.got.the.application                               96.067ms asymm 13
  23:  it.needs.evaluation                                 112.377ms asymm 15
  24:  a.heinous.crime                                     114.826ms asymm 17
  25:  a.show.of.force                                     120.842ms asymm 18
  26:  bad.horse                                           133.089ms asymm 20

Read the green text

Mine too. Maybe it's CGNAT.

This is not my beautiful home-page.

You can also do out-of-order HTML streaming without JavaScript using declarative shadow DOM. For example:

https://lamplightdev.com/blog/2024/01/10/streaming-html-out-...

Anecdotally, I've run a bunch of traceroutes and reverse traceroutes to different locations and they tend to follow the same AS paths — although sometimes the traceroute will surface more routing through your ISP (especially from college networks). In general you are correct, though, and I would love to explain more about hot-potato vs. cold-potato (and other interesting routing decisions) in the future. Either way, the results the reverse traceroute provides are good enough for the purposes of explaining the internet, IMO!

FYI what you described is hot-potato routing: each AS gets rid of it as soon as possible.

You may think this is unfair, and yes, it is, but it's also quite logical when you consider you don't know where the packet is going in the destination AS. If you have a network spanning Berlin and Hamburg and the packet is going to a different network that also spans Berlin and Hamburg, and you interconnect at both points, and you don't know which city it's actually going to, handing it off at the closest interconnect doesn't risk round-tripping it for no good reason.

Dealt with something similar 25 years ago as a new guy at a large bank.

They had a DS3 to AT&T for Internet and a T1 to Sprint for 'back-up' in case the primary went down. Same AS, but 75% of the Internet traffic perferred the Sprint return route.

Our 'network guy' couldn't figure out why everyone in this company (100k employees) was experiencing worse than dial-up performance at their desks. Took about 10 minutes to see what the issue was (using reverse traceroute from a looking glass server out there somewhere).

As soon as we fixed that, ran into the next problem. Dude built a caching proxy server on a Sun e4500 with ONE disk.

Got to be a hero for a little bit lol.

somewhat better now! added a bit more concurrency. lesson learned: use tokio next time