| 11 Jan 2020 |
 Sorunome | Als Antwort auf@tulir:maunium.net
clients can have a separated list for the unimportant users sounds like you are introducibg a problem which was solved with the bot iser not being in tge dm: not all clients doing that (labeling as 1:1 / hiding bot user) | 15:24:17 |
 tulir | In reply to @jan.christian:gruenhage.xyz
So why do we even have appservices at all then? It sounds like you're arguing against the whole appservice spec here controlling many users easily is still needed, but yeah | 15:24:34 |
 jcgruenhage | IMO, receiving a stream of all PDUs and EDUs from the ghosts would make sense. No need to have a separate user for that | 15:25:25 |
| jcgruenhage | There is a need for that right now, but IMO there shouldn't be | 15:25:44 |
| tulir | In reply to @sorunome:sorunome.de
sounds like you are introducibg a problem which was solved with the bot iser not being in tge dm: not all clients doing that (labeling as 1:1 / hiding bot user) controlling thousands of e2ee devices is just ridiculous though | 15:25:46 |
| Sorunome | Als Antwort auf@tulir:maunium.net
unless you do some very dangerous shared bridge rooms, the bridges are basically separate and can have their own bots imagine mx-puppet-bridge only wit an additionalx-puppet-client so that people can self-host the protocol part to not give the matrix server their credentials for the remote protocol. As soon as you have multiple connections (users) you'll need multiple e2ee devices
| 15:25:57 |
| tulir | In reply to @sorunome:sorunome.de
imagine mx-puppet-bridge only wit an additionalx-puppet-client so that people can self-host the protocol part to not give the matrix server their credentials for the remote protocol. As soon as you have multiple connections (users) you'll need multiple e2ee devices
yes, those are all separate bridges that can have a single device each | 15:26:27 |
| Sorunome | then everyone would need theor own bridge and thus appserver | 15:26:49 |
| tulir | it would basically be user-hostable bridges (a kind of proxy) without actual support in synapse | 15:26:51 |
| Sorunome | áand thus synapse | 15:26:54 |
| tulir | In reply to @sorunome:sorunome.de
áand thus synapse just no | 15:26:58 |
| Sorunome | yes? | 15:27:04 |
| Sorunome | need to be registered somewhere | 15:27:10 |
| tulir | In reply to @tulir:maunium.net
it would basically be user-hostable bridges (a kind of proxy) without actual support in synapse ^ | 15:27:13 |
| tulir | In reply to @tulir:maunium.net
no, just add user-hostable bridges ^ | 15:27:21 |
| Sorunome | that sounds like a WAY bigger msc etc. than just sending those events from all ghosts....which should be done anyways | 15:27:53 |
| tulir | In reply to @tulir:maunium.net
it would basically be user-hostable bridges (a kind of proxy) without actual support in synapse ^ doesn't need any spec changes | 15:28:24 |
| tulir | but of course user-hostable bridges in the spec would be good to have eventually | 15:28:43 |
| Sorunome | how do you plan that then? | 15:28:49 |
| jcgruenhage | Oh right, because you add a layer of unspecced stuff in between | 15:28:53 |
| Sorunome | if you only want a single device for an entire AS bot then you need multiple AS bots....thus multiple bridges.....thus you need to register multiple things in synapse.....thus goes against the concept of a publically hosted bridge | 15:29:22 |
| tulir | In reply to @sorunome:sorunome.de
how do you plan that then? your suggestion of a mx-puppet-bridge and mx-puppet-client sounds like pretty much that, a proxy that gives access to a sub-namespace | 15:29:22 |
| Sorunome | yes, but you need multiple devices | 15:29:40 |
| Sorunome | one per sub namesapce | 15:29:43 |
| Sorunome | but teh AS bot is combind oer all | 15:29:51 |
| tulir | AS bots aren't special, just register a new account per sub namespace to act as the AS bot | 15:29:53 |
| tulir | I guess that EDU proposal could just send the to_device stuff to all puppets to make that easier (have the bot in the namespace too) | 15:30:29 |
| tulir | but then just use it for a single device per sub namespace | 15:30:45 |
| Sorunome | In reply to @tulir:maunium.net
AS bots aren't special, just register a new account per sub namespace to act as the AS bot ah, yes, that could work......BUUUUUT that would mean taht the AS bot would ahve to be in EVERY room which, as soru pointed out, is highly undesirable | 15:30:58 |
| tulir | managing thousands of e2ee devices is far more undesirable | 15:31:20 |
