Is Forth a 4GL?
Badum tish. (Sorry)
Respect the burrito.
Is Forth a 4GL?
Badum tish. (Sorry)
Packet loss. Hur hur.
I thought that these personality tests had been debunked?
We had the myers briggs test back in the day, and I’ve heard on couple podcasts that these tests (including MB) are highly questionable.
As it happens, the latest maintenance phase podacst is about the MB test:
https://podcastaddict.com/maintenance-phase/episode/182427039
Not listened yet, but will.
Anyone remember linuxconf?
What’s old is new again.
It’s a really silly requirement IMHO.
This smells of academics…
On the other hand you can’t really have UB in code written in asm.
Just throwing that out there!
I gave up on kodi. Jellyfin works better, presumably because it transcodes better.
I known they outsourced the firmware development, so who knows, maybe the electronics hardware too.
You guessed wrong.
It’s a ridiculously expensive and “home made” looking, but it saved my hands from OCD.
Hrm. I have a keyboard that requires an A to A cable and I think it works with the cable any way around…
Might be wrong.
syncthing is great.
(Type punning) :)
Is that a pun?
He would have to infer that…
Sorry to hijack the thread, but does anyone known a terminal tool I can use to auto-tag the odd album when I find one with bad tags?
Music is stored on the server and served read only, so gui tools are not convinient.
Picard is great, but gui.
It’s this (excuse formatting): https://www.openssh.com/releasenotes.html
sshd(8) will now penalise client addresses that, for various reasons, do not successfully complete authentication. This feature is controlled by a new sshd_config(5) PerSourcePenalties option and is on by default.
sshd(8) will now identify situations where the session did not authenticate as expected. These conditions include when the client repeatedly attempted authentication unsucessfully (possibly indicating an attack against one or more accounts, e.g. password guessing), or when client behaviour caused sshd to crash (possibly indicating attempts to exploit bugs in sshd).
When such a condition is observed, sshd will record a penalty of some duration (e.g. 30 seconds) against the client’s address. If this time is above a minimum configurable threshold, then all connections from the client address will be refused (along with any others in the same PerSourceNetBlockSize CIDR range) until the penalty expire.
Repeated offenses by the same client address will accrue greater penalties, up to a configurable maximum. Address ranges may be fully exempted from penalties, e.g. to guarantee access from a set of trusted management addresses, using the new sshd_config(5) PerSourcePenaltyExemptList option.
I know. I just couldn’t resist the allure of the dad pun.