tchap-android-legacy

myself [2]. I'll look a bit more into that nevertheless, and it should improve by June, from the article. Regarding the second one, someone recently linked to this Gnome mailing list archive [3] where (in the reply) Matthew details a bit more his (then) long-terms plans for homeservers. Having one homeserver per device would solve most of my issues pretty neatly. I am not sure how far it is in the roadmap. I am also curious to know what's the status on that specific discussion topic: I was discussing just this the otherday on #postmarketos-offtopic:matrix.org [4]. I was interested in having a unique matrix daemon on a phone operating system to provide push support, maybe as well as a Matrix protocol broker. Otherwise, for self-hosting with ~10-200 users, it looks like synapse has shed a lot of weight recently, and other homeservers implementations seem to be picking up steam, so we'll see how that goes. I am not sure how synapse would handle a dynamic IP For now, my gripes with the ecosystem are the following: - There doesn't seem to be easy ways of migrating: accounts, homeservers (including address and implementation, ex. migrating to/from synapse, Dendrite, Ruma...). - No easy way to manage multiple identities: work, home, etc. Multi-account clients or community-bound identities could probably help solve this. Ideally, it would be the later, and my account would be on multiple homeservers (backup plan for availability). - The search functionality is really lacking on most clients. No way to search my own messages, or at a specific time, in a specific community, etc. It's also kind of fun to have both COI (chat over IMAP) and Matrix making the front page at the same time :) [0]: https://fosdem.org/2019/schedule/event/matrix_french_state/ [1]: https://blogs.gnome.org/tbernard/2018/05/16/banquets-and-bar... [2]: https://github.com/dinsic-pim/tchap-android [3]: https://mail.gnome.org/archives/desktop-devel-list/2017-Sept... [4]: https://matrix.to/#/!VTQfOrQIBniIdCuMOq:matrix.org/$15496441... A bit off-topic, but my registrar doesn't provide an API to update the DNS records on their servers. As a workaround, would there be a free dynamic DNS with an API out there? I don't care what the address would look like, as I would just use it as a CNAME record.