Done, I guess. Turns out editing the code would only be needed if running #Dendrite naked towards the Internet. When behind a reverse proxy the changes needed can be made there.
The rest was just to spin up the additional Docker image for sliding-sync. I now have #Element X running towards my Dendrite server.
#Element on my iPhone has suddenly gotten the "notifications arrive but sync needs the app to be open and takes _forever_" syndrome. Reading up on it this seems to be some sort of known issue, and rather than figuring out how come it can happen overnight the solution is apparently to upgrade to #ElementX
Alright. That however needs the server to support "sliding sync". Fine - I run my own server, so let's ...
Sure. I use #Dendrite, not #Synapse, so it doesn't support Sliding Sync yet. It seems to consists of running an extra Docker container and then ...
... add a single line to a JSON response created by Dendrite.
This is why we open source. If my understanding is correct my server will support this today then.
(I'm getting the feeling Dendrite is a lost cause. Synapse or #Conduit would be my recommendation for someone doing a new #Matrix server install today)
#element #elementx #dendrite #synapse #conduit #matrix
@stefano @fnwbr I share Florian's opinion.
For my network of friends and family, I use #Conduit. It is a solid #Matrix server with low resource requirements. However, the development could be a bit faster.
Being the official #Matrix server of the future, I would have an eye on #Dendrite .
What would you recommend for a new Matrix server these days?
Please, comment and boost!
#Matrix #MatrixServer #Synapse #Dendrite #Conduit #MastodonAdvice #OpenSource #Decentralization
#matrix #matrixserver #synapse #dendrite #conduit #mastodonadvice #opensource #decentralization
Unser Matrix-Space hat das Update auf Dendrite 13.2 erfolgreich absolviert. Wenn ihr jetzt die empfohlenen Spaces sehen könntet, wäre das super, dann wäre ein fieser Bug weg:
Wer will mal gucken kommen, ob das so aussieht, wie im Screenshot?
https://matrix.to/#/#bonndigital:bonn.chat #Matrix #Dendrite #Bonnchat
I'm curious to hear about other people's experience with hosting #Matrix.
I'm now trying #Synapse, #Dendrite, and #Conduit to see which one is most suitable for setting up a reasonably large community.
What I'm looking for in particular is a friendly onboarding experience, and the ability to invite only a specific list of people to join (feed a CSV via API or command line script, say). Ideally, people would use a personalised sign-up link.
Anyone any experience with this? Tips? Warnings?
#matrix #synapse #dendrite #conduit
#dendrite doesn't seem to have an option to prevent (unauthenticated) public room listing? Or do I just not see it?
Following the #dendrite documentation on https://matrix-org.github.io/dendrite/administration/createusers, the create-account command fails with "Shared secret registration is not enabled".
Well, how do I create an account without it?
حرفی که میزنی زیاد دقیق نیست. احتمالا منظورت سیناپس بوده که آره با تنظیمات پیشفرض واقعا نابهینه هست و اگر از اسکیولایت استفاده کنی بدتر هم میشه. با یکسری توئیکها یکمقدار بهتر میشه و بنظرم بشه روی دو گیگ اجراش کرد. ولی تهش باز هم زیاد خوب نیست. مگر اینکه بری سراغ دندرایت یا کاندویت که با گو و راست نوشته شدن.
#matrix #ماتریکس #synapse #سیناپس #sqlite #اسکیولایت #dendrite #conduit
#matrix #ماتریکس #synapse #سیناپس #sqlite #اسکیولایت #dendrite #conduit
Tips on selfhosted dendrite (matrix server)
- Make sure DNS TLD setup is on point (use first a dummy test domain is best to be fair)
- Matrix Signing key backup (and be sure DNS is correct otherwise fun fun fun)
- DNS Server for dendrite (srsly - join a remote server room with 5k ppl and you have 150k+ dns request in 2 minutes)
sooo.... is dendrite running ?
yes....
did i crippled my local DNS servers (3 total) ?
yes - DDoS myself into oblivion. :ablobfoxbongo:
PSA: After having scratched my head since I first moved the whole family over to #Matrix more than a year ago, the solution to the non-existent notifications on Android has been identified in the issue below. It happens when using manual user account creation on the #Dendrite server, and apparently even though it's known it has not been fixed for existing setups.
tl;dr: (In #Element) Enter any 1:1 chat, go into settings for that room, notifications, switch to "none" and back to all.
This will populate the previously empty notification rules that can be viewed from Advanced Settings in your account. And that's the #Dendrite bug, they weren't automatically set up at (manual, by admin) user account creation.
Imagine how frustrating this has been for this iOS using admin with almost everybody else in the extended family on Android ...
Conclusion is a big yes.
Using static files under a primary domain .well-known/matrix/{server,client} hosted in, route traffic via Tailscale Funnel on ports 8443 and 443 (one federation port).
Through a Tailscale Docker container configured as a proxy, traffic can be forward TCP/TLS via socat.
From socat, traefik handles routing to Dendrite.
Was concerned with bandwidth, stability and latency, but things are looking good so far.
#tailscale #traefik #docker #funnel #matrix #dendrite
@Blase Love the idea of #Dendrite / #Conduit. My #Matrix instance is for my family, including some fairly low-tech family members, so reliability is the number 1 concern. If it breaks I may never get them back from #Facebook Messenger / #Skype etc.
I'm assuming that Synapse would be the most reliable as it seems to be the most developed...
That said, #Element video calls with my mother rarely seem to work, unless I use #ElementWeb instead of #ElementAndroid.
#matrix #elementandroid #ElementWeb #element #skype #facebook #conduit #dendrite
I really want to love #Matrix and #Element, but here we go again. Suddenly messages from a family member arrive as "Unable to decrypt message" and none of my four always running clients have the keys to decrypt them.
Since I moved the family off Google WhatEverChatIsCalledToday to self-hosted Matrix this has happened way too regularly to not be an actual issue somewhere.
#Dendrite server on Linux, #Element clients on Windows/Android/iOS/Linux/macOS
It's a bit difficult to get back to discussions more than a few days ago, which is unfortunate. I remember having one about #Matrix and #Element and whether it's only a UI issue or something else that causes (my) family members to suddenly need a reset due to expired keys.
Well - my main Element (Linux) client up on the window next to this is currently showing an "Open another device to load encrypted messages" dialog.
It's done so for two days now, and all other clients have been active during that time. They're all verified, they're all in the device list, and "Resend key requests" makes no difference.
I love Matrix, and Element is the client of choice, but there is an issue here that really messes it up for non-techies (and those of us who need to support them).
(While it shouldn't matter, #Dendrite is running the server)
While the documentation was clearly for an earlier version, #dendrite is up and running and I'm able to join various federated rooms! It's still a bit slow though, not sure if that's something I can address...
@timsmalley They are great photos. #4 looks like it could be a #neuron #dendrite anatomy pic
Aww yeah I fixed the #Dendrite installation.
#Federation is now working.
It seems like Dendrite has issues joining large rooms like #matrix:matrix.org.