This reminds me of my struggle with yoga.
Stretching: good. Magic energy: sigh…
Respect the burrito.
This reminds me of my struggle with yoga.
Stretching: good. Magic energy: sigh…
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.
Never buy from a seller with no feedback or sales.
Send the video over a messenger instead?
Anyone remember linuxconf?
What’s old is new again.
Or OpenBSD in general. I’ve used it on my desktop for about 25 years.
It is compared to their predecesssor.
The 720kb “double density” diskette used for example, in Commodore Amiga computers.
Carry one in your pocket so you can whip it out in a threatening gesture… like in the film hackers
And it has a replacable battery and headphone jack. What is this madness? Next you will be telling me it has an sd slot.
My only worry would be whether the software gets patched to fix security vulns and in reaction to breakage with 3rd party services (e.g. whatsapp).
I gave up on kodi. Jellyfin works better, presumably because it transcodes better.
Burger sauce
syncthing is great.
Well I looked at beats over a decade ago and it wasn’t handling extra files that came with albums correctly (pdfs, jpgs etc).
That bug is still present all this time later: https://github.com/beetbox/beets/issues/111
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 recall hearing that openssh has something like fail2ban built-in now. I forget the name of the feature.
I self host. Don’t.
Jellyfin is the way