Anyone remember linuxconf?
What’s old is new again.
Respect the burrito.
Anyone remember linuxconf?
What’s old is new again.
I love that someone got the reference!
Bravissimo, hip hip hooray. What a glorious display.
I gave up on kodi. Jellyfin works better, presumably because it transcodes better.
syncthing is great.
It evokes an emotion… a pang of loss, but what is lost?
I’ve tried downvoting and upvoting and cancelling the upvote and putting it back. Neither worked.
This is frustrating.
Any news at your end?
Could be something to do with image processing on sdf?
Sometimes it takes multiple attempts to upload a picture, although I’d assumed that was a bug in the client (voyager).
I downvoted my post, waited a minute, the upvoted it. Let’s see if it shows.
Thanks for getting back to me! I hope it can be fixed because it’s a community I mod.
Out of interest, how do you debug such things? Is there a log file you inspect? Is it public?
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.
I went 10 years or so ago. It was awesome.
There’s also a massive zip line over the quarry, which we also did.
Thanks! While we are here, my last three posts to !fountainpens@lemmy.world didn’t actually make it to the community.
The first was over a week ago. The last was today.
I’m posting from the sdf instance. Any idea why this could be?
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.
This is what I use too.
It casts?! I’m sold!
But I’m not sure how i feel about downloading an apk like that.
Unless somethkng changed in the last few years, SSDs are much much faster.
That’s true. I did learn a lot, but the idea of setting it all up again gives me anxiety.
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.