I'm seeing threads where even for HDDs people are recommending you mount them yearly to do a full check of the data and to ensure that everything keeps moving freely.
regardless if it actually helps the longevity, it's probably a pretty good way to notice when you need another copy of the data. If you have your precious data on three harddrives and one starts thowing errors during your yearly check, you can get a replacement in good time
You've validated that the scrub is actually running, right? I know that the lack of a default schedule for ZFS scrubs caused Linus Media Group to lose a bunch of archived videos to bitrot.
I think I can understand it to a degree. If the code is well-documented (with comments and design docs) then there really should not be a need to look at the prior state of the code. In an ideal universe, the only things that should matter are what the code currently does and what is being requested that it do new or differently.
That's about as charitable as I can be to their take.
I've been trying to create clean metadata for a collection of Blu-ray rips recently. The MKV format has a bunch of defined metadata fields but handling of it is inconsistent between players. VLC seems to be the worst in that it doesn't even bother displaying important pieces of the metadata. You can work around that by effectively duplicating the important parts in the track name, but then other software ends up doubling up on that because it's displaying both the track name and the values pulled from the other track metadata. And I'm being driven crazy on how I should use the subtitle track flags that indicate if a track is Forced or Default, because it seems like the auto-selection behavior based on those flags arbitrary from player to player.
I should probably just give up and let it all be a mess. Not sure I'll be able to though. The only thing that freed me from metadata obsession when it came to my music collection is that I switched to streaming services.
> And I'm being driven crazy on how I should use the subtitle track flags that indicate if a track is Forced or Default, because it seems like the auto-selection behavior based on those flags arbitrary from player to player.
Oh, this seems to be more or less completely ignored when selecting subtitles, though some players will at least list "English (forced)" or "English (default)" &c. when selecting a subtitle. Quite a pain with dubbed foreign-films when the subtitles are used for translating on-screen text; you really want the forced subtitle in that case!
You almost always want to see what's in the forced subs; but if you're reading a different language then it has to be translated first.
Also compression and color/HDR mapping prefers the text be separate from the image.
It's just plain lazy devs. They do that crap on Windows too despite having conventions for where the stuff goes since Windows 98 (though Photos and Videos folders were introduced with XP, and Game Saves with Vista).
The folder for config is even older. CSIDL_APPDATA has been able to be used to get the path to the AppData folder since the update for Windows 95 that added Internet Explorer 4.0.
I prefer CachyOS. It's basically an easy-to-use Arch distro. They package more than the default Arch repos contain which helps a bit in avoiding building stuff yourself out of AUR.
I tried Bazzite, but I'm just not a fan of how everything is installed as a flatpak. It might be more secure and allow for easy rollbacks and stuff, but it limits what apps are allowed to do by default. The main issue that caused for me is that the 1Password Firefox extension was not able to communicate with the main 1Password process. Maybe I could have tinkered with it using Flatseal, but that feels like such a hack.
Sorry for commenting about the page itself, but did anyone else have to go into reader mode to read it? The page is bouncing up and down, the text is extremely blurry and varying in size letter by letter, and every element seems randomly slanted.
reply