Live data from Hacker News

The Internet origin story you know is wrong

wired.com

31–40 of 58 posts

Re: The Internet origin story you know is wrong

#31
post #24

Earlier quoted context omitted.

The myth was that the ARPANET was designed to survive nuclear war. Wikipedia sets this one straight, anyway: https://en.wikipedia.org/wiki/ARPANET > The ARPANET was not started to create a Command and Control System that would survive a nuclear attack, as many now claim. To build such a system was, clearly, a major military need, but it was not ARPA's mission to do this; in fact, we would have been severely criticize…

Don’t have refs to hand but IIRC the concept of packet switching was developed theoretically as a candidate for a military network but was deemed impractical by the Pentagon’s telecoms providers. However, the theory papers were picked up again by the early Arpaner designers

https://www.rand.org/pubs/research_memoranda/RM3420.html (1964)

"We will soon be living in an era in which we cannot guarantee survivability of any single point. However, we can still design systems in which system destruction requires the enemy to pay the price of destroying n of n stations. If n is made sufficiently large, it can be shown that highly survivable system structures can be built—even in the thermonuclear era. "

Re: The Internet origin story you know is wrong

#32
post #4

There are other aspects of the origin story that seem to be myth. For instance, the idea that the Internet was designed to route around damage, and could also treat censorship as a form of damage, and therefore it was resistant to censorship. I once spent a long weekend reading through the early RFCs. What I found was the obvious recognition of the fact that AT&T, which at the time had a monopoly on telephone service…

For instance, the idea that the Internet was designed to route around damage, and could also treat censorship as a form of damage, and therefore it was resistant to censorship.

Yes. That comment was actually made about USENET, not the ARPAnet. Because USENET really did that. When two USENET nodes connected, they compared lists of message IDs, and each one requested any messages the other had, but they didn't. The result was distributed flooding - everybody eventually got everything in any group to which they subscribed.

If someone censored the messages going across a link, that would prevent the message traveling over that link. But if any other possible path existed, two nodes would eventually compare messages lists, note the missing ID, and transmit the missing message. So censorship was only possible if you controlled all possible connections between two networks.

This came up at Stanford in the 1980s, when some IT administrator (Ralph Gorin?) tried censoring rec.humor.funny. But there was one professor (McCarthy?) who had his own USENET node both on the Stanford network and connecting to the outside. It didn't have much capacity, but as long as there was even one low-bandwidth path, any censored messages would eventually take the slow path and arrive. So censorship was futile.

But so was spam filtering.

Re: The Internet origin story you know is wrong

#33
post #24
post #4

There are other aspects of the origin story that seem to be myth. For instance, the idea that the Internet was designed to route around damage, and could also treat censorship as a form of damage, and therefore it was resistant to censorship. I once spent a long weekend reading through the early RFCs. What I found was the obvious recognition of the fact that AT&T, which at the time had a monopoly on telephone service…

The myth was that the ARPANET was designed to survive nuclear war. Wikipedia sets this one straight, anyway: https://en.wikipedia.org/wiki/ARPANET > The ARPANET was not started to create a Command and Control System that would survive a nuclear attack, as many now claim. To build such a system was, clearly, a major military need, but it was not ARPA's mission to do this; in fact, we would have been severely criticize…

MILNET actually was. It was 5-connected - each node had at least 5 connections to other nodes. Same technology as ARPANET, but DoD-only.

Re: The Internet origin story you know is wrong

#34
Author seems to miss one major point that many tech-journalists seem to miss these days which is the internet is different than the web. I had actually bookmarked the book before but now it doesn't seem very interesting to read.

PS: What the hell is the point of writing a title as aggravating as this? It's almost as if they go out of their way to be insulting! Sheesh!

Re: The Internet origin story you know is wrong

#35
post #4

There are other aspects of the origin story that seem to be myth. For instance, the idea that the Internet was designed to route around damage, and could also treat censorship as a form of damage, and therefore it was resistant to censorship. I once spent a long weekend reading through the early RFCs. What I found was the obvious recognition of the fact that AT&T, which at the time had a monopoly on telephone service…

A packet-switched network is less necessarily centralized than a circuit-switched network.

This is not actually true. The AT&T Long Lines network was originally very decentralized. When it was first fully automated, there was no central control point. There were 10 regional control centers, but they were not essential to most calls. Eventually there was central control, out of Bedminster, Pennsylvania. Originally all it did was collect data and send out new routing tables every few minutes. It didn't process any calls. Previously the routing tables had been fixed, changed maybe once a month. Calling pattern changes on holidays were a serious cause of overload. AT&T used to run ads asking people to make their Xmas calls earlier in the day.

There's "A History of Science and Engineering in the Bell System"[1], written by the old-timers at the AT&T breakup to record how all the old stuff worked. A general understanding of how the more advanced electromechanical switching systems worked is useful in designing high-rel systems. Number 4 and Number 5 crossbar systems had system reliability much higher than component reliability. In the entire history of the Bell System, no electromechanical central office was ever out of service for more than 30 minutes, other than due to a natural disaster or major fire. That record has not been maintained in the computer era.

[1] https://www.amazon.com/History-Engineering-Science-Bell-Syst...

Re: The Internet origin story you know is wrong

#36
post #4

