To get a feel for this effect, activate an instant ice pack. Mixing ammonium nitrate with water is an endothermic reaction, instantly making the pack cool down. Being able to reverse a reaction like this simply by applying pressure is fascinating.
My US-born child qualifies for US-Canadian dual citizenship under Citizenship Act Bill C-3. I can see several upsides to having a Canadian passport but what are the potential downsides for a US citizen and resident that does not intend to relocate?
Currently, none as far as the US is concerned[0]. The child is a US citizen and while in or entering/exiting must use their US passport. If they move to Canada (or any where else), they are still required to fulfill US tax obligations.
You'll want to check if Canada has the same tax requirements for citizens living in a foreign country. In Canada, the child would be a citizen of Canada and US consular protections/services are unlikely to be helpful there. Same while in the US, they are only seen as a US citizen and are subject to the US.
However, a bill was introduced: Exclusive Citizenship Act of 2025. You may want to follow it (in-case it actually passes and is not simply grandstanding for maga). It would require US citizens to only hold one citizenship and dual nationals would be forced to renounce any others or automatically lose US citizenship. Which would be challenged up to the Supreme Court as US citizenship is protected in the Constitution and can only be voluntarily renounced. The provision saying it would be lost by missing the one-year deadline to provide a written renunciation of their foreign citizenship to the State Department -- is very likely unconstitutional.
If they’re us-resident there should be no problem, assuming the person travels on the us passport outside of Canada. They’d have to travel with two passports going to Canada, as each country expects to see their passport upon entry. Canada doesn’t tax non residents like the us so there’s no tax changes without moving into Canada, and there’s currently a tax treaty for that.
There was a Windows 2000 bug that would allow the computer to be crashed via a malformed IrDA packet. Of course someone crafted a Palm Pilot app to zonk all the vulnerable PCs in the vicinity. It worked on servers as well. Endless fun for a little while.
Some laptops had them, and came with IR remotes. Some of the marketing was around using those laptops as "media centres", and you could control them from the sofa while it was plugged into a TV.
I connected self powered crank telephones to my home phone wiring for use as intercoms. Crank one and the others ring. Pick up to engage the battery powered talk circuit and you're chatting with Mabel like it's 1915. I did replace the old dry cell batteries with lithium camera cells so I don't need to think about them for a decade.
We have an Ethernet run that's not in use right now. I had a Cisco ATA from earlier experiments so I picked up 2 old phones with proper bell ringers and now the kids can call up from the living room to my office when it's time for dinner, they love it.
The second I heard that engine fire it was 1986 in my brain again. I could smell the fuel and feel the finger damage from repeatedly trying to get the darned thing to start. Followed by damage on the other side of the finger when it actually did. Ouch.
...some mockingly asking whether the firm would've maintained the same tenacity and reimbursed the Intern had he been fined 50,000 RMB at the event instead
It seemed like the future was all cloud but this year's exhibit hall was packed with infrastructure suppliers. Every third booth seemed to feature valves, pumps, massive high density power distribution systems and all the stuff you would need to cram a megawatt of electrical power into the smallest space possible and then extract the heat. Most notable to me is the waterless phase-change heat extraction provided by https://zutacore.com/. Their technology avoids massive water consumption and provides a high temperature heat source that is immediately useful for campus heating or co-generation.
Visiting Bletchley Park and seeing step-by-step telephone switching equipment repurposed for computing re-enforced my appreciation for the brilliance of the telecommunication systems we created in the past 150 years. Packet switching was inevitable and IP everything makes sense in today's world, but something was lost in that transition too. I am glad to see that enthusiasts with the will and means are working to preserve some of that history. -Posted from SC2025-
I wanted to learn more about computer hardware in college so I took a class called "Cybernetics" (taught by D. Huffman). I thought we were going to focus on modern stuff, but instead, it was a tour of information theory- which included various mathematical routing concepts (kissing spheres/spherical code, Karnaugh maps). At the time I thought it was boring, but a couple decades later, when working on Clos topologies, it came in handy.
Other interesting notes: the invention of telegraphy and improvements to the underlying electrical systems really helped me understand communications in the 1800s better. And reading/watching Cuckoo's Egg (with the german relay-based telephones) made me appreciate modern digital transistor-based systems.
Even today, when I work on electrical projects in my garage, I am absolutely blown away with how much people could do with limited understanding and technology 100+ years ago compared to what I'm able to cobble together. I know Newton said he saw farther by standing on the shoulders of giants, but some days I feel like I'm standing on a giant, looking backwards and thinking "I am not worthy".
When the Bell System broke up, the old guys wrote a 3-volume technical history of the Bell System.[1] So all that is well documented.
The history of automatic telephony in the Bell System is roughly:
- Step by step switches. 1920s Very reliable in terms of failure, but about 1% misdirected or failed calls. Totally distributed. You could remove any switch, and all it would do is reduce the capacity of the system slightly. Too much hardware per line.
- Panel. 1930s. Scaled better, to large-city central offices. Less hardware per line.
Beginnings of common control. Too complex mechanically. Lots of driveshafts, motors, and clutches.
- Crossbar. 1940s. #5 crossbar was a big dumb switch fabric controlled by a distributed set of microservices, all built from relays. Most elegant architecture. All reliable wire relays, no more motors and gears. If you have to design high-reliability systems, is worth knowing how #5 crossbar worked.
- 1ESS - first US electronic switching. 1960s Two mainframe computers (one spare) controlling a big dumb switch fabric. Worked, but clunky.
- 5ESS - good US electronic switching. Two or more minicomputers controlling a big dumb switch fabric. Very good.
The Museum of Communications in Seattle has step by step, panel, and crossbar systems all working and interconnected.
In the entire history of electromechanical switching in the Bell System, no central office was ever fully down for more than 30 minutes for any reason other than a natural disaster, and in one case a fire in the cable plant. That record has not been maintained in the computer era. It is worth understanding why.
The more I study the 5E I see it as a multicomputer or distributed system. The minicomputers were responsible for OAM and orchestrating the symphony over time, but the communications are happening across the CM which implements the Time/Space/Time fabric and a sea of microcontrollers. I think this clarification is worthwhile because it drives your point about faults in this computer-era and by extension this (micro)services-era home even more -- it's much less mainframe and more distributed system than commonly chronicled, which can be a harder problem especially with the tooling back then.
The big dumb switch fabric of #5 Crossbar has no processing power at all, but it has persistent state. The units that have processing power all go down to their ground state at the end of each call processing event, and have no state that persists over transactions. The various processing units (markers, junctors, senders, originating registers, etc.) are all at least duplicated, and usually there's a pool of them. Requests "seize" a unit at random from a pool, the unit does its thing, and the unit is quickly released.
Units have self-checking, and if they fail, they drop out of their pool and raise an alarm. The call capacity or connection speed of the exchange is reduced but it keeps working. Everything has short hardware stall timers which will prevent some unit failure from hanging the exchange.
#5 Crossbar has almost no persistent memory. End offices (for connecting subscriber lines) did not log call info. Toll offices did, but that used an output-only paper tape punch. There's so little state in the switch that matching up call start and call end events was done later in a billing office where the paper tape was read.
The combination of statelessness and resource pools prevented total failure. Errors and unit failures happened occasionally but could not take down the whole switch.
There's plenty of info about #5 Crossbar on line, but 1950s telephony jargon is so different from 2020s server jargon that it's not obvious that #5 Crossbar is a microservices architecture.
