Maxy

That seems like a good edit, and fair enough. Good to know that there is also room for people who want to use their computer in a non-fanatical way, simply minding our own business.

I don’t fit in an of these teams, and neither do literally all Linux users I know. Should we have identity crises, or could this be a giant oversimplification?

Which compression level are you using? My old server is able to compress flac’s at the highest (and therefore “slowest”) compression level at >50x speed, so bumping the level up shouldn’t be too hard on your CPU.

I’ve been running some external drives on my server for about a year now. In my experience, hard drives with an external power supply suffer less from random disconnects. The specific PC also makes quite a large difference in reliability. My server is just a regular desktop and has very little problem staying connected and powering my 3 external drives. My seedbox is an old laptop, and has been having almost constant problems with random disconnects and power issues. Maybe test how well your framework does with some external drives before committing to the plan?

To change the ownership of the files, you should only have to run sudo chown -R user:group directory. -R makes chown run recursively, so it will modify the directory and all subdirectories and files. Do note that changing the ownership to plex:plex or something similar would leave your user unable to normally modify the files. My solution to this was to add both my regular user and the plex (in my case jellyfin) user to the same group. That way both users can easily see and modify the files, as long as the group has read/write permissions (the 2nd column of rwx in ls -Al). If necessary, you can add group permissions with sudo chmod -R g+rw directory.

On a side note: have you considered using jellyfin? It’s a completely free alternative to plex, which recently received a truly massive update with tons of new features. Some people prefer plex’ overall experience, but I’ve been running jellyfin with almost no complaints.

Small disclaimer: I’m writing from mobile, so the commands might not be 100% correct. Run at your own risk, and NEVER POINT A CHMOD/CHOWN COMMAND AT SYSTEM DIRECTORIES LIKE / OR /USR. That’s one of the easiest ways to completely break your system.

Have you tried the official guide from the jellyfin website?

As for the guide this AI generated: it bothers me that they instruct you to use chocolatey for the *arrs, but still advice you to install docker, qbittorrent and jellyfin manually (all of which have chocolatey packages). I disagree with the comment that external storage would be recommended, as internal storage is generally more reliable (depending on a lot of factors of course). Also, I believe the "adding a library"-section of the jellyfin setup is a bit too short to be of any use, and would recommend referring to the jellyfin docs instead.

This guide also doesn't explain how to make jellyfin accessible outside of your LAN. Once again, I'd recommend referring to the jellyfin docs if you want to do this.

I personally have only set up qbittorrent, jellyfin and docker (not the *arr suite), so I can't comment on the completeness of the guide, but I wouldn't trust it too much (seeing the previous oversights).

And finally, as someone who started their selfhosted server journey on windows: don't. There is a reason why almost all guides are written for linux, as it is (in my humble opinion) vastly superior for server usage once you get used to it.

~~didn’t know that was a part of bisexuality~~

I should probably flee before I get eaten by an army of blahåjar (apparently that’s the correct plural?)

Oh I don’t mind the nitpicking, thanks for the explanation! I (apparently erroneously) thought “demake” and “decompile” were synonyms. Guess I’m one of today’s 10000.

In that case the (now taken down, but forked a gazillion times) portal64 project would be a correct example of a demake, right?

interested in females

Username checks out, though I’m assuming you meant “demakes”?

Anyways, the demake I’m most familiar with is the in-progress Lego island. The YouTuber behind it documented part of the process in vlogs (linked on the GitHub page), so that might be an interesting starting point.

I believe SSD’s don’t actually experience wear when reading data, only when writing. Loading more data from SSD’s shouldn’t cause any premature failure. Overwriting more data each update could cause the drive to fail slightly earlier, but if that’s really that big of a concern, you’d be best of moving to Debian stable (no updates means no SSD writes).

If SSD wear prevention is really that big of a concern, you might be interested in profile-sync-daemon (https://wiki.archlinux.org/title/Profile-sync-daemon). It reduces writes to hard drives by keeping your browser profile in RAM, and only periodically syncing it to disk.

Though I must add that SSD’s wearing out really isn’t that much of an issue with modern drives. With normal usage, a drive will become obsolete long before it actually wears out.

I tried using Linux alternatives to iTunes, but it was always a pain. Even iTunes itself on a separate windows box was more of a hassle than I wanted. I eventually discovered rockbox, which works great with my iPod (5th gen AKA video): it has way more config options and allows me to simply create .m3u playlists and use my own folder structure. If your iPod is supported (https://www.rockbox.org/wiki/IpodPort.html), I’d absolutely recommend Rockbox over other solutions.

If your iPod isn’t supported by Rockbox (like my nano 5th gen), you could probably use strawberry or GTKpod. Both are imperfect, but work “good enough”.

Oh never mind, you’re already using the proprietary driver.