| 18 Feb 2022 |
 hexa | more input welcome | 22:57:56 |
| hexa | * more input very welcome | 22:57:58 |
 f0x | added some more assertions | 23:43:07 |
| f0x | I think it would be great to support both option designs, perhaps make them mutually exclusive though | 23:44:23 |
| f0x | we would also need some way of handling the load balancing considerations when having multiple sync or federationReceiver workers | 23:46:46 |
| f0x | im considering writing some kind of proxy to handle the access token parsing for efficient /sync loadbalancing, because doing that in pure nginx became impossible with the new temporary tokens afaik | 23:52:57 |
| f0x | https://github.com/sandhose/matrix-doc/blob/sandhose/msc/refresh-token/proposals/2918-refreshtokens.md these are entirely opaque whereas the old (long) access tokens actually encoded the MXID | 23:57:27 |
| f0x | so you would need to do an http request or database access to figure out who the token is for | 23:57:41 |
| 19 Feb 2022 |
| hexa | In reply to @f0x:pixie.town
we would also need some way of handling the load balancing considerations when having multiple sync or federationReceiver workers ideally yes, but until that is possible we should resort to simpler measure, like hashing the src address of incoming requests | 01:07:27 |
