Well obviously, seize the means of production?

1. Fedora has a major update every 6 months, and every version is supported for 2 releases + 1 week (= ~1 year).
   Updates have always been pretty painless for me. Most of my problems during updates have come from NVidia drivers (on a laptop), but a fix has always been available from the community.
2. Fedora has auto-update systemd services for both DNF and RPM-OSTree (more on this later). IIRC it's just enabling a service and maybe editing a config file, but this is easy to search for, so I won't tell you stuff I might not remember.
3. SELinux mostly just works, and if it doesn't it's probably a bug (if something is a package for Fedora, SELinux should work OOTB. Browse Fedora Magazine for the quirks you need to know how to handle.
4. I have no experience with ARC GPUs but Fedora might have better support as it tracks the latest kernel release = latest driver (depends on what was actually the issue, of course)

Concerning you RAID, just make sure the installer doesn't touch it and mount it afterwards. You might have to do some kind of "restore" to give the files the needed SELinux metadata. The Discourse forum would probably be a good place to ask.

Now, a bit about DNF vs RPM-OSTree. Fedora with DNF is the standard distro much like most other distros. Use this if the next part doesn't sound useful to you.

RPM-OSTree is used in a new family of distro that work a bit like git for your OS.
Your system runs off an "atomic" image. Atomic means unsplittable in Greek. Everything you change on your system is applied to your atomic image, like a file is added or removed from a git repo.
This is nice because upgrading to the next major version becomes a simple matter of rebasing you changes on top of the new version, and likewise, rolling back (in case of issues) becomes a single command and a reboot.

Fedora IoT is the "Server" edition of the Atomic desktops. Fedora CoreOS is a more "immutable" approach.

Feel free to ask more questions if something doesn't make sense.

Yes it is (sadly) very different for phones.

When an the OS for an Android phone is created, the Linux kernel is forked, and the firmware/drivers for it's hardware components are laid on top (instead of being upstreamed to the kernel). When the manufacturer decides they no longer care about that phone, they stop updating firmware and that will no longer receive updates. You might use a rom that still updates everything else, but these critical parts won't get updated anymore.

The newer Pixel generations get 5-7 years of security updates (IIRC). I believe IOS devices get 5 years.

Android and arm has (/had? I might be partly out of date) a lot of out of tree (not included in the upstream Linux kernel) code which makes booting it on Linux a shit show.
This is also why so few devices are supported by the Linux-phone-OSs.

Thanks for the recommendation, stranger. I'm gonna watch that!

No problem!

I hacked this together instead of going to sleep, so it might make your deck explode, but maybe it's a starting point for you or someone else:

# home-deck-mounts.mount
#
# Mount units must be named after the destination path, this / replaced by -, like above
#
# This is a template unit.
# That's explained here: https://fedoramagazine.org/systemd-template-unit-files/
# TL;DR: run it like this `netmount@linuxisos.mount` if you want to mount the subdirectory "linuxisos" from SHARE_PATH
[Unit]
Description=NetMount %I
After=graphical.target
# This is commented out, because it is implicit for network mounts https://www.freedesktop.org/software/systemd/man/latest/systemd.mount.html#Default%20Dependencies
# I keep it here as an example
#After=network-online.target
#Requires=network-online.target

[Mount]
# %i expands to what ever you put after the @ when starting/activating the service
What=10.10.10.99:/mnt/user/%i
Where=/home/deck/mounts/%i
Type=nfs
Options=exec

[Install]
WantedBy=default.target

I couldn't confirm if mount units are allowed to be template units, but if not, just duplicate the service for each path and replace %i.

Say the word if you run into issues!

Don't put yourself down! Using systemd wouldn't make it work "better", it's just more "proper" (and a great tool to know in general!)

Great job and keep going!

Nextcloud doesn't verify your email and has tons of other nice features as well. ProtonDrive (/ProtonMail as another user suggested) probably doesn't or you could use your Proton address for that.

You mention allowing weak passwords are a plus. Please use a weak password, especially without email as 2nd factor.

Have you considered using mnemonics for your passphrase?

Generate a number (i would use around 5) of random words (EFF has a wordlist, humans are really bad at randomness) and link them together using silly images. For example:

• sparrow
• window
• automobile

First, you link sparrow to window: imagine a sparrow trying to break through a window, not just flying into it by accident, no, this sparrow is mad and is set to destroy it.

Second, you link window to automobile: imagine an automobile with huge windows. The car is completely normal sized except every window is at least 3 meters tall. It looks absolutely ridiculous and you feel embrassed that youvhave to drive it everywhere.

Repeat this proces for the rest of the words. It helps remembering them if the image makes you feel something, like making you chuckle or feel angry that you have to deal with this stupid contraption (only in your mind, hopefully)

Also, make sure each "link" is distinct. Eg. Don't make the second link an automobile driving into a window when the sparrow does the same. It will mess up the order and make you jump around between similar mental images.

You can also just pause it and change filament manually.

Just remember to push through some of the filament until the color comming out is right.

I don't know about Australia, but in the countries i have heard about with compulsory voting, it's totally legal to vote blank, i.e. not actually vote for anyone. You just have to go to the polling station and put your blank ballot in the box.

So you're (if i'm not mistaken) not forced to vote for a party you don't agree with.

