Current problem
Currently to connect to self-hosted instances you need to switch accounts which effectively silos your communication to whatever instance you are signed into at the time. When self-hosting ramps up fully you will likely see a large number of communities self-hosting a server for 1 or 2 guilds and people joining maybe 1 guild of a larger self-hosted community.
This means that to check all your channels and respond to messages across self hosted communities you end up switching accounts every 2/3 minutes, with the potential to miss notifications/calls as the clients reconnects to a different community. (There is already a bug report about not disconnection calls as you switch accounts, as an example)
Proposed change
Ideally the client would be able to connect to multiple communities at once (like the way irc clients work) and show a combined view of active guilds/notifications/calls. Backend-wise, there would really be no difference as the client would still fork out a ws connection per logged in instance.
Platform
macOS, Windows, Linux, Web, Android, iOS, Self-hosting
Additional information
Some things you could look at doing with this:
- Updating status would do so across all logged in instances (configurable)
- Handle per self host instances profiles editing
- Mark each guild with the self hosted instance logo
Comments
No comments yet.