| 18 Feb 2022 |
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 |
f0x | oh that's pretty good actually | 01:08:17 |
hexa | also I think there was something proxy-adjacent linked recently, I think by sorunome? | 01:09:37 |
hexa | https://github.com/Sorunome/matrix-synchrotron-balancer | 01:09:43 |
hexa | though that looks dated? | 01:09:46 |
Dandellion | its old and uses the trick with usernames in AS tokens IIRC | 01:09:59 |
hexa | so no good | 01:10:31 |
f0x | In reply to @dandellion:dodsorf.as its old and uses the trick with usernames in AS tokens IIRC it does use a whoami request so should still work | 01:12:04 |
f0x | maybe other parts changed though | 01:12:33 |
f0x | using a hash of the authorization header could work too? | 01:12:52 |