Mathijs van Gorcum

I think the error is that synapse can't bind to your homeserver name, though I'm not entirely sure. You have: `server_name: "tomeChat"` If you want synapse to work right this...

STUN worked for me using only ports 3478, 5349 forwarded to the container, but this only worked for a few simple NATed clients. You can test your server [here](https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/) if...

I never used docker swarm, so I can't comment on that. I did reduce the port range with min-port and max-port in turnserver.conf (I think I 'only' forward a couple...

The current canonical way to link to matrix rooms, users, or events is to use matrix.to, see [here](https://github.com/matrix-org/matrix.to)

The matrix server does indeed supply the client with an access token upon login, which can happen through some form of SSO just fine, but sharing access tokens between sessions...

Yes, for some reason seaglass wasn't showing some new messages that did show up in riot. However, after a restart the issue seems gone. I'll report back if the issue...

Right, so after restarting the issue resurfaced, see attached screenshots. 

I did a bit more experimentation, and I think I found the cause of this issue: The room in question was added with the `production.yaml` config, but not through `!mjolnir...

Happy to help!

You may want to have a look at what [davx5](https://www.davx5.com/manual/introduction.html#permissions-and-battery-optimization) [does](https://gitlab.com/bitfireAT/davx5-ose)