Slavi Pantaleev

It's possible. However, reconciliation work at the moment is focused on 2 things **about each policy user**: - current state (profile, membership data) - desired state (what's described in the...

I'm not sure I understand what the above nix configuration does, but anyway.. writing out the entire command sounds (`matrix-registration serve`, instead of just `serve`) sounds good.

I also started hitting this problem today for some yet unknown reason. What causes `ReflectionClass` to say the filename is `/.../.../vendor/friendsofphp/proxy-manager-lts/src/ProxyManager/GeneratorStrategy/EvaluatingGeneratorStrategy.php(54) : eval()'d code` and why does `CachedReader::getLastModification()` insist on...

I'm hitting the same problem with the Docker image. I've tried `collabora/code:3.4.0.8` and a few earlier versions. At some point turning logging up to `debug` yielded a slightly more descriptive...

Given that it's been at least 6 years and the font size is still exactly the same, it's obvious that element-ios' developers think that whatever the font size is now...

No upstream progress on these issues, unfortunately.

Good idea! It only makes sense if both supported login types (`m.login.password` and `com.devture.shared_secret_auth`) are enabled. We can then play around with the order and try to register `m.login.password` first....

See what else could be occupying port `8448` and preventing `matrix-nginx-proxy.service` from starting. `netstat -anp | grep :8448` may help. Perhaps you had a manually installed Synapse in the past?

So.. there is no issue in the end? Perhaps you did not see and do this thing mentioned in the changelog: https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/CHANGELOG.md#compatibility-break-changes-to-docker-src-permissions-necessitating-manual-action

`matrix-synapse-shared-secret-auth` supports 2 different login types: - `com.devture.shared_secret_auth` - `m.login.password` More details here: https://github.com/devture/matrix-synapse-shared-secret-auth#configuring The playbook intentionally disables `com.devture.shared_secret_auth` because of https://github.com/vector-im/element-web/issues/19605 You can use `m.login.password`, however. See the `m.login.password`...