stratself

We are (like everyone) on matrix.org now but realize we need to move eventually.

Consider moving to another open registration server too. Find one that supports Element Call

do I need to pay for a domain still?

If you're gonna selfhost, you should purchase a domain for proper federation with the wider network. IP-only servers are possible, but they are generally banned in most rooms due to antispam. Same with dynamic DNS domains

Unless it really is easy enough to do it on a synology nas for text/voice/screen share...

You'll need to integrate a Matrix homeserver (I recommend Continuwuity.org, much lighter than Synapse) and Livekit (the software that handle Element Calls). It's not particularly easy so maybe consider managed hosting beforehand, too

I'm using Continuwuity.org (also a Rust-based server and forked from the same former project as Tuwunel) so I'll name a few that this one lacks:

• Synapse Admin UI (helps a lot in large server setups)
• Ability to purge rooms and some history (Rust servers use rocksdb with high compaction, so not a high priority for them)
• Matrix Authentication Service (aka next-gen OIDC-based authn)
• Ability to become a notary server (maintain other servers' signing keys for faster retrieval by the public)
• More niceties implemented for Element Call
• More niceties implemented for encryption

I don't think anything except for maybe OIDC would be really needed for a small-scale homeserver, but they do lack them. For me the resource efficiency, storage savings, and ease of maintenance is definitely a larger factor in choosing the server implementation

You can try Snikket.org, which is basically Prosody but easier. But you can't selfhost "on each person's own computers" as you said because you'd still need a publicly exposable IP addresses and high uptime. Maybe you could try registering on an XMPP or Matrix instance you like and migrate your community over there first

Question for others: is Prosody's (and XMPP's) group calls really good? I'm under the impression that Matrix (with Element Call) is currently better due to the SFU architecture, but I'd be happy to be proven otherwise. I'm interested to hear required specs, how large the calls can be, and how much strain it puts on the TURN server and clients especially when it comes to multiparty streaming

AFAIK the Movim people are working on SFU calls too, but not soon

• E2EE: all servers support it
• Federation: this is where most of the resource hog is. If you disable it you can use anything. I enable it and use continuwuity.
• Voice calls/screen shares: requires extra integration with Element Call + Livekit
• Mobile notifs: requires integrating with ntfy or some other UnifiedPush service. Or download Element X from Play Store and use Google's push services

Edit: the main differences between these servers are that Synapse is written in Python/Twisted and is known to take up huge storage space. Meanwhile all other mentioned projects are Rust based, has a shared lineage, are usually more efficient with storage and ops, though are more focused on a smaller user size and doesn't yet have advanced Synapse features

If you want a non-federating LAN-only Matrix server, then STUN/TURN can be behind the NAT. Since you have Tailscale, STUN/TURN can also expose itself on the Tailscale VPN too. Just configure proper DNS records per-interface and you should be fine.

Since calls are p2p, the purpose of STUN is to determine a client's (usually public) IP address, and TURN is to relay the connection if they can't connect directly (i.e. behind NAT). If your clients are on the same LAN/VPN with unrestrictive firewalls then you might not even need any STUN/TURN altogether.

Few of the answers given were concrete. So here's my take.

I am able to run singleuser Continuwuity on a 8GB RAM Pi machine with 4 cores, and join many large rooms (around >=1000 users, although the number of homeservers in the room is a more suitable metric). It would use around 2GB RAM, but you can tune it for less (basically reduce cache values, but ask in the room for more advice).

After a few months the database hovers at around 2GB, because the database uses zstd compression by default. It's not anyhow a major problem like Synapse, just don't use HDD for storage and you should be fine.

For best experience, I also selfhost a dedicated caching resolver (unbound) for continuwuity. That takes like a few hundred more MBs of memory.

Given the fact you'd like to play around with it, a mid-tier VM/VPS (2CPU, 2GB RAM, 20GB SSD) is a reasonable starting choice. For a non-federating server, it can take a lot less resource than this.

jade-liveit-guide.continuwuity.pages.dev/calls

the call docs are being rewritten to reflect latest developments. Join the Matrix room for further help too, it's quite active these days

If you're still interested in selfhosting a Rust-based homeserver, https://continuwuity.org/ will get you there. However if you're just migrating your community to this federated protocol, making a room on an open registration server could be enough

Question: what sort of misconfiguration was it? Might have an effect on the round robin assignments of Cloudflare

Edit: just FYI, if behind a VPN, you may prefer using the DNS servers of that VPN provider to blend in with others. But I guess your VPN is your VPS so it's a bit different here

Why are files unusable outside of Nextcloud? Consider using the External Storage plugin.

Imo there are two types of file servers: smart clouds with offline and smart selective on-demand sync on brand-specific clients, groupware support, conflict resolution, and enterprisy plugins (Nextcloud, Opencloud, Seafile, etc); and dumb clouds with protocol-based file transfers and filesystem-tree/userperms instant compliance (copyparty, sftpgo, etc)

Of the first one, only Opencloud has a native-looking filesystem (PosixFS) and does it without dependency on a db. It supports smart sync for Windows (via the same API OneDrive uses). Linux smart sync is sadly nonexistent due to lack of protocols, and whatever other software do (e.g. using an .owncloud placeholder file) is highly experimental.

Of the second type, you'd get all the standardizations and speed but no bidirectional sync nor offlineness - again this is honestly an advanced undertaking requiring academic understanding of distributed systems and whatnot. On Linux you may try emulating some aspects of it via a half-smart client like rclone with VFS, but the UX to store files offline is still not there.

Knowing these constraints I'd tier my storage into 2 parts: the daily files like notes and recent photos stored in one of the smart sync solution, ready for download and later offline use; and anything unnecessary (Jellyfin media, archives, ) to be in a dumb SMB share/SFTP mount.

HI, kinda late to the party. I'm in a similar rut with intercontinental internet issues, and would like to share my thoughts

While not a full-fledged CDN, you may consider setting up an Asian VPS to serve as a second reverse proxy/ingress route, terminate TLS there, and route plaintext HTTP back to your homelab (this virtual tunnel shall be behind a WireGuard VPN interface). As I've figured out in my blogpost here (see scenario 2), this allows the initial TCP and TLS handshakes to happen nearer to the user instead of going all the way to Europe and back home.

You can consider setting up a separate Jellyfin instance for Asia, but of course that comes with setting up syncing media, maintaining separate user credentials, and so on. So before renting compute, I suggest trying these smaller actions first - if they work you mightn't need a VPS anymore:

• Look into Linux sysctls tuning of network parameters. My personal tweaks for the /etc/sysctl.conf stuff are:
  • Increasing all the memory usage for network stuff (net.core.(rmem_max/wmem_max/rmem_default/wmem_default), net.ipv4.tcp_(mem,rmem,wmem)`. Relevant blogpost and another. YMMV
  • Enable BBR (net.ipv4.tcp_congestion_control=bbr), a modern congestion control algo suitable for long distance/high latency.
• Implement some sort of Smart Queue Management on your router (e.g. CAKE algorithm) to avoid the bufferbloat problem
• Enable HTTP/3+QUIC on your reverse proxy for reduced handshakes. Though it's unlikely native Jellyfin clients also benefit from such features

Curious to see if any of this helps :)

Try writing a maubot plugin or build from the ones available