Retrotechtacular: The Tyranny Of Large Numbers

Although much diminished now, the public switched telephone network was one of the largest machines ever constructed. To make good on its promise of instant communication across town or around the world, the network had to reach into every home and business, snake along poles to thousands of central offices, and hum through the ether on microwave links. In its heyday it was almost unfathomably complex, with calls potentially passing through thousands of electronic components, any of which failing could present anything from a minor annoyance to a matter of life or death.

The brief but very interesting film below deals with “The Tyranny of Large Numbers.” Produced sometime in the 1960s by Western Electric, the manufacturing arm of the Bell System, it takes a detailed look at the problems caused by scaling up systems. As an example, it focuses on the humble carbon film resistor, a component used by the millions in various pieces of telco gear. Getting the manufacturing of these simple but critical components right apparently took a lot of effort. Initially made by hand, a tedious and error-prone process briefly covered in the film, Western Electric looked for ways to scale up production significantly while simultaneously increasing quality.

While the equipment used by the Western engineers to automate the production of resistors, especially the Librascope LGP-30 computer that’s running the show, may look quaint, there’s a lot about the process that’s still used to this day. Vibratory bowl feeders for the ceramic cores, carbon deposition by hot methane, and an early version of a SCARA arm to sputter gold terminals on the core could all be used to produce precision resistors today. Even cutting the helical groove to trim the resistance is similar, although today it’s done with a laser instead of a grinding wheel. There are differences, of course; we doubt current resistor manufacturers look for leaks in the outer coating by submerging them in water and watching for bubbles, but that’s how they did it in the 60s.

The productivity results were impressive. Just replacing the silver paint used for terminal cups with sputtered gold terminals cut 16 hours of curing time out of the process. The overall throughput increased to 1,200 pieces per hour, an impressive number for such high-reliability precision components, some of which we’d wager were still in service well into the early 2000s. Most of them are likely long gone, but the shadows cast by these automated manufacturing processes stretch into our time, and probably far beyond.

Continue reading “Retrotechtacular: The Tyranny Of Large Numbers”

Forgotten Internet: Giving (or Getting) The Finger

Hey, you know that guy in accounting, Marco? If you want to find out more about him, you’d probably go surf LinkedIn or maybe a social media site. Inside a company, you might look on instant messaging for a profile and even find out if he is at his desk or away. But back in the 1970s, those weren’t options. But if Marco was on the computer system, maybe you could finger him. While that sounds strange to say today, Finger was a common service provided by computer services at the time. It was like a LinkedIn profile page for the 1970s.

Based on RFC 742, Finger was the brainchild for [Les Earnest]. From a user’s point of view, you put a few files in your home directory (usually .project and .plan; both hidden files), and when someone “fingered” you, they’d see some human-friendly output about your account like your name and office location, if you were logged in or not, and the contents of your project and plan files.

Modern versions may also show your public PGP key and other data. You could usually put a file in your home directory called .nofinger if you wanted to stop people from fingering you.

Continue reading “Forgotten Internet: Giving (or Getting) The Finger”

Illustrated Kristina with an IBM Model M keyboard floating between her hands.

Keebin’ With Kristina: The One With The DIY Homing Keys

r/keebgirlies Is Totally a Thing Now

When [coral-bells] posted her first build to r/mechanicalkeyboards, she likely felt some trepidation. After all this is reddit we’re talking about, so right away you’ve got two layers of male-domination hobby.

Most of a lovely plant-themed keyboard.
Image by [coral-bells] via reddit
What she likely didn’t expect was to be upvoted into the tens of thousands, or to receive such a response from other girlies who came out of the woodwork to share their builds.

And so r/keebgirlies was born, and already has a few thousand members. This is a brand-new subreddit for women and non-binary folks who are into mechanical keyboards. As it says in the sidebar, men are welcome but limited to the comments for now, so don’t go trying to post your builds. The girlies are currently seeking moderators, so give that some thought.

