@Maxy
@lemmy.blahaj.zoneVeel succes met WisB! Ik heb hetzelfde examen, hopen dat hij een beetje goed te doen is.
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.
Interessante analyse, al heb ik (als mede links-progressieve rakker) wel een paar kleine opmerkingen:
Om dan nu wat van het artikel af te dwalen:
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”.
Which GPU do you use? I believe mint defaults to the nouveau drivers for Nvidia GPU’s, which generally has significantly worse performance compared to the proprietary driver.