What they're saying there is that when trying to auto detect the server configurations, there are unexpected connections to cloudfare IPs, which didn't usually happen with K9. Who posted the concern associated this to telemetry, but the answers are pointing a different direction. But at this point it just guesses, :(

I guess some more formal traffic inspection needs to happen to understand if truly there's unexpected traffic, where it is directed to, and hopefully infer somehow its purpose. The guesses about what's happening suggest it's just about the auto connection, but again, just guesses.

I explored the configurations, and I didn't find anything about telemetry, and so neither how to disable it. K9 does not have an about:config advanced configuration like desktop Thunderbird does, so if there's truly telemetry or some other sort of information leakage, then after proving it, perhaps developers realize they can do better. But so far nothing really proving telemetry or information leakage.

Arkenfox user.js, or derivative broswers like Librewolf on the desktop and Mull on android are there for a reason. Firefox default settings are not the safer, although it has all the knobs to make it a much better experience.

There's as well !monero!monero@lemmy.ml which I guess halted in favor of !monero!monero@monero.town?

If this is the case, I'm wondering why not locking the community, writing a message in the community information to go to the actual active one (!monero!monero@monero.town)...

Not true, FF comes with few binary blobs which are removed from Librewolf. Also there are some things disabled entirely at build time, so they are removed from being an option. So it's not just the settings, and it's not plain re-branding. Some distros has gotten it wrong, believing that it's just a matter of settings, but at least on the case of Librewolf and the Tor browser that's not the case.

That hey depend on FF continuous development to exist is true, that doesn't mean they just rebrand.

Source Mage GNU + Linux (external wiki)

Correct

Jami doesn't require a phone number, which is p2p. Xmpp (+ Omemo) doesn't require a phone number and it's federated... I mean, if a service is willing to rid of phone numbers, it'll do totally without them.

I recommend you to explore sourcehut as well, if you're not afraid of something different to gitlab/github workflows.

Alacritty (with screen if I need a multiplexor)

Is it normal that on an upgrade, users are forced to re-login?

1.- jami 2.- xmpp + omemo 3.- matrix 4.- signal

It's hard no one cares. Where I live everyone uses whatsapp, and unfortunately what comes closer, and still without enough users base is signal on my list, and it's the last. Jami is distributed, which makes it best in class, and there are good efforts trying to make it not to steal the whole battery, as opposed to briar. I which more people were interested on not using centralized stuff, not even what has been called lately decentralized, which means centralized but with several central points (only if everyone self hosts it would be decentralized, which is not the case). Currently I use Jami and signal, though I've tried all those, plus briar, plus tox, even telegram...