If you’re wondering, as I was, who Amateur Radio Digital Communications is and how they have money to make grants, it’s the foundation that sold a quarter of the 44.0.0.0/8 IPv4 address block, allocated in 1981 for use in amateur radio, to Amazon in 2019 for $109 million.
FS.COM Limited (深圳市飞速创新技术股份有限公司, https://cn.fs.com/) was founded in Shenzhen in 2009. They’ve applied to be listed on the Hong Kong Stock Exchange; here’s the draft prospectus from a month ago:
I liked An Answer for Linda (1961), which shows the work of outward toll operators using mark-sensing call tickets at traditional (3CL) cord switchboards. “Watch Billie closely, as she handles a group of typical calls.”
(I won’t spoil the Answer; you’ll have to watch for yourself.)
RJ45S and RJ45M are ordering codes for so-called “registered jack” configurations for terminal connections to the U.S. telephone network. These codes were defined until 2000 in the FCC Rules (47 CFR § 68.502(e)) and later in the TIA/EIA-IS-968 standard, and they refer to single and multiple arrangements of two wires and a programming resistor on a miniature eight-position keyed jack.
Unfortunately, the “RJ45” part of these codes has become a metonym for the unkeyed version of the miniature eight-position jack and plug, now widely used for Ethernet and other purposes, but strictly speaking, RJ45 refers to a different connector with totally incompatible wiring.
Symbol Sourcebook would’ve been my first guess, too, but I just glanced through my copy (7th printing, 1977) and didn’t see the ⌘ symbol. The closest thing in the Graphic Form Section is a symbol for “Atomic d orbital,” but it’s clearly not the same one that inspired Susan Kare.
Interesting. The left side of the slide at 15:43 in the video is definitely from page 27 of Symbol Sourcebook, but the detail of the ⌘ symbol doesn’t seem to be: not only could I not find the symbol, but also its caption (“FEATURE”) is set in Helvetica rather than Univers as used in the book.
I have a suspicion that she may no longer possess or even remember the book in question. Heaven knows I wouldn’t were I her, but my memory is atrocious.
The treaty returning sovereignty over the Chagos Archipelago to Mauritius, disestablishing the British Indian Ocean Territory, seems to be on track for ratification:
The consequences for the .IO ccTLD are still unclear and ultimately will depend on how the United Nations, the ISO 3166 Maintenance Agency, and ICANN respond. I’m not aware of anything more definitive than ICANN’s blog posting from November 2024, which emphasizes that “much of the discussion about .io is simply speculation” but also acknowledges the possibility that “a five-year time window will commence during which time usage of the domain will need to be phased out.”
My two biggest clients are exclusively running on .io domains and have hundreds of subdomains each - I really hope they don't end up doing something dumb here, I know two companies that don't want to deal with this.
I’ve always thought of Kerberos as a centralized authentication system, to establish users’ identities.
Authorization, in the sense of deciding to allow or deny a requested action by a known user on a specific object, remains distributed, even with Kerberos. For example, a Windows file server, having received a Kerberos ticket showing a user’s identity and security group memberships, consults its own access control lists to determine what operations to allow on files and directories.
The article here argues that those authorization decisions should also be centralized, presumably using the sponsor’s “cloud-native authorization platform,” instead of being made within each service or application.