There are other aspects of the origin story that seem to be myth. For instance, the idea that the Internet was designed to route around damage, and could also treat censorship as a form of damage, and therefore it was resistant to censorship. I once spent a long weekend reading through the early RFCs. What I found was the obvious recognition of the fact that AT&T, which at the time had a monopoly on telephone service…

When John Gilmore said in the early 01990s, "The Net interprets censorship as damage and routes around it," he was talking about USENET, not the internet. USENET is a peer-to-peer gossip network, like Bitcoin. John Gilmore is a techno-utopian, a libertarian, and a technologist; he was Sun employee #5, he designed BOOTP (the basis of DHCP), and he wrote substantial parts of GCC and GDB. This saying of his was quoted in Time Magazine in 01993 https://web.archive.org/web/20210408023213/https://kirste.us... which seems to be a bit confused about the relationship between the internet and USENET. I don't know how far back it dates, but I don't think he made it up for the article.

The claim is, strictly speaking, true of gossip networks like USENET. If node A talks to nodes B and C, which also talk to each other and also to another node D, and node A utters a message that node B chooses not to distribute, the situation from D's perspective is precisely the same as if node B were temporarily down. Node C will still get the message (directly from A, rather than from B) and node D will still get it from C.

You can find a lot of technologists who are also techno-utopians and libertarians making grandiose claims about the decentralizing influence of the internet in the cypherpunks archives from 01992 and 01993. At the time, the list was hosted on Hoptoad, John Gilmore's personal machine, in his house.

I think there are a lot of ways that the internet architecture is less centralized than the PSTN that aren't related to packet-switching versus circuit-switching. Regular users aren't allowed to run traceroute on the PSTN (though some phone phreaks used to do that sort of thing, and MPLS means traceroute means less than it used to). The PSTN doesn't have a public whois database. It won't delegate even a class C of 256 phone numbers to your PBX for local use (though that was becoming difficult to get on the internet too by the mid-01990s), much less 2^48 phone numbers. You can't get a PSTN AS number so you can multihome your PBX to two different long-distance providers. Historically there was no mapping from logical names to phone numbers, so to call someone on the phone you had to dial an area code and exchange that identified their local phone company and its exchange, so user-visible addresses were inherently owned by local regulated monopoly providers, not by users themselves.

Moreover, ideologically the deployment of new applications on the PSTN was centrally controlled and administered by the phone company, and they would run on the "switches" in the buildings without windows, while on the internet any random person could write and run an experimental server on their node, at least if their sysadmin was cool with it. Until the Carterfone decision of 01968 it was illegal in the US to plug even third-party telephones into the PSTN, and direct-connect modems didn't become legal until 01975. After that, lots of innovative applications of the PSTN were actually deployed in a decentralized way, such as answering machines, fax machines, and BBSes, but they were very limited in the features they could provide.

By comparison, the early internet was wildly decentralized.

Packet-switching does mean that a single computer can directly talk to an arbitrarily large number of other computers at once, instead of just however many circuits its connection supports. But a graph of degree three can already be a robustly cyclic connected graph, so three circuits per node would be enough. Of course, the phone company only provided most users with one at a time, with thousands of milliseconds of latency to establish a new circuit.

So it wasn't so much that we imposed decentralization retroactively on the work of the 01970s and 01980s. It was more that we observed that it had resulted.

Re: The Internet origin story you know is wrong

#37
post #4

There are other aspects of the origin story that seem to be myth. For instance, the idea that the Internet was designed to route around damage, and could also treat censorship as a form of damage, and therefore it was resistant to censorship. I once spent a long weekend reading through the early RFCs. What I found was the obvious recognition of the fact that AT&T, which at the time had a monopoly on telephone service…

maybe all the arpanet design docs are not public?

Well, a lot of the early RFCs have been lost.

Re: The Internet origin story you know is wrong

#38
post #2

This reads like a college student who was assigned a book review assignment and wrote it an hour before class.

Don't most of these tabloid-tier rags?

That is absolutely insulting—to procrastinating college kids. Most modern journalism feels like it was scraped five minutes ahead of time from another site and barely changed.

Re: The Internet origin story you know is wrong

#39
Perhaps it would be accurate to say that Arpanet provided the vision and ultimately protocols to create one unified network, while the online communities (BBS seems the wrong term to me) created many of the _applications_ (in concept, no code survived) that would eventually run on that unified network. Even that's not really true because NNTP was a strictly Internet thing and SMTP email existed before most online communities did. Heck you may as well throw in Prestel and Minitel while you're at it. Honestly the online communities seem like the Dodo of the modern internet, not the Coelacanth. For example I was able to get through those decades without using any of them (save for a little bit of CIS required because something...something...Microsoft developer...something needed it).

Re: The Internet origin story you know is wrong

#40
post #4

There are other aspects of the origin story that seem to be myth. For instance, the idea that the Internet was designed to route around damage, and could also treat censorship as a form of damage, and therefore it was resistant to censorship. I once spent a long weekend reading through the early RFCs. What I found was the obvious recognition of the fact that AT&T, which at the time had a monopoly on telephone service…

"Decentralization" has many meanings and often organizational and technical decentralization are conflated.

The decentralization talked about in 1990's Wired was both because the technology wasn't controlled by a single company (unlike competitors like AOL or MSN).

Post reply on HN