Fedora gives you a secure and functional desktop distro out of the box while with Arch, you can get that as well but have to invest more configuration time, since you have to configure things like Secure Boot, SELinux, disk encryption, firewalls, AppArmor and other security stuff by yourself, it's not going to have all that jazz by default, since Arch is a minimalistic and modular DIY-like distro, so it's up to the user to configure this. Arch doesn't put obstacles in the way of the user but also doesn't just preconfigure this stuff. But it's all there if you need it. Arch also offers a linux-hardened kernel variant which uses various hardening patches of the GrapheneOS project for the kernel (not sure if Fedora offers this as well).
Experienced Linux users tend to like Arch's approach because of more flexibility, modularity and minimalism while still offering everything necessary, but the less experienced of a user you are the more you probably will have problems with this approach, and the more you want more things to be pre-configured out of the box, so that you as the user have to configure less stuff. The more you view it that way, the less suitable Arch is for you.

But both are excellent and modern distros. Fedora is generally for people who want to generally spend less time configuring their desktop distro. Arch is for people looking for either a more universal distro or something more modular, technically simple and customizable.

The RedHat backing of Fedora can be a blessing (lots of great stuff came from RedHat so far) but also could become a curse soon due to IBM's influence (which bought RedHat some time ago, and IBM isn't such a great company, and this can negatively impact RedHat as well) and current US politics (it's a US-based company). Arch, on the other hand, is even more independent than Fedora is and it's a fully community-run distro, and from all community-run distros, it's of very high quality, similar to Debian. Both Debian and Arch are also quite democratic in nature. If IBM hadn't bought RedHat, and US wouldn't be like it is today, I'd maybe view this differently but as it is I'd rather use a community-run distro than a US-corporation backed one. Even if Fedora is still very independent as a project, or so it seems.

If you're very well familiar with Arch there's really no need to switch to Fedora, but it can save you some time or configuration trouble overall in some cases, while it could also mean more potential trouble with major upgrades than with Arch with its frequent but lightweight updates all the time and never a big major version upgrade because Arch has no versions at all, it's purely rolling, whereas Fedora is a mixture of rolling and point release. That said, if you update your Arch very infrequently (e.g. only once every couple of weeks), you will also have a higher chance of update troubles (though these are often easy to solve for an experienced Arch user, but can be crippling for a newbie). To benefit from Arch's update mechanisms, you have to update frequently, as in every couple of days, at the very least once a week. And you really should set up a fallback mechanism, e.g. via filesystem snapshots, so you can revert an update which went wrong. Although so far, one of my Arch installations here is like 7 years old and there were only very minor update issues during that whole time, all of which were solvable via downgrading a specific package, waiting 1-3 days for the fix and then upgrading that package. So I'd say Arch is much more stable than its reputation, but still, even objectively small update issues can be devastating for you if you don't know how to solve them, so it again depends on the user.

Another factor is probably going to be whether the AUR or Fedora's community repos have more of the additional packages that you need for your use cases, from the packages that aren't in the default repos.

Which of the two distros makes more sense depends highly on the user, the user's familiarity with Linux basics, the user's available time, and general use cases. I'd say both choices are excellent for a desktop distro, and Fedora would immediately become my daily driver if I ever became unhappy with Arch. Which so far hasn't happened.

Another option if you still can't decide between those two excellent distros would be an Arch derivative like EndeavourOS or CachyOS, which pre-configure more of Arch for an easier desktop use out of the box. So they are more like Arch of course (based on it) but trade away some of Arch's subjective "weaknesses" for Fedora's subjective "strengths". I say "subjective" because those weaknesses and strengths can be different for each user and use case. Sometimes this gets forgotten in discussions like this. It's not a clearly defined drawback if your distro doesn't preconfigure most stuff out of the box. Whether that is a drawback or not depends on the user. However I'd assume that most users probably prefer more pre-configuration. But still, one size doesn't fit all.

Well this got longer than intended but I hope it helps for decision making.

It may be fixed and perfect, now, but I will never forgive Redhat for RPM, and by extension, every derivative. Fedora. CentOS. Anything rpm-based. I'm not a huge fan of debs, either, but I have never experienced dependency hell as bad as on rpm systems.

Lots of people like it. It's really popular for installing on a desktop configured to run an obscure, but mission-critical, service, putting the computer in a closet, and then later walling up the closet so that the physical computer can never be found again. It's great, as long as you never upgrade it.

I don't think there is a way to forward cellular phone calls. You'd need a phone provider which provides that feature, like a Voice-over-IP provider. Or a SIM card in your computer. Plus the right phone contract.

Kdeconnect can forward a lot of other things though, like SMS, files...

I wish there was a way to hook into calls. But as far as I know they're deliberately keeping that closed.

EDIT: Actually, I've just tried Bluetooth and that does just about that. I've used the standard Bluetooth pairing within the GNOME desktop, and now my Android phone lists the computer in the audio optione of a call (where you can choose if it's phone, handsfree or via a bluetooth device... And I can click on my computer name there and it'll then use the computer's mic and speakers.

This is an XY solution but...

Telegram and similar services offer both calling and texting and can be carried across devices. It's linked to the same phone number, all folks would have to know is "between these hours call telegram"

Not by default, but yea it is encrypted, I use almost exclusively encrypted chats through TG, even my voice and video calls are encrypted through TG.

E2e encryption is security theater though, a chance for companies to tell states "We'D lOvE tO hAnD oVeR tHaT dAtA bUt ItS eNcYpTeD".

In reality, it doesn't matter, if someone wants to snoop on your convos you can't stop them.

Crypto works. Nobody can break good encryption.

You can make an argument for store now, break after quantum leap or whatever. But, no, if the US wants to spy on the communications of their enemies, they can't do it by breaking encryption.

Not sure if you'll find something that cheap, but RackNerd has some pretty cheap offers sometimes. Thing is, they don't seem to expire, so there's this: racknerdtracker.com/?sort=pric…

But I haven't tried them yet.
Also keep in mind the monthly bandwidth limits.
You get what you pay for, and $10/year is basically nothing.

Oh, and you may be responsible for random people's traffic depending on the provider. I think I've read in ToS of some VPS provider that you have to notify them about running a public service for this reason.

Its a concept called defense in depth. Without root login now you require the key AND sudo password.

Also, outside of self hosted you will have multiple people logging in. You want them to log in with their own users for logging and permission management.