I don't know many people that still call it "Microsoft Office"... They usually refer to the individual apps they use (Word, Excel) rather than the suite as a whole.
Some people just call it "Microsoft" ("please install Microsoft on my computer"), especially if they're on MacOS where it's the only Microsoft software they use.
Some people assume it's part of Windows since they've only ever used computers that have had it preinstalled.
I didn't realise they have unprotected streams 👀
usually cable channels lock down their streams pretty well, with CDN URLs that either expire or have a single-use token in them.
If you're not getting 100% full strength signal, it is literally unwatchable.
It depends... Sometimes it's terrible, while other times even low signal strength is fine. I only get around 65% signal strength and 75% signal quality for one channel (ABC, I think?), and it still works fine with no stuttering.
I use a HDHomeRun TV tuner, so I can place the antenna where I get the best signal, and the HDHomeRun transmits it over my LAN.
At least NBC is a broadcast station, so you can watch it for free using an antenna. I have an indoor antenna in my garage, connected to a HDHomeRun.
Huh, interesting. TIL videos can have non-square pixels.
You can still have full control over your site if you want to.
THE CHEESE IS UNDER THE SAUCE
How often do you type IP addresses? That's what DNS is for. The only time I use IPs is when I haven't configured a DNS record yet (and in the DNS configuration, of course).
Exactly. Most good ISPs will give you a /56 or /60 range if your router asks for it, and then you can subnet it into multiple /64 ranges (16 /64 networks for a /60, or 256 networks for a /56).
I have three VLANs with internet access (main, guest, and IoT), and each one gets its own /64 range.
Note that you shouldn't use subnets smaller than a /64, as several features (such as SLAAC and privacy extensions) rely on it.
Rewriting existing systems is one of the riskiest things a company can do, so old codebases are going to be around for a long time.
Those old COBOL codebases likely contain 50 years of bug fixes for every possible edge case. It'd take a long time to rewrite everything and ensure feature parity, and there's usually not a significant business reason to rewrite it (after all, a successful end result is just that the system behaves exactly the same as the old one).
The COBOL language is still getting updates, too.
Both of those documents agree with me? RedHat are just using the terms "client" and "server" to make it easier for people to understand, but they explicitly say that all hosts are "peers".
Note that all hosts that participate in a WireGuard VPN are peers. This documentation uses the terms client to describe hosts that establish a connection and server to describe the host with the fixed hostname or IP address that the clients connect to and, optionally, route all traffic through this server.
--
Everything else is a client of that server because they can't independently do much else in this configuration.
All you need to do is add an extra peer to the WireGuard config on any one of the "clients", and it's no longer just a client, and can connect directly to that peer without using the "server".
Unfortunately they no longer include elaborate Easter eggs like that, since they adopted a security policy around 20 years ago that forbids them. https://learn.microsoft.com/en-us/archive/blogs/larryosterman/why-no-easter-eggs