igjeff

I think the spec is supposed to be one ball per second, but I guess that's not really adhered to.

Tangentially, I think it'd be interesting to use something like this to explain the networking concepts of throughout, latency, jitter, baud vs bits per second, symbol rate and bits per symbol.

You can find analogous examples in the main video to compare to all of those concepts.

Nothing in IPv6 says you have to stop dividing at the /64 level.

There has been some hardware that takes a bit of a performance hit when doing route lookups that are longer than /64 in the past, but if you're doing this all in software on an end host, that's not an issue.

Go ahead and divide up that /64 to smaller blocks for your classification purposes, you'll still have plenty.

I'm curious what you're looking for in OSM. I looked at highway=street_lamp and the results were....let's say "sparse".

It is probably pretty much straight down...until it impacts the flat surface of the ship.

As others have mentioned, the poles in Louisville are owned mostly by a mix of AT&T (about 40%) and our local power utility (Louisville, Gas & Electric; LG&E) (about 60%).

But pole ownership really isn't relevant, here. The right for new companies to attach to the poles isn't in doubt, and isn't part of this dispute.

The dispute here is part of the make ready process...who has the right to rearrange the wires already on the pole to make space for the new attacher? Even the right to have the space made available isn't in doubt...it's merely who does the actual work of making it available.

While you're not wrong...all of the issues you mention are, in general, issues that have to be dealt with. Those issues are, however, all addressed as part of the permitting process to be allowed to attach to the poles.

What's at issue in Louisville is the make ready process after the permit has been issued (after it has been determined that the poles have enough room and are strong enough to handle the new wires).