Most distros are running the same software. The biggest difference is your package manager & community. Personal preference is NixOS but that ain’t beginner-friendly even if the rollbacks from bad states would help. Arch isn’t as difficult to set up as it used to be & has been more stable than a lot of distros in my experience so I wouldn’t discount it but .pacnew files can bite you if modifying in /etc instead of in the home folder (when possible). Of the things folks normally suggest as a first go, Fedora would probably be my pick (not yet had a problem) as everything Ubuntu-based still rubs me wrong for support & leadership.
Signal will force you into using an Android or iOS mobile device—no alternatives—and you couldn’t have 2 Android devices (like a tablet, e-reader). You are forced to have a SIM card which gives away part of your identity. Servers are centralized & closed-source (closed for 2 years, rewritten history)—so did the NSA force in a backdoor? …We may never know. On Android, by default notifications are sent thru Google Service’s Firebase (fork Molly supports UnifiedPush now tho). The ToS is questionable with “don’t break the law” language.
Your ideal chat would be free software, P2P or federated+self-hostable servers, E2EE, & the only required personal info you share is your account ID (no phone or email).
You’d think Matrix fits the bill, but its high system requirements (especially storage) & majority Matrix.org mean defacto centralization around an org that controls the spec, the largest server, reference server, & most popular client.
What you are looking for is good ol’ XMPP with OMEMO or PGP set to required in all clients. Its server options run on a toaster, has years of smart engineering & open governance guiding the project, & being extensible by nature, means it’s not purely limited to chat/conferencing. XMPP appears to be the common chat option on the dark web for a reason. You can use gateways to puppet accounts on these untrustworthy networks too (such as messlidger to puppet Facebook Messenger is needed, but also Signal, Telegram, etc.).
Alternatively, Briar & its ilk are gotos, but P2P has some downsides (brains your battery hard on Android).
While true & I remember folks actually using this in arguments for ‘slow development’, there is some merit to versioning differently for something expected to get minor updates to perpetually follow latest specs such. I can’t imagine trying to discern what a “breaking change” would be in this context. Or would you make a new version for every visual redesign? Dates might have just made more sense, but maybe ESR is easier to follow with the current scheme.
Older Sony Xperia phones support LineageOS and have a headphone jack. Normally it isn’t until their 2-warranty is up that a LineageOS build is mainlined (likely because they aren’t high volume & are expensive). I got a III recently to running LineageOS for microG (but the proprietary camera app is missing).
Be aware that the cheaper ASUS Zenfones have a headphone jack, but are nearing a year since their bootloader unlock servers “went down for maintenance”. They’ll likely never come back.
Some alternative forges offer better features (or less social cruft) & are faster (some are not even limited to Git!)… what you will get is the ability to own the code & community along with set the terms instead of letting Microsoft set them for your community & be the gatekeeper for who gets to have access. If you wanted a corporate, centralized, proprietary forum go back to Reddit/Twitter; if you think that’s a terrible recommendation, in the same spirit you should leave behind corporate, centralized, proprietary code forges.
It’s not compatible with other Markdown forks, but the whole Markdown ecosystem is a mess duct taped together by more forks & extensions that aren’t compatible either. Even the common denominator CommonMark is feature-barren & isn’t suitable for documentation or technical writing, but boy howdy will the next guy have his Markdown contraption to sell you.