My workplace originally had regular UPSes, just like the one you showed, one of the many that would only intervene when the power gets cut.

It introduces a temporary power loss, in terms of some milliseconds usually, expecting the devices downstream to be able to handle them.

I had a similar issue on my workplace's server after a bad storm, then did some research about how to avoid issues when a UPS is present.

Turns out that there is a whole another category of UPSes, namely Double Conversion UPSes, where the UPS is constantly charging a battery and the battery is constantly powering the load.

Almost no outside factors can interfere with the load this way, and I'm certain it saved my ass both in the workplace and at home: just a few days ago we had some huge storms, hail, thunder, strong winds and such.

Power would constantly go out and quicky come back up.

The initial UPS failed for much less.

Both my workplace's server and my home server never felt any of it, cause they're never directly connected to the power line (unless the UPS is in maintenance mode), and the peace of mind of knowing that they never feel any of that is priceless.

It's a good thing that I cannot count how many times they saved me lots of time, mostly because since their introduction I never had a power loss which I previously had with a regular UPS.

The disadvantage? Much more expensive, since wattage matters more than ever as they have an inverter running 24/7.

For my workplace I got one that costed about 900 euros, for me I got one that was about 400.

I do not agree about this being a simple solution, especially if you want to set up netboot for this, but I don't want to engage this discussion any further since we're just talking about a solution to a problem that I don't have and I don't care to solve, so maybe we should just agree to disagree?

What if you have a system that just works and you can't break?

No rsync, no remoting from work (vpn or other software et al), no "i gotta be on alert for when my kid breaks my computer again"

Also, why do we have to shame people for just wanting to use their computer?

The only possible improvement would be to mention that they are bytes - as said otherwise, representation is meaningless, but they factually are 8 bits each segment, which means they are effectively just a number between 0-255.

Still, I think you were able to explain yourself to the other comment, so there's that.

This guy works ^

I don't handle alcohol well, so I don't use it that much.

Almost always, I find myself heavy-headed, and if I insist, it takes me a bit of effort to stay upright, although it's manageable, just it's not "automatic" anymore.

Other than that, I tend to talk and rant a bit too much, and even in the moment I tend to realize that I shouldn't be saying some things or shouldn't be talking as much but I just "ignore" this instinct, like "do I need to really bother with stopping my mouth?"

I would, but in a soft fashion.

However, don't emulate internet strangers, just be yourself.

Reallocated sectors, yup, it's dying...

Preface: This is what I learnt about Subsonic and such. The informations below may not be fully correct but the core idea is there.

An API is not a piece of software.

It is merely a way to define how to make a software "do" an action, like search for a song title or download the song file for streaming/playback.

Navidrome does not make use of anything from Subsonic, it merely implements (exposes) a Subsonic-compatible API.

Knowing this information, anyone can run a web request to Navidrome and search for a song, and download/stream it, like they would already do for any other Subsonic-compatible provider:

You can find a plethora of software that can leverage any Subsonic-compatible API provider to connect to that music library, from dedicated Web UIs to Android and iOS apps, which know how to download and stream songs and play them back.

This mechanism gives the user the freedom to choose the backend and frontend, and the developers can just implement the part they prefer: for example, the Navidrome team does not have to build an Android or iOS App, whereas App developers don't need to write a serverside application to manage the "real" music archive, decode tags, or even implement a search algorithm, as all this data can be asked via the API.

Technically, Navidrome wouldn't even need a Web UI.

Over the years, the Subsonic API has been forked into OpenSubsonic API, which as far as I could tell, merely serves as a way to better define, and to further add new features into, an otherwise closed and possibly reverse-engineered API.

Yep. There's no AUR for bazzite since it's based on fedora immutable, unless I'm mistaken and there's a way to do so anyway somehow. Still, bazzite and AUR do not go hand in hand AFAIK as it's meant to be an immutable system.

Just to not sound like a complete asshole... ofc the 25% boost does not depend on bits/kbits, the difference is still 256 vs 320, but I just wanted to emphasize that the expected result is 25% bigger in all terms.

If it helps to imagine, the space needed to store a 256k 5 minutes song will store a 320k 4 minutes song. Then, you are already relying on a quite decent quality beforehand so it's all extra quality and details.

I usually hear the difference in the high frequency sounds, which is exactly what is otherwise sacrificed in low bitrate compression formats.

FLAC will produce an even better sound, as it's lossless, but for most songs I couldn't justify the file size difference.

That's 64 kbits, or about a 25% boost in bitrate.