Ugh, thinking about on-hold music brought back the old BellSouth Business Repair (800-247-2020) hold tune. I don't think I've called that number in 25 years (looks like AT&T still uses it for reporting line trouble)... the fact that I still know the number AND CAN HEAR THE TUNE shows just how much time I spent with it in the late 1990s.

Building a Linux distribution requires a fair amount of infrastructure, and that's something that's pretty different from distro to distro (and not all make all the necessary tooling public). Changing to a different base distro would most likely require a significant rework, and may be more than someone, especially someone who has mastered the intricacies of one distro's tooling, wants to do.

Incorrect response - some manager will believe that THEIR meeting is SO important that it's worth paying for (and you said it's fine if they pay). Even if they pay time-and-a-half for extra time, it's still almost certainly not worth the intrusion into your life... living a life outside of work is worth more than some extra $$.

Which, that's kind of a privileged point of view, because I've never needed to work more than one office-hours job to survive. I've been on-call, but that's kind of a necessity in my line of work (systems and networks for small ISPs and other Internet companies). I've never worked for a company large enough to have a 24x7 high-level staff (and I probably wouldn't enjoy being in that large of an organization).

It's not all of them. One thing that tends to happen with a major outage is everybody treats downdetector.com as the gospel truth. Then end users try to make their own reports, and don't even know what service they're trying to connect to (like reporting Netflix is down when they try to load Hulu). Then lazy news services just pick up downdetector results and publish stories, which are then picked up and copied by other news services.

What's known: GCP (Google Cloud Platform, not to be confused with Google Actual Cloud Platform) has experienced a major outage. It affected some Google services as well as a lot of customer services. CloudFlare had a significant outage at the same time, although it looks like mostly just that CF's systems got backed up and overloaded trying to talk to the GCP-hosted customers.

[citation needed]

For example, the 3-reactor plant near me hit about 89% capacity for the year last year, and part of the less-than-100% was due to refueling/maintenance outages. The peak annual capacity was 96% in 2017.

Artemis II is not a landing, it's a manned flight to Lunar orbit (similar to Apollo 10). Artemis III is the mission for landing, assuming it still happens.

The Artemis II rocket is being stacked now for testing.

Eh, I have no trouble with USB-C to RJ-45 cables. I had way more trouble with the device end than the computer end before everybody finally settled on the same pinout (at one job we had to have a basket of adapters with every combination of DB-9, DB-25, male, female, and null-modem - that was the real PITA). Use quality USB adapters with genuine FTDI chips and they "just work" everywhere (including my phone and tablet).

CentOS is upstream of RHEL, so it's the other way around.

It depends on the Discord server. At minimum, they'd have an email address that the user controlled at least at some point (to confirm it). Due to spam bots, a lot of servers require a phone number verification via SMS as well.

There are multiple companies that provide bulk SMS sending for corporate use (plus some large companies do it themselves). All my notifications are from such senders - I don't get any email-to-SMS gateway messages. Bulk senders would otherwise get blocked; the email-to-SMS gateways have low rate limits. Even things like restaurants that use SMS to notify waiting customers a table is ready use real SMS senders, not email gateways.

Email-to-SMS (at least on the carriers I've seen) is really obvious and stands out as weird (which no sender wants), and the only time I remember seeing it was when I was testing it for personal use.

Email-to-SMS has always been a lightly-documented, "best effort" (don't call support if it doesn't go through or is delayed), and probably lightly-used service. Due to email abuse, it's never going to be a service that doesn't cost some money to support, so I can see it getting the axe from all the providers. I also wonder if the shift to RCS meant they were going to have to spend development money to keep it working and decided it wasn't used enough.

I've been on T-Mobile for ages, and I've seen their email-to-SMS gateway be unreliable at times, with no real effort apparent to update it.

For my personal stuff, I shifted to Pushover (one-time $5 fee, per receiving-platform but I only use one platform to receive), which a lot of things already support and can easily be called with a simple wrapper around curl. For a couple of email-only things, I have a special address in my own domain and a procmail rule to forward to Pushover.

See the list at Rabbit Ears - stations highlighted in red and with a lock icon next to them have encrypted their ATSC 3.0 signal:

https://www.rabbitears.info/ma...

It's not just approved for experimental use, it's fully approved for use. It's voluntary, not mandatory, and stations must still maintain an ATSC 1.0 signal, but they can satisfy that by getting together and compressing multiple primary channels (e.g. the major broadcast networks, leaving out public and independent broadcasters) into a single ATSC 1.0 channel. Broadcasters get together, put the ABC, CBS, FOX, and NBC primaries on one or two over-compressed ATSC 1.0 signals. Then they can each move all their additional channels to ATSC 3.0 only, and flip the DRM flag.

This isn't conjecture or "how it could happen", this is fact in multiple markets. And it's been successful enough that now they are pushing to make it a mandatory transition and drop the ATSC 1.0 requirement (and then drop ATSC 1.0 completely).

That'll work right up until the broadcasters in your market flip the ATSC 3.0 DRM flag, at which point you'll lose all DVR functionality. SiliconDust has said they're "working on" DRM support... for several years.

The ATSC 3.0 DRM parts were already approved and are already active in many markets. It's not a proposal, it's in use... the only proposal here is to force the end of ATSC 1.0 (probably hoping for another handout for set-top boxes for all the TVs that don't support ATSC 3.0).

LG (IIRC) included ATSC 3.0 tuners in one generation of TVs, then dropped it over the licensing fees. TV makers don't mind the Internet requirement - they'd like for you to hook that up so you can get THEIR ads, not the broadcasters'.