Synapse VS Rocket.Chat

I think thats the exactly the point. It depends on how you use it. Matrix is a protocol at first. Your own Community-Matrix-Server without federation is perfect, with federation it could leak some data, depending on what you are doing (but yes, you should be aware of). For the profile data there are options to limit the „leakage“ a bit: https://github.com/matrix-org/synapse/blob/develop/docs/sample_config.yaml

NAT is not at all recommended by matrix, https://github.com/matrix-org/synapse/blob/develop/docs/turn-howto.md

I found this: https://github.com/matrix-org/synapse/issues/6395

Once you have the home server set up and configured (not covered here because it's a process), clone the bridge repo (for instance mautrix-signal and follow the instructions.

Is there a way to change the domain name of my existing Matrix Synapse chat Server? Renewal for my domain name is expensive. I'd rather just buy a cheap domain name every year and replace with my new domain name. The only info I could find was this from several years ago: https://github.com/matrix-org/synapse/issues/3031

ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; location / { # If not within location, it would always be executed (return does not work like in programming languages) return 444; } # https://github.com/matrix-org/synapse/blob/master/INSTALL.md#client-well-known-uri location /.well-known/matrix/client { default_type application/json; add_header Access-Control-Allow-Origin *; # To work in browser based clients, the file must be served with the appropriate Cross-Origin Resource Sharing (CORS) headers return 200 '{"m.homeserver": {"base_url": "https://matrix.example.com:8448"}}'; } # https://github.com/matrix-org/synapse/blob/develop/docs/delegate.md location /.well-known/matrix/server { default_type application/json; return 200 '{"m.server": "matrix.example.com:8448"}'; } }

3: you can host your own server and still write with people from other servers. and well...kinda hard to collect data if there's no third-party server to collect said data. can't get more private than that, at least not without going completely p2p. if that's too much work you can still use their default server or any other community hosted server.

I think it's the same logic as empty rooms. There is an opened issue about that : https://github.com/matrix-org/synapse/issues/4720

I found this: https://github.com/matrix-org/synapse/blob/master/docs/workers.md

Does the confirmation email come from rocket.chat or nootropicsrebirth? I can't find one from either, but I'd rather only have to search for one.

At one point I seriously considered self-hosting a Rocket Chat [1] instance for very similar reasons. It seems to have a good balance of features, moderation controls, and polish while still being pretty straight-forward to host.

The main challenge I ran into was, of course, convincing folks to use it (instead of the "easier" forms of communication that they already had....).

1. https://rocket.chat/

Overall i'd just reccomend signal as it's the perfect balance, or rocket.chat if you prefer that

revolt.chat, rocket.chat, matrix, signal, ...

Signal? or maybe Matrix? or rocket.chat? there are plenty of alternatives

We call this first script nightly via CRON. It mirrors the repos, keeps only the newest versions, and deletes all of the older files. About two hours later Ansible crawls our inventory, does an update check, and tosses us a message on our internal rocket.chat server if we have any updates. It's handy. Anyhow, here is an excerpt the repo-mirrorerer: (You would do this for each repo that you need.)

Middle ground could be something like a community version self hosted solution like rocket chat. Integration into wordpress would be the same as the 3rd party options (Js snippet) but you host and manage the rocket chat instance.

Rocket.Chat

Another viable alternative not mentioned is Rocket Chat instead of Slack.