It’s so difficult (and expensive) to run a #Matrix#Synapse server for my own domain. Is it worth it?
I started out wanting to support Matrix, and I've set up a number of channels for my community on Matrix, but everything happens on Discord and IRC right now, and we have a bridge between Discord and IRC, but we can't bridge to Matrix at the moment, so is it even worth it to keep maintaining a separate Matrix presence?
If not, I’m just gonna shut it down. I don’t want to spend the money.
@ramsey I set up synapse many years ago and it was a nightmare. And a resource hog. Guess it hasn't improved. Wrote a few bots. Tried also to write a custom proxy and the proxying protocol was so weird. Hell the whole protocol was weird: maccaroons wtf? My understanding is that the server doesn't follow the spec anyway.
I don't consider Matrix a serious project or protocol anymore. If I had to build anything that had to work reliably I'd use either IRC or XMPP.
@ramsey FWIW, ours runs on an AWS/EC2 t3.micro (which is 2vCPU @ baseline 10% + bursts) and serves ~25 people on a given workday. It also does Tailscale, and runs our self-hosted Element if anyone happens to be using that today.
@fijxu Ojo que intente entrar desde mi instancia y me sale que no esta federada, no se si esto es apropósito, pero https://federationtester.matrix.org/#matrix.nadeko.net tira que los nombres del servidor en la config de nginx y el homeserver de synapse no coinciden.
@Kommander Porque nombre del homeserver es nadeko.net y no matrix.nadeko.net. Lo mismo pasa con tchncs.de que tiene el homeserver con ese dominio pero esta alojado bajo matrix.tchncs.de
So good news, the stream from my laptop to peertube was successful with few technical hiccups.
I wish I could say the same for the Synapse install. Out of memory issues and really slow loading times led me to the conclusion that I should probably explore alternatives. I have some ideas but I have to think about it for a while. I'm leaning towards Conduit but we'll see when I can try that.
I might finally do a technical stream this weekend. But instead of coding the goal for me will be to set up #Synapse and hook up to the #Matrix. I tried this before but got stuck on the mail server setup step, but I've been told there are other options so I guess we'll give this another go.
Will I finally divorce myself from #Discord? Probably not, but this is a good first step and if I can get this to work, then I can finally delete my server from that cursed network! 😂
So has anyone had experience setting up a #Matrix server using #Synapse? The platform itself seemed pretty straightforward until it got to the part where I needed to configure a mail server. What solutions do people use?
I want desperately to set my own server and ween myself off of Discord soooo badly. 😅
@zalasur i think you don't need one. You can set a mail address (any mail adress also ones from microsoft and gmail work) in the config file, but you can set up synapse without it
@benjo I'm pretty sure it required one because it needed to send out emails for registrations and that sort of thing. I'm going to try again this weekend but I definitely remember the mail server step was a major stumbling block the last time around.
Cryo-ET of the SC-CA1 hippocampal connection from Eric Gouaux group. Nice confirmation that GluA2 N-terminus is closer to the pre-synapse than to the post-synapse!
Do #Synapse#Matrix servers by now finally come with some proper admin interface, or the #Element (X) client perhaps? Or do you still have to either rely in third-party admin interfaces or curl the API directly?
Just (accidentally) done an interesting experiment while trawling through my Web server logs for another reason. It seems as though there are some /very/ old versions of #matrix#synapse servers running out there querying my well-known URI. If you're still on 1.53.0 (or even older), please upgrade!
(neo)’liberal’ licenses like MIT and BSD that enable corporations to partake of the free labour of others
implying that the #GPL / #AGPL doesn't let corps partake in the free labor of others too> and enclose the commons
Your "open commons" is worthless if it's effectively still proprietary. Case in point: #Mastodon's #ActivityPub extensions that pretty much everybody else have to support (Mastodon is AGPL, and it's not realistic to implement ActivityPub strictly to the spec and expect it to be compatible with Mastodon). Or GNUisms (implemented by #GNU software which are GPL) that #BSD userlands are forced to support. Or #Matrix where there's basically only one server implementation that is usable (#Synapse whichis AGPL). I could go on and on.
@smallcircles@mima that's a bit backwards - Mastodon built on a previous collection of composable specs called OStatus and participated in the ActivityPub standards process. They then removed most of the OStatus parts, except Webfinger which they insist on for unclear reasons.
They also used bits of AP oddly, especially the summary field.
Yes, in terms of the history and specs they used you are correct. Maybe "holes in the spec" was wrongly formulated. They created their 'flavor' of ActivityPub within its flexible bounds, integrated with other specs in ways they deemed best, and added their own bits where needed.
My point is that implementing a spec doesn't give a FOSS project a duty to maintain it. It's prudent to spend time on healthy spec + ecosystem evolution, and can be a win-win. It's not a requirement.
Synapse (Matrix) does a lot of COMMITs and INSERTs fucking my PostgresDB and my NVME TBW.
I am the only one using it + 2 other people so I will just shut down those services.
#Synapse instance maintainers. I kneel, having to manage a Synapse instance takes a lot of money.