5 ms·

Nice! Now please: 1) Kill the electron crap. Just look how awesome, fast, funcional, beautiful and feature-rich telegram is 2) Kill synapse. Is close to impos

Nice! Now please: 1) Kill the electron crap. Just look how awesome, fast, funcional, beautiful and feature-rich telegram is 2) Kill synapse. Is close to impossible to run a home server with all that python shit going on. Dendrite is the way I guess, but it is super resource-consuming to have a small home server (and slow) 3) Make it accessible and interesting for the casual john doe: FluffyChat is one possible route

hestefisk 5y ago
Why is Synapse “impossible to run”? I agree it’s not the most performance but for a small home server it’s quite fast to set up. Dendrite is definitely going to be faster but it also has a lot more complexity (multiple databases, Kafka etc). Synapse is quite simple to understand and reason about.
justshowpost 5y ago
That would be the sensible business decisions. Feed new horses, don't feed old horses. But they are hackers and have no idea of management. I'm really curious, if they manage to burn through 30 million and still keeping Element being crappy. At least thanks to Matrix being an open protocol anyone can develop a better alternative.
vfclists 5y ago
> Synapse is a reference "homeserver" implementation of Matrix from the core development team at matrix.org, written in Python/Twisted. It is intended to showcase the concept of Matrix and let folks see the spec in the context of a codebase and let you run your own homeserver and generally help bootstrap the ecosystem. Is a reference "homeserver" implementation supposed to go into production on a large scale?
cvwright 5y ago
If running an Ansible playbook [1] is "close to impossible" for you, then there are a few different companies who will host a server for you. Including the guys mentioned in the main article here. Sure, Synapse's performance isn't great, but still. Last summer I was able to run Synapse on a 1 vCPU, 1 GB RAM droplet from Digital Ocean. I had 100 copies of a bot running, each with their own room, constantly sending messages and replies to each other. With all 100 going at once, it was super slow. But with fewer bots, or with a lower chance of replying to a message, it worked pretty well. Not bad for like $10 / month. Also, if you want light and fast, check out Conduit, the homeserver written in Rust: https://conduit.rs/ https://conduit.rs/ [1] https://github.com/spantaleev/matrix-docker-ansible-deploy https://github.com/spantaleev/matrix-docker-ansible-deploy
- Macha 5y ago
  Conduit's homepage says: > Note: This project is work-in-progress. Do _not_ rely on it yet. Last I checked it also didn't support federation.
karmanyaahm 5y ago
2) Synapse works fine for me with 300MB memory to it and 400MB to the db, which can all be run (along with several other lighter applications) on the lowest tier Linode. 3) Yes
__david__ 5y ago
Re #2, it's a Debian package now which makes it super easy to get running on Debian systems (and probably Ubuntu). I suspect there are also docker images which can also make it very easy to get it up and running without dealing with python deps (I feel you as a non-python-dev, it's really hard to get python apps to run).
arendtio 5y ago
Running a communication server at home is inherently a bad idea. I have done so for a some years and switched to a Hetzner VM just with this service some time ago and it feels much better. One of the problems with a server at home is connectivity, because every second your service is not reachable, you are not serving your users well. In general, I would say that I have a very stable connection, but once a year or so I have to disconnect the internet connection for some reason and it doesn't feel right to steal your friends and family the possibility to exchange messages. Furthermore, I had some trouble with the dynamic DNS from time to time, which always caused the communication service to fail. In addition, my backup strategy wasn't very sophisticated and at some point I had to search 200GB of data (broken filesystem) in order to restore the contact roster of all people on the server (the last backup was a few weeks old)... So if you really want to, do it, but if you ask me, my clear advice is to run communication services at some professional hosting partner.

hestefisk 5y ago

Why is Synapse “impossible to run”? I agree it’s not the most performance but for a small home server it’s quite fast to set up. Dendrite is definitely going to be faster but it also has a lot more complexity (multiple databases, Kafka etc). Synapse is quite simple to understand and reason about.

justshowpost 5y ago

That would be the sensible business decisions. Feed new horses, don't feed old horses. But they are hackers and have no idea of management. I'm really curious, if they manage to burn through 30 million and still keeping Element being crappy. At least thanks to Matrix being an open protocol anyone can develop a better alternative.

vfclists 5y ago

> Synapse is a reference "homeserver" implementation of Matrix from the core development team at matrix.org, written in Python/Twisted. It is intended to showcase the concept of Matrix and let folks see the spec in the context of a codebase and let you run your own homeserver and generally help bootstrap the ecosystem. Is a reference "homeserver" implementation supposed to go into production on a large scale?

cvwright 5y ago

If running an Ansible playbook [1] is "close to impossible" for you, then there are a few different companies who will host a server for you. Including the guys mentioned in the main article here. Sure, Synapse's performance isn't great, but still. Last summer I was able to run Synapse on a 1 vCPU, 1 GB RAM droplet from Digital Ocean. I had 100 copies of a bot running, each with their own room, constantly sending messages and replies to each other. With all 100 going at once, it was super slow. But with fewer bots, or with a lower chance of replying to a message, it worked pretty well. Not bad for like $10 / month. Also, if you want light and fast, check out Conduit, the homeserver written in Rust: https://conduit.rs/ https://conduit.rs/ [1] https://github.com/spantaleev/matrix-docker-ansible-deploy https://github.com/spantaleev/matrix-docker-ansible-deploy

Macha 5y ago
Conduit's homepage says: > Note: This project is work-in-progress. Do _not_ rely on it yet. Last I checked it also didn't support federation.

karmanyaahm 5y ago

2) Synapse works fine for me with 300MB memory to it and 400MB to the db, which can all be run (along with several other lighter applications) on the lowest tier Linode. 3) Yes

__david__ 5y ago

Re #2, it's a Debian package now which makes it super easy to get running on Debian systems (and probably Ubuntu). I suspect there are also docker images which can also make it very easy to get it up and running without dealing with python deps (I feel you as a non-python-dev, it's really hard to get python apps to run).

arendtio 5y ago

Running a communication server at home is inherently a bad idea. I have done so for a some years and switched to a Hetzner VM just with this service some time ago and it feels much better. One of the problems with a server at home is connectivity, because every second your service is not reachable, you are not serving your users well. In general, I would say that I have a very stable connection, but once a year or so I have to disconnect the internet connection for some reason and it doesn't feel right to steal your friends and family the possibility to exchange messages. Furthermore, I had some trouble with the dynamic DNS from time to time, which always caused the communication service to fail. In addition, my backup strategy wasn't very sophisticated and at some point I had to search 200GB of data (broken filesystem) in order to restore the contact roster of all people on the server (the last backup was a few weeks old)... So if you really want to, do it, but if you ask me, my clear advice is to run communication services at some professional hosting partner.