The most shocking revelation that I took from this game is how many coding fonts think it's acceptable to neither slash nor dot their zeroes.

I can't imagine using one of those fonts that leaves 0 and O nearly indistinguishable.

Many ISPs (e.g. AT&T Fiber) block UDP traffic with source port 123 to mitigate NTP amplification attacks.

Most people won't notice that problem since low-end consumer routers tend to mangle the source port when they perform outbound NAT. The ISP-provided router will generally do this itself until you enable "DMZ+" or "IP Passthrough" or some similarly-named mode, as home networking experts will typically do so they can manage NAT and firewalling on their own devices.

If a Windows laptop can sync and the wired Windows desktops can't, your wi-fi AP might be doing the necessary source port mangling.

If you add a NAT rule to your router to change the source port for NTP traffic, you should get time sync working.

Effective collaboration relies on iterating over clarifications until ambiguity is acceptably resolved.

Rather than spending orders of magnitude more effort moving forward with bad assumptions from insufficient communication and starting over from scratch every time you encounter the results of each misunderstanding.

Most AI models still seem deep into the wrong end of that spectrum.

And that's counting the extra ~year I got out of the Lenovo after having to replace the fans.

Having user serviceable parts is nice but having parts that last 14 years is better. If there was a brand that did both, that's what I'd buy.

I put off upgrading my personal MacBook for years after work issued me a MacBook with the touch bar. Such a usability nightmare for the sake of eye candy. That was a long seven years.

Beyond that technicality, your guess is often right... Routers will frequently prioritize forwarding packets over sending the TTL exceeded packets tools like MTR use to measure response times.

When Steam Machines re-launch with the current generation of Proton compatibility it will be an entirely different story.

Essentially all you're asking for them to add is better specs.

In December their revised branding guidelines added a "Powered by SteamOS" badge so presumably 3rd-party boxes with various specs in set-top form factors will be coming before too long:

> The Powered by SteamOS logo indicates that a hardware device will run the SteamOS and boot into SteamOS upon powering on the device. Partners / manufacturers will ship hardware with a Steam image in the form provided by and/or developed in close collaboration with Valve.

Sort of like the bittorrent algorithm that favors retrieving and sharing the least-available chunks if you haven't assigned any priority to certain parts.

Still awful, but nowhere near as awful as the former.

tmux has `lock-command` / `lock-after-time`.

You could implement a screensaver on top of those... they only "lock" as much the $LOCKPRG / lock-command chooses to lock them, no reason a single keypress can't "unlock" the screen if it's just a screensaver.

Those will be invoked regardless of whether a program is running or it's sitting at the prompt. Since tmux and screen are terminal emulators, the underlying shell and programs running in them won't even be aware of the screen saver.

I have my friend's garage NAS set to use `cmatrix` as a lockscreen on the system console and mine uses `glances`.

In good conditions you can go months without sending a single byte of traffic between an SSH server and client and both will pick up the connection just fine when it's time to communicate again.

You could cut off traffic between them for any amount of time and they would be none the wiser as long as the network connection is back to normal when they finally try to send traffic again.

(I had SSH sessions in a QA lab persist as if nothing had happened after the connection between the endpoints was down for almost a week while we replaced the aggregation layer routers. They never saw a link state change since the access layer switches were up the whole time. They never attempted to communicate while the connections between those were down, so there was never any problem as far as they were concerned.)

The keepalives and connection checks and so forth are mostly to account for things like stateful network gear (firewalls, NAT routers, etc) between the endpoints that will cease relaying traffic between them if they are quiet for too long.

Would you like me to share if I can't find one and wind up doing it myself?

> ...these observations hold true of singing, especially singing by a singer of renown. The singer manifests herself in the song. To impersonate her voice is to pirate her identity...

> We need not and do not go so far as to hold that every imitation of a voice to advertise merchandise is actionable. We hold only that when a distinctive voice of a professional singer is widely known and is deliberately imitated in order to sell a product, the sellers have appropriated what is not theirs...