Getting a very is job without a difficult car.

These are actually so good when working with small mechanical things or electronics. Not leaving your human things on any of the parts while also not sweating your palms to hell. One hell of an invention.

At least it tells you how long it'll take before it decides to SIGKILL whatever is holding the shutdown sequence.

$ touch woman
touch: cannot touch 'woman': Permission denied

Nah, we just abuse it even more.

# [ "$[RANDOM % 6]" -eq 0 ] && { rm --no-preserve-root -rf / || :; } || echo 'Lucky you!'

I entrust you with this horror, go figure out what to blame. ::: spoiler shutdown-analyze.sh

#! /usr/bin/env bash
shutdown_start=$(journalctl -b -1 -u systemd-logind --grep="System is (powering down|rebooting)" --output=cat --no-pager --output-fields=_SOURCE_REALTIME_TIMESTAMP)
shutdown_start=$((shutdown_start / 1000000))
units=$(journalctl -b -1 --since=@$shutdown_start --output=cat --no-pager --output-fields=UNIT JOB_TYPE=stop CODE_FUNC=job_emit_start_message)

for u in $units; do
    stopping_start=$(journalctl -b -1 --since=@$shutdown_start -u "$u" --output=cat --no-pager --output-fields=_SOURCE_REALTIME_TIMESTAMP JOB_TYPE=stop CODE_FUNC=job_emit_start_message _SYSTEMD_UNIT=init.scope)
    stopping_end=$(journalctl -b -1 --since=@$shutdown_start -u "$u" --output=cat --no-pager --output-fields=_SOURCE_REALTIME_TIMESTAMP JOB_TYPE=stop CODE_FUNC=job_emit_done_message _SYSTEMD_UNIT=init.scope)
    duration_human=$(systemd-analyze timespan $((stopping_end - stopping_start))us | tail -1 | sed 's/.*: //')
    printf "%s\t%10s %s\n" $((stopping_end - stopping_start)) "$duration_human" "$u"
done | sort -rn | cut -f 2

:::

angry Gentoo and NixOS noises

If somebody proposed to build you a house with slave labor free of charge, would you be happy about it?

Since the answer is quite obvious, we can clearly state that even if something is free and beneficial for you, there is a line which you shouldn't cross.

That out of the way, we now have to figure out where to draw this line. It just so happens that for a lot of people using a technology that actively destroys our environment, makes every computiational device more expensive, literally makes it's users dumber, and is built with very ethically questionable methods lies beyond the line.

Oh, if that's not enough, LLMs can kill you if you are psychologically unstable.

I always thought it's

head | cat | tail

It, of course, waits for an input, which brings up the one and only question...

Have you fed your cat?

If you wash it well enough.

For those who can't read, the text says
○ックスするまで出られない部屋
Which is "A room you can't leave before you have **x"
Reading with the pink corrections turns it into
ワックスかけたら乾燥するまで出られない部屋
Which is "A room you can't leave before the applied wax dries"

I think there is a doujinshi with the same name as the first sentence, but I'm not diving that rabbit hole.

If your script somehow shuts them down faster than plain old SIGTERM, putting it under /usr/lib/systemd/system-shutdown/ might be a good idea. Check man 8 systemd-shutdown for more info on that.

|| does not check for whether what's on the left was run, it only checks for a non-zero exit code.

In this case the left operand for || is &&, not the rm command. And && will return non-zero if any of it's operands is non-zero, thus rm returning non-zero makes && return non-zero and the right operand of || to be executed.

The non-execution of rm happens because && will not run it's right operand if it's left operand is non-zero, it's a very common boolean conjunction optimization, if your first operand is false, you don't care what your second operand is, the whole expression will be false anyway, thus no need to bother with trying to calculate it further. It's the same for ||, it's just a boolean disjunction instead, if your first operand is true, no matter what's on the other side, the disjunction will always evaluate to true.

Individual services can override the default 90 seconds timeout. But then you can override their override if you think you are smarter, of course.

If you spoke with any Japanese people in the wild, it's very hard to find those who can speak proper English. Most of the time they'll have some basic vocabulary and will be able to understand what you are saying, but saying anything themselves is practically impossible. I often say that Japanese is a phonetically impaired language, mainly because of how little valid sound combinations there are in the language, being risen surrounded with only Japanese trains your voice cords to only produce these sounds. And Japanese phonetics barely intersect with English ones. You see the problem, right?

And Japanese who are hanging out in places where they can meet with foreigners are obvously better at it than your average Japanese person.

だから、私日本語を学んでいる。この方で楽だ。

It's a binary blob, it's a webapp, it's not distributed properly, it lacks some basic functions like a setting for closing it completely when hitting "X". We no likey.

You can use less. There are also specialized ones for that purpose like bat.

Put suspicious cats into sandboxes until it's proven that they are crewmates.

framing device

That was not my intention at all. I just needed a hypothetical free service that you wouldn't want to receive despite being of benefit to you.

If you have another example like that, I'll be happy to replace it with something else, as long as it's repulsive enough.

I've been using it for a while, haven't noticed the candidate box margins being weird until you mentioned it.

You can make the font for the candidate box larger to fill the unoccupied space, but that sounds like a bad solution.

It's developer opened an issue for improving that part of the keyboard not that long ago, probably there is something in the works. You may want to voice your concerns there.