Your doing weeklys so why not 7

They are all daily backups, those schedules I pointed out are for pruning. And I don’t understand the question… How would keeping 7 instead of 10 dailies help me?

Ah, yes. 300 lines of basic from a magazine, wrote it to a cassette tape and played it back when I wanted to play the game.

Daily for 10 days, 4 weekly, 4 monthly.

That covers me from broken updates, generally.

deleted by creator

Sir, are you OK?

I ran a linux box with two gigabit Intel NICs for years with iptables. Almost any device can do it.

Like others say, opnsense is prob your best bet unless you like the abstraction of iptables

This person isn’t saying public housing is bad as an idea, they’re saying it’s bad in its current form.

And while it’s better than no shelter at all, it certainly is not ideal in its current form.

deleted by creator

1. Obtain flac cd-ripped originals
2. Convert to 256bit center-weighted opus
3. Use Picard to tag music, save to artist - album/song file & folder pattern
4. Sync to my subsonic-compatible server

Uhh… That’s a repackage of Lidarr in docker, and based on the commits only to comments and to the packager’s Discord server, I would say they probably aren’t adding any actual functional changes.

This is the actual Lidarr repo: https://github.com/Lidarr/Lidarr

I don’t think there is anything, really. I use a soulseek client to get flac files and convert them to opus manually.

Radarr and Sonarr work because the naming conventions for videos are more or less established.

With music, everyone has a different philosophy for tagging, renaming files, transcoding, how to handle best-of albums, compilations, etc. So what works for you probably doesn’t work for me and vice versa.

Lidarr gets very few updates, I don’t think anyone is working on it anymore. I remember the problem was keeping up with metadata handling.

I know this doesn’t answer your question directly, but it’s related; Lidarr is pretty much dead. The problem became managing metadata sources and assignment to media.

Google didn’t buy it, it’s an open standard.

What google did is host RCS infrastructure and have the worlds most popular messaging client.

You can absolutely setup an RCS server, build an FCS client that has the appropriate keys and access, put RCS relays in important peering points a over the world, and roll that out to millions of ppl yourself.

Sort of like nuclear power; you could probably build a reactor yourself, but it’s a heavy lift plus there are players that don’t want you to.

telling me what’s wrong

How do you verify the accuracy?

I have been in IT for 30 years, and in security for the last 16.

You’ll find lots of arguments from a productivity and removing barriers point of view that say don’t bother with strict user access controls, just layer on other security measures. Others (usually older-school sysadmins) preach “doing the work”, meaning secure your users well and audit access often. There are advantages and disadvantages to both approaches.

I personally do a bit of both. The old way of being meticulous with access works, but not without diligence and self-audit. The newer devops way if doing things with secrets management and treating everyone as untrusted works too, as long as you document the automation.

Maybe one suggestion about user control in a homelab setting is not to use the same username across multiple services, but rather name your users something like name.of.service.admin so that you a) don’t forget where you are and b) if you start collecting logs centrally, you can easily identify which system the logs came from.

Schools exist to standardize baseline knowledge for the working class. If this weren’t true, private schools wouldn’t exist.

Well, related to time, the one guy who maintained Linux NTP client/server almost had to stop doing it and go get a job a couple years ago.

These projects are important, and while the article is a bit dramatic, I would argue that the folks doing work like writing IEEE specs and the drudgery of IANA cleanup are what keep the internet from being any shittier than it already is.

It’s not super difficult. They provide setup instructions and then you just connect to your new instance instead of the public one.

I just looked back over your post and your answers there and in here. With respect, your writing style sounds combative. I would never ask you to change it for anyone, but you should understand how it comes across.

Regarding the AI disclosure stuff, you aren’t the first burgeoning dev posting to Lemmy to go through this exact gauntlet of “AI slop” accusations. You are on a platform used by a fairly specific group of people who were pissed off enough to leave reddit, so not the usual general “tech enthusiast” crowd, and a fairly militant bunch.

The way I see it, AI is 1) already here and 2) just a tool. It’s being used in the background of a LOT of projects and there is by now simply no way to cover our ears and pretend it doesn’t exist. For better or worse, it’s also changing the pace of development, check out how fast PS5 emulation is happening because of AI tooling.

That said, developer practices that took us 40 years to make standard are still valuable, so folks have legitimate reason to call out your commit and documentation practices. If there is anything I objected to in your project, it might be that.

Ultimately, a created work starts to live a different life once it is public. You started without sharing it, shared the source, and now you have to make a decision: continue sharing and accept that not everyone will like it, or stop sharing. It’s really that simple.

Sir… You came to us for these comments this time. Are you just here for a fight? It’s not clear what you want from us.

I don’t find your project interesting enough for me, but I was happy you did it. I prefer to keep my infrastructure at home in a controlled environment and take my maps out with me, but I don’t use navigation, I just record GPS tracks.

Now with this post, I’m starting to wonder what your motivations are altogether, particularly considering your responses here.