Be especially aware of the mandatory backup (!) this time
since during upgrade your account data is migrated to a new state and you should not downgrade again with the migrated accounts.
So the developers actually announced it. That’s fair, but in my opinion, wasn’t enough, because many (including myself) don’t follow changelogs of every piece of software they have installed, or do backups before upgrade, or they have automatic upgrades. Before I realized what’s going on, it was too late for: me, mother and a friend of mine. A warning should be shown after upgrade and before migration, clearly explaining the consequences and suggesting to make a backup just in case, let such a huge change not be overseen.
Now if I want to stick with 1.x, my only choice is to use broken database, which indeed causes problems (i.e. double chats). There’s no tool or instruction to reverse the migration (prior to my knowledge, I assume it’s reversible). Apple users are in even worse situation, as they have no word about what version to use.
The Dhammanana’s writings are really hard to read and understand, written most likely using some poor machine translation, with a lot of political phrases in it. If I understood the intention well, the DC community has divided by the ideas how DC should evolve and 2.x update is the most controversial one in the history. In the Drop classic email support - #21 by adbenitez forum thread we can see many responses of people who disagree with the new direction in favor of so-called security but against interoperability. One way was chosen officially and many are upset. If the project maintainers won’t find a way to satisfy both groups, while not perfect – maybe it’s time to run a fork…
Actually there’s already Arcane, WhatsDown, also unofficial clients with its own codebase. They exist for a reason. We could reach them to save the effort of running and maintaining a completely new fork.