oxygen_crisis

The Constitution pertains to limiting the power of the state, limiting abuses by the people and systems entrusted with enforcing the law, not limiting your neighbors.

Technically it's an IPv4 router once you enable net.ipv4.ip_forward in step 1, the rest is enabling a whole lot of supplementary services and operations not intrinsic to the definition of a router.

> * dotted zero vs slashed zero (i prefer the slashed zero, but dotted is fine as well)

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.

Might be a good idea in general to throw out a few preventative iterations of "Your code is broken, can you find the mistake?" before you even bother reading its initial output

Windows NTP client uses UDP port 123 as both the destination and source port, rather than letting the OS assign an ephemeral source port.

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.

Yep, humans have had a remedy for the problem of ambiguity in language for tens of thousands of years, or there never could have been an agricultural revolution giving birth to civilization in the first place.

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.

There was a Lenovo and an ASUS and an Acer in between but those all went in the graveyard pile before their second year was up and I had to keep resorting to the 2011 Macbook.

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.

Isn't the real prize the library of personally-identified samples preserved in their "biobank" and not the methodologies or analysis they've applied to it so far...

I thought the touch bar was even worse than the butterfly keys...

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.

You're somewhat exaggerating the effect, the headline uses past tense and your comparisons don't.

They are only misleading if you allow yourself to be misled by them. It's an extremely informative measurement if you are aware of how it works and don't misinterpret the results.

Traceroute doesn't use ping requests except with the old Windows binary. Usually it uses "Time-to-live (TTL) exceeded in transit" messages.

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.

Steam Deck succeeded where Steam Machines flopped because of nearly a decade of advancement on the Proton compatibility layer, so the catalog of eligible games is orders of magnitude larger than it was in 2015.

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

The deck already has bluetooth for controllers and HDMI out if you get a standard USB3/HDMI dongle (or their expensive dock).

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.

You could let users choose what to mirror, and one of those choices could be a big bucket of all the least available stuff, for pure preservationists who don't want to focus on particular segments of the data.

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.

I see 24 seeders for the entire 72-episode run of the 1991 sitcom "Herman's Head" which was so poorly rated that it's never seen a home media or streaming release, your premise doesn't hold any water at all.

This isn't the equivalent of burning it, a closer equivalent would be barricading it for a while.

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

GNU screen has a `lockscreen` option with a $LOCKPRG environment variable, and an `idle` command that can do `idle 300 lockscreen`.

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`.

There's no timeout on SSH sessions by default.

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.

Has anyone rolled this into a docker container yet?

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

The court explicitly limited their decision to the voices of professional singers in that case:

> ...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...

We may be choosier than most about social media, but here we are typing our thoughts into a web page expecting nothing in return except the possibility of hearing other peoples' thoughts.

We all know people who are truly tired of social media, we're not going to hear from them here.

sshpass is a travesty of security.

It has all the pitfalls of putting your front door key under your doormat. Except you're doing it in a world where everyone can materialize a unique key out of thin air, and you can always instantly tell your door which of those keys should or shouldn't be allowed to open it.

sshpass is a curse, even calling it a crutch would be improper flattery. It's a dangerous cheat that accomplishes nothing except impeding people from otherwise spending the 20 minutes it takes to figure out SSH keys.

Showing it to a reporter with a reputable news agency shouldn't count as distribution.

Reporters and their editors are meant to be the experts on the ethics and legalities of what should be redacted and what level of detail is in the public interest to report.

You should be able to fork over everything to a reporter securely and let them defer to their ethics, consult with their lawyers, liaise with law enforcement, etc. to determine what level of disclosure is appropriate.

echo 1*; echo 2*; ...

Break it into tenths (ninths, maybe, with no leading zeroes?), or finer granularity if necessary.

The argument list isn't nearly as constrained as it was a decade ago. "echo {00000001..10000000}" works in bash on most modern distros where shells on earlier systems would have choked on a tiny ARG_MAX.

> An interview question for a position that requires knowledge of bash/linux/stuff could be:

> What if you're ssh'd into a machine, you're in your trusty bash shell, but unfortunately you cannot spawn any new processes because literally all other pids are taken. What do you do?

I'd look in the /proc/[pid]/ filesystem for visibility into what processes are exhausting the PID space.

`kill` is a shell builtin in bash, you don't have to rely on forking a new process like /bin/kill. If you can find out the parent process whose children are exhausting PIDs you're well on your way to stopping it and getting a handle on things again.

And I'll be darned, this script parses /proc. No | pipes or $( .. ) substitutions that would need to spawn another bash subshell process either. Pretty clean.

I don't think there is one... macOS doesn't have enough functionality-breaking updates to make a significant list, and Linux/BSD-based distros generally do cleanly segmented updates to individual apps and services rather than Microsoft's great big monolithic all-or-nothing OS update bundles that touch on dozens of services at the same time.

Here's >100 of them in the past ~8 months:

https://www.manageengine.com/patch-management/resources/micr...

> how often are big eruptions followed by even bigger eruptions?

Quite often, I'd say.

Disruptions in the stability of geological processes frequently have a compounding domino effect... a volcanic eruption is often preceded by the opening of smaller vents, small landslides can trigger large landslides, small sinkholes can suddenly develop large ones, a trickle over a levee can turn into a total breach, most M>7.0 earthquakes have foreshocks...

You can't tell where the peak severity will be in a cluster of geological events except in hindsight after the entire cluster is passed.

$* will break on directory names containing spaces and other bash "word" delimiters, use "$@":

    cd() { builtin cd "$@" && ls; }