You're building new cell towers, managing countless failed backhual links (thanks to fiber's natural enemy, the backhoe), working with whatever obscure bugs your MVNOs have managed to uncover, certifying new cell phone designs, and still working on upgrading everything to 5G while simultaneously planning for 6G (keeping in mind that the 5G network architecture looks radically different than the LTE architecture). Much of that work is necessarily physically distributed across the entire country.
Not to mention dealing with end-user sales and support, which unfortunately often needs physical stores.
I'm not going to say whether 100k is too many, but there's a lot more involved here than just maintenance and monitoring - especially if you want your network capacity to keep up with growing demand.
The problem is you can’t find any company willing to recycle them. Because of the nicotine content, I’ve heard e-waste recyclers consider them hazardous waste and refuse to touch them.
yeah, e-waste recyclers suck, they love to ship it all to the 3rd world where piles of circuit boards get tossed in an open fire and stirred by kids to reclaim the metals.
The biggest tangible benefit is you don't need to worry about NAT port mapping any more. Every device can have a public address, and you can have multiple servers exposing services on the same port without a conflict.
(The flip side is having a network-level firewall is more important than ever.)
You also don't have to worry about running a DHCP server anymore, at least on small networks. The simplicity of SLAAC is a breath of fresh air, and removes DHCP as a single point of failure for a network.
So the benefit is that you dont need to worry about NAT for a couple of port forwarded services you may use (which might well even use UPnP for auto setup), but the tradeoff is you now need to think about full individual firewall protection for every device on your network?
I'll take full security by default and forward a couple of ports thankyou!
NAT doesn't solve everything, and creates a whole new class of problems that you can just avoid by adopting IPv6 natively. And it's definitely not being ignored at larger companies.
In particular, just off the top of my head...
- T-Mobile US doesn't even assign clients an IPv4 address anymore. Their entire network is IPv6 native.
- Many cloud providers charge extra for IPv4 addresses, but give IPv6 addresses out for free.
For trivial cases NAT is easy, for complex situations it's a nightmare. I've been fighting a lonely battle against multiple-NAT VPNs as being the solution to the wrong problem for longer than I care to remember, and I'm tired boss. A few years ago we had a client site go offline because a local network guy just didn't like IPv6 and turned it off, not realizing that a huge amount of stuff was happening automatically and that's why he hadn't been needing to work on it.
They do not used bottled (or boxed) water for coffee.
That comes from the coffee machine built into the galley, which uses the aircraft’s onboard potable water tanks.
Those tanks are filled from a hose by the ground crew during refueling.
(At least for major US airlines. I understand some other carriers serve instant coffee packets. Even then, the hot water still comes from the aircraft tanks.)
I wonder how air Canada reconciles this. There was a popular globe and mail article a while ago that gave awful rankings to air Canada's water tanks -- so the company put up signs in the bathroom saying the water is non-potable and called it a day.
Not super comforting if they're then using the same 'non-potable' water to make coffee...
Is there any reason to expect there would be "toxins", given that it's just water? I can imagine how there might be accumulated toxins it's a pack of chicken breasts left in a hot car for 8 hours, but if it's water it should be fine? After all, boiling water is a tried and true way of making water safe to drink.
Yes, there are substances that slip through, but it works well enough for most cases that it's probably fine. Otherwise you get into weird edge cases like "what if there are prions in the water?!?" or whatever.
Heavy metals are a big problem, especially from cheap brass fittings common in outdoor water hoses.
Indoor plumbing, by contrast, uses copper and/or plex tubing and so there’s near zero risk of metal poisoning (caveat on cheap plex fittings- don’t do that.)
AOL was it's own network, completely parallel to the internet. It didn't use TCP/IP, it used a propritary transport called P3 - heavily optimized for dialup.
They had their own dedicated client app, where each page loaded in its own window. It didn't use HTML, it used something called "Rainman". URLs weren't a thing, you accessed "channels" (pages) by entering a specific "keyword".
Later on, in 1993, they added support for Usenet (see: "Eternal September"). Then in 1994 they added support for Gopher and WWW. So you could dial into the AOL client, and then open a regular web browser. But for most home users, there was more content in the AOL walled garden, so the web was something of a curiosity at first.
So to answer your question: It wasn't an artificial limitation. AOL was designed in a way that was fundamentally alien to the way the Internet + Web evolved.
(At some point, you could connect to AOL over TCP/IP - useful if you had a broadband Internet connection but still wanted access to content on the AOL network. This was done by encapsulating P3 inside a TCP/IP header. You still had to use the AOL client software and have an AOL membership.)
The problem is every aircraft model flies differently. The remote pilot would need to be familiar with that particular type of aircraft to safely land it.
I'm thinking of higher-level contributions such looking at the weather and saying 'fly to this airport and use this runway'; or asking the passenger, 'what does this gauge say?' or 'look at the left engine; what do you see?'; or talking to air traffic control.
That's a really big if, especially since not all traffic has a transponder, and not all airports are towered.
It would need to understand how to visually look for traffic with a camera, and understand what intentions other pilots are communicating on the radio.
You're building new cell towers, managing countless failed backhual links (thanks to fiber's natural enemy, the backhoe), working with whatever obscure bugs your MVNOs have managed to uncover, certifying new cell phone designs, and still working on upgrading everything to 5G while simultaneously planning for 6G (keeping in mind that the 5G network architecture looks radically different than the LTE architecture). Much of that work is necessarily physically distributed across the entire country.
Not to mention dealing with end-user sales and support, which unfortunately often needs physical stores.
I'm not going to say whether 100k is too many, but there's a lot more involved here than just maintenance and monitoring - especially if you want your network capacity to keep up with growing demand.
reply