@strypey 3/3
This makes the future needs of design (if they keep going this route with every other connection type) simply incompatible with using traditional email services.
It is a user pain point right now, and I think their messaging has been rather nonexistent as to the big plan - just upgrading the app from say 2.53 to 2.57 broke people. That's a 3.x release right there in semver standards, the DC devs are playing fast and loose with their users and it shows.
@nokke
> Good old port 25 is the Achilles heal. Email ports are just too easy to target for any regime
This too seems like a good argument for using XMPP instead, or especially Matrix, which is a web protocol. So I presume it would be harder to fingerprint than either email or XMPP.
> the DC devs are playing fast and loose with their users
That's my impression too. But what I'm wondering is, why?