Open MurzNN opened 7 years ago
IMO such multi-accounting is more up to synapse / riot than puppet bridges. See the issue that referenced this.
I know about multi-accounting feature request in Riot client. But this feature request is for matrix2matrix bridge, that provide completely different another usage behavior of multiple matrix account - this way will organize whole conversations of several Matrix accounts in one master Matrix account, instead of splitting it between many accounts.
Another usage of matrix2matrix bridge is technical accounts. For example, our company have 100 sellers, 2 stocks and 10 showrooms-shops. Each day each shop have different seller, so too difficult to remember which seller now in needed shop. Solution is to create separate matrix accounts per shop, like '@shop-14', '@shop-26', etc, but with this way sellers will lost his private history and rooms, because accounts will be shared. Best way will be keep personal accounts for each seller, and auto connect to shop accounts (on user login on shop computer event) via some matrix2matrix gateway.
I am an admin of 3 companies, in each of them I install separate homeserver with Matrix synapse and LDAP authentification.
So now I have 4 Matrix accounts - one on
@murz:matrix.org
and one per each company like@korepov:company1.com
,@admin:company2.com
,@korepov-a-v@company3.com
and I want to talk with employees of each company from corresponding corporate account.Using 4 Matrix clients for this is too uncomfortable.
Good solution will be use something like
matrix-puppet-matrix
bridge, in which I can use master account and connect to it other accounts as slave. So users of slave account for me will have addresses like@matrixbridge_user_company3_com:masterdomain.com
and I can talk with all of them from one Matrix client and one account, and they will see me with address incompany3.com
domain, not inmasterdomain.com
.What do you think about this problem and provided solution?