Re:Drawbacks of P2P and a defense of Signal
by sweden on Sunday January 31, 2021 @04:03AM
(#25977296)
Which file are you talking about? The homeserver.yaml?
Mine only has around 100 lines without comments.
Re:Drawbacks of P2P and a defense of Signal
by MayeulC on Sunday January 31, 2021 @09:40AM
(#25979131)
Probably the homeserver.yaml file, as yaml is a standard format where indentation matters, and is always 4 spaces.
# cat /etc/matrix-synapse/homeserver.yaml|wc -l
1611
# cat /etc/matrix-synapse/homeserver.yaml| grep -v '^\s*#\|^$' | wc -l
101
The config file is just well-commented.
Every part of setting up a server that will federate/host repeats again and again that you need a TURN server (and they recommend coturn) - which is another 26,000 character config file - in order to do VOIP. If you've ever run or used a pbx before, STUN is needed 100% of the time for nat traversal between clients. Coturn even says it won't run if it's NAT'd (it will, but that's irrelevant to most people.)
This is the fourth concurrent tech trial of chat daemons, with rocket.chat and mattermost being a couple of the other ones that we're testing. synapse/element/matrix has the benefit of forced e2ee by my configuration. I don't know of any other matrix federated servers, so i haven't tried that yet, but an associate says it works on my configuration - which means it's not as big of a pig as i thought it was based on the outlandishly, comically large config file - where whitespace matters!