There's already people doing unofficial builds of Tchap which work against the public Matrix network rather than the .gouv.fr deployment - e.g. https://github.c

There's already people doing unofficial builds of Tchap which work against the public Matrix network rather than the .gouv.fr deployment - e.g. https://github.com/14mRh4X0r/tchap-android https://github.com/14mRh4X0r/tchap-android and https://git.snt.utwente.nl/14mRh4X0r/tchap-proxy https://git.snt.utwente.nl/14mRh4X0r/tchap-proxy, although I'm not sure it's useful yet as more than an interesting experiment. On the riot side, we're trying to do our best to make it support both Barbecue as well as Banquet use cases (assuming that's not a contradiction in terms). In terms of other points: > Having one homeserver per device would solve most of my issues pretty neatly. I am not sure how far it is in the roadmap. It's in the 'further still' column - we published the roadmap last week at https://matrix.org/blog/2019/02/15/publishing-the-backend-roadmap https://matrix.org/blog/2019/02/15/publishing-the-backend-ro... - look for the card labelled 'p2p homeservers'. > - There doesn't seem to be easy ways of migrating: accounts, homeservers (including address and implementation, ex. migrating to/from synapse, Dendrite, Ruma...). There are scripts to do it, but it's a bit crap (similar to migrating between IMAP servers). We're working on fixing it properly via MSC1228 (https://github.com/matrix-org/matrix-doc/pull/1228 https://github.com/matrix-org/matrix-doc/pull/1228) > No easy way to manage multiple identities Multiaccounts are next up for Riot. > The search functionality is really lacking on most clients yeah, we need to fix this.