As for [coral-bells]’ lovely build, this is an Epomaker MS68 with MMD Vivian V2 switches, and those flowery keycaps are from Etsy. She is currently waiting for supplies to mod a Yunzii AL66, but wants to build a kit at some point.

Continue reading “Keebin’ With Kristina: The One With The DIY Homing Keys”

The FTC Take Action, Is Time Finally Up For John Deere On Right To Repair?

Over the last decade we have brought you frequent reports not from the coolest of hackerspaces or the most bleeding edge of engineering in California or China, but from the rolling prairies of the American Midwest. Those endless fields of cropland waving in the breeze have been the theatre for an unlikely battle over right to repair, the result of which should affect us all. The case of FEDERAL TRADE COMMISSION, STATE OF ILLINOIS, and STATE OF MINNESOTA, v. DEERE & COMPANY  relates to the machinery manufacturer’s use of DRM to restrict the repair of its products, and holds the promise to end the practice once and for all.

This is being written in Europe, where were an average person asked to name a brand that says “America”, they might reach for the familiar; perhaps Disney, McDonalds, or Coca-Cola. These are the flag-bearers of American culture for outsiders, but it’s fair to say that none of them can claim to have built the country. The green and yellow Deere tractors on the other hand represent the current face of a company with nearly two hundred years of farming history, which by virtue of producing some of the first mass-produced plows, had perhaps the greatest individual role in shaping modern American agriculture and thus indirectly the country itself. To say that Deere is woven into the culture of rural America is something of an understatement, agricultural brands like Deere have an enviable customer base, the most loyal of any industry.

Thus while those green and yellow tractors are far from the only case of DRM protected repairability, they have become the symbolic poster child for the issue as a whole. It’s important to understand then how far-reaching it is beyond the concerns of us technology and open-source enthusiasts, and into something much more fundamental. Continue reading “The FTC Take Action, Is Time Finally Up For John Deere On Right To Repair?”

Hackaday Links Column Banner

Hackaday Links: January 26, 2025

Disappointing news this week for those longing for same-hour Amazon delivery as the retail giant tapped the brakes on its Prime Air drone deliveries. The pause is partially blamed on a December incident at the company’s Pendleton, Oregon test facility, where two MK30 delivery drones collided in midair during light rain conditions. A Bloomberg report states that the crash, which resulted in one of the drones catching fire on the ground, was due to a software error related to the weather. As a result, they decided to ground their entire fleet, which provides 60-minute delivery to test markets in Arizona and Texas, until a software update can be issued.

Continue reading “Hackaday Links: January 26, 2025”

Networking History Lessons

Do they teach networking history classes yet? Or is it still too soon?

I was reading [Al]’s first installment of the Forgotten Internet series, on UUCP. The short summary is that it was a system for sending files across computers that were connected, intermittently, by point-to-point phone lines. Each computer knew the phone numbers of a few others, but none of them had anything like a global routing map, and IP addresses were still in the future. Still, it enabled file transfer and even limited remote access across the globe. And while some files contained computer programs, others files contained more human messages, which makes UUCP also a precursor to e-mail.

What struck me is how intuitively many of this system’s natural conditions and limitations lead to the way we network today. From phone numbers came the need for IP addresses. And from the annoyance of having know how the computers were connected, and to use the bang notation to route a message from one computer to another through intermediaries, would come our modern routing protocols, simply because computer nerds like to automate hassles wherever possible.

But back to networking history. I guess I learned my networking on the mean streets, by running my own Linux system, and web servers, and mail servers. I knew enough networking to get by, but that mostly focused on the current-day application, and my beard is not quite grey enough to have been around for the UUCP era. So I’m only realizing now that knowing how the system evolved over time helps a lot in understanding why it is the way it is, and thus how it functions. I had a bit of a “eureka” moment reading about UUCP.

In physics or any other science, you learn not just the status quo in the field, but also how it developed over the centuries. It’s important to know something about the theory of the aether to know what special relativity was up against, for instance, or the various historical models of the atom, to see how they inform modern chemistry and physics. But these are old sciences with a lot of obsolete theories. Is computer science old enough that they teach networking history? They should!