What RAID system did you use which corrupted your data on power loss? With software raid like zfs I believe corruption on power loss shouldn’t be a problem (unless the hardware fails. Or your using btrfs raid 5/6, ignoring all warnings).
Edit: For this reason I’m looking into buying another drive for an offline backup of my media files. I could redownload them, but it’d be increasingly more annoying.
If you want better speeds and quality I recommend looking into TorrentLeech, FearNoPeer and similar private trackers.
Sometimes BluRay remuxes aren’t available or well seeded on public trackers, while they aren’t even counting against your upload/download ratio on the above trackers (On TL, FNP big torrents are freeleech).
What is the video bitrate of movies/shows in the share? Does it support transcoding or are they only doing direct stream?
I’m curious because OP wants higher quality and to save space I’m usually using similar bitrate as commercial streaming services for my media library.
Most people using these sites prefer the lossless codec flac anyway, which can be transcoded to anything.
MP3 320kbps and MP3 V0 is transparent to most (all?) people, so there’s not much of a reason to go with a newer codec, except for space savings.
There’s not even much of a reason to go with 320kbps, as V0 achieves the same quality with smaller files. That’s why almost nobody actually downloads MP3 320.
I personally think MP3 is there for historical reasons, as I don’t see a reason for using lossy codecs for archiving purposes. Just download flac and transcode it once or on demand on a media server for streaming.
Not natively, as far as I know. NTFS works well on Linux for the most part (unless you need permissions), but macOS natively only supports reading.
FAT32 is universally well supported, but the partition size limit and 4GB file size limit make it unusable for me.
Linux filesystems as well as macOS filesystems aren’t supported natively anywhere else, so ExFAT it is.
ExFAT does make sense, since it’s the only filesystem which supports read and write on all major OS. Sadly it’s also pretty basic, and thus not the first choice on any OS - except for USB sticks.
I generally recommend formatting any new storage media before using it. Just to make sure it’s properly formatted to work with my machine, and the manufacturer didn’t mess up their implementation for some reason.
What format did the drive use? HFS+?
fclones is fast and supports hardlinking/softlinking of duplicates instead of removing them.
I’ve used it successfully to deduplicate my documents folder (and “archive”).
As its quite the amount of data, I recommend using the --cache option to make subsequent runs way faster, if you want to dial in the options. This directory can be deleted at any point and isn’t necessary.
tl;dr
Read the first sentence after each citation ;D
So Wayland, a protocol, is needing the addition of other protocols?
Yes. What we know as Wayland is the Wayland core protocol and a few other protocols that are absolutely necessary for desktop use (stable).
Then there is staging, which is not necessarily implemented by all compositors, e.g. fractional scaling.
Unstable also exists, which is even easier to get a protocol into (idk the exact requirements, likely the amount of support and explicit dislike by contributors).
These are often only used by a subset of compositors with e.g. XDG decoration allowing compositors to announce to clients (windows) that they support server side decorations (top bar with close/minimize/maximize buttons). This isn’t implemented by Gnome, but most other desktops support it.
Different desktops also have their own protocols, which are published so that apps targeting those desktops can implement them. Some are also supported by other desktops, if they think they are suitable for them.
E.g. wlr layer shell makes status bars possible, which are used by basic compositors like Sway or Wayfire. KDE also supports it, even though it was originally created by wlroots.
Does this make it a Wayland Distro?
In a way you could say that a compositor is a Wayland distro, as it implements a subset of Wayland protocols.
In the end this is good, because it allows for rapid development and discontinuation of protocols. E.g. if a better protocol comes around, both protocols can be supported at the discretion of every compositor.
The goal was to solve the problem of X11, where Xorg still has to support drawing UI by itself, even though no program or toolkit uses it anymore (the 80s were very different). The Wayland core is so minimal there shouldn’t be any issue with using it for a very long time.
Also, Wayland was developed by people with the goal to use it in automotive and other industry applications, where basic desktop functionalities, like multiple windows or session lock, aren’t useful.
It’s more so that you are allowed to try to block ads. If YouTube adds DRM or otherwise manages to stop usage of ad blocking, they are completely in their right to do so.
IIRC if something runs on your system, you have the right to mess with it, however you want — e.g. block specific parts of the site, or use reader mode etc.
That’s one of the reasons I don’t like buying games with Denuvo. Waiting a few years before buying games is something I usually do anyway, so at that point Denuvo DRM would’ve already been removed.
I’m honestly fine with DRM, as long as it’s removed within my definition of reasonable time. I’d say a year vor two.
Once the DRM is removed it allows for archiving and preserving the piece of media — as well as pirating copies.
Really very similar to Lemmy, where the identity of each group is tied to a particular server, e.g. lemmy has [email protected] but Matrix has #anime:matrix.org
So what happens if matrix.org goes away or decides the server admin wants to be hostile to #anime?
A matrix room can have multiple identities/adresses set by the room admin. E.g. the admin of !anime:matrix.org could add another adress for the same room on !anime:myanime.instance. Because the room is replicated on all other participating servers, this would let the room continue to exist on the network (besides all matrix.org users not being able to access it).
Matrix does have a single “room id” per room, which looks like it gives the original creating home server more rights, which it does not. E.g. !ehXvUhWNASUkSLvAGP:matrix.org
Any server admin does not have any more rights over a room than another server admin. They can ban the room for their local users, but this does not stop federation as a whole.
[1] https://github.com/element-hq/element-meta/issues/419
[2] https://app.element.io/#/room/#synapse:matrix.org/$htJmba92wLTP9AoFg4eEWi9IXpgwvXr6G9Sa-kBsNNs
[3] https://matrix-org.github.io/synapse/latest/admin_api/rooms.html#delete-room-api
It also appears that anything beyond text has to be hotlinked […]
Matrix allows for media to be hotlinked, but it can also be replicated across servers.
I.e. if I send an image in a room and look at the source (available on many web clients), the image url looks like the following "url": "mxc://matrix.org/qGgUKuZuHcRsWAhSfqKnmtiX". The actual image (and preview) then gets fetched by your server from my server [4], and then gets send to your client.
It’s important to note that a server isn’t required to download all media. If a user does not read a room, it might not download the media from another server, until the user actually wants to view it (or rather that part of the room history). Or a server admin might clean up the media store to free up space.
[4] https://matrix.org/docs/spec-guides/authed-media-servers/
They do basic checking for known malware.
You’re right. I’ve read somewhere that Apple plans to work with GSMA to add encryption to the official RCS standard, so this major issue hopefully gets fixed at some point.
RCS isn’t E2E, and it doesn’t minimize metadata.
Moxie Marlinspike has been strongly against federation in Signal because of how it makes avoiding metadata almost impossible.
I’d say there’s basically zero chances Signal will add RCS.
I’d argue XMPP is less ideal than Matrix because groups are located on a single server, which makes them easier to take down than Matrix’ replicated state.
Running any P2P/decentralized protocol over I2P seems to be the best for privacy and censorship-resistance. I2P already works great for torrents, except for it’s speed and lack of users/seeders.
The problem always comes down to usability and barrier to entry. Telegram is popular because it’s great to use, and doesn’t moderate much. More private services rarely (never?) reach the level of usability most people expect, often simply because of it’s architecture.
Well, it seems my reading skill deteriorated to a surprising extent. You’ve even mentioned handbrake in your post…
Building MakeMKV seems to require a binary, which is unfree. I assume this is the reason it’s not in official distribution repos (except Nix and FreeBSD).
It’s in the AUR and Nixpkgs, both automate building it from “source” (+binary). MakeMKV is in FreeBSDs official repos, according to pkgs.org.
I agree that there are many great free streaming sites out there, with 1080p and good quality.
But quality is still an advantage of paid services (or acquirung the larger files in other ways). Streaming with higher bitrate costs way more bandwidth (= money) while being marginally better.
It’s noticeable though, if you have a good, large enough display. Especially darker scenes suffer from low bitrate. On my phone I don’t notice it at all.
That’s even true for high bitrate. E.g. I’ve even compared a Reacher WEB-DL to BluRay remux, and the latter was noticeably better — not that it’s worth the additional storage usage.