Because they will quickly use up a ton of storage just for showing other instances content, or did i misunderstand you?

That is a good question, but methods like pruning old content from other instances might evolve into a path for solving this (very real problem).

Federation as it stands right now is a terrible system.

I beg to differ. Right now federation is an okay solution. My proof is that it at least works, and that the problem you mention isn't killing the fediverse (yet).

We should not forget that ActivityPub is a W3C standard, (which itself is a huge milestone for a decentralized internet) and like other similiar standards (eg. HTTP) it can be iterated on and improved when solutions to new or old problems are found.

I must admit i don't know exactly what is and isn't in this community, but The Pirate Bay ended being closed because it "facilitated piracy" or something like that. (Of course it didn't actually close but the legal loophole was closed, so legal action could be taken)

I don't remember details but essentially it was decided (in some court, somewhere, i guess) that linking to illegally copied material was also illegal.

IIRC the new loophole became encoding the link to what ever you wanted to copy, for example as base64. That's what's done here, right? (Please correct me if i'm wrong)

My point is that this may, in a legal sense, actually be spreading copyrighted material, and the risk of being sued (no matter if you are in the right) is a very good reason to not run the risk, since the legal system favors deep pockets and good lawyers over challenging the limits of the law.

For good measure, i want to point out that i am absolutely for the free sharing of knowledge and culture. The whole world gains from free access to this. I just also sympathize with not wanting to be a martyr in this battle.

Also, as the person i replied to earlier made me aware, the admin of LW is apparently a homophobic asshole, so fuck that guy.

By circumstance.

It was hard for me initially to switch over because i kept either creating or running into problems i couldn't figure out how to solve.

This overlapped with the Snowden leaks and i got really interested in privacy and security which lead to me running Qubes OS[1] for a short while. It was a slow and almost painful experience since i didn't actually have anything worth that effort to protect - but it got me over the edge and i wiped Qubes and reinstalled Fedora 23.

At the time i just liked the package manager better, for reasons that are no longer relevant.

Today i like it because it forces me into good habits of: figuring out what exactly is misbehaving > finding the official documentation or issue tracker for it > finding a solution or reporting the it to the developers.

Don't tire yourself out with that in the beginning. Just do stuff you need or stuff that seems fun.

Protip: Learn how to use Toolbx or Distrobox to create a "sandbox", (that's both the technical term and a very descriptive one) that will make it easier to get back to a working state if you mess something up. Learn about and understand what it can't get back to a working state. This will help keep you sane if you like to tinker.

1 A Linux-like operating system that only runs VMs and everything you do happens inside one of these. This way you can isolate you virtual "work computer" from your virtual "personal computer", making it harder for malicious programs to access the rest if your data.