matrix.org VS ssh-punchhole

That's a very interesting thread, because this is one of the major issues we have with Matrix. It's not directly a product but a (technical) protocol that can't be presented as such to the general public.

We definitely aim for Matrix-based products to be used by the general public, in the same way emails are. For this to happen, we need to be mindful of who our audiences are, what they are looking for, what they know and don't know, and how to deliver a message that works for them.

If you're interested in how we thought the website, you can check https://github.com/matrix-org/matrix.org/issues/1502 and https://github.com/matrix-org/matrix.org/issues/1543 for example

no idea what's going on here; the post hasn't been changed since it was published: https://github.com/matrix-org/matrix.org/commits/main/conten...

Scalar (the integration manager) is not open source [1] (though there was some effort to reverse-engineer its protocol [2]); and some of their anti-abuse scripts aren't public [3]

[1] https://github.com/vector-im/element-meta/issues/260

[2] https://github.com/turt2live/matrix-dimension/blob/master/do...

[3] https://github.com/matrix-org/matrix.org/issues/557

Saw this post and made me a bit concerned that im heading down a bad route. I understand that CF can harvest metadata but as the chats are encrypted it will be all good?

At home, just a bunch of AlmaLinux VMs with K3s, using MetalLB for LoadBalancerIPs in my LAN and ssh-punchhole to forward ports from an externally hosted VPS to my local ingress-nginx and other things, so my stuff is externally available.

Get yourself a cheap VPS and then try something like https://github.com/TamCore/ssh-punchhole (which i hacked together, because everything else just looked too bloated for my taste). That way you can host everything at home and don't have to forward any ports, as the tunnel is established from within your network :)

I've published my setup for that case as a container image: https://github.com/TamCore/ssh-punchhole.

I've published my setup on Github: https://github.com/TamCore/ssh-punchhole Even if you don't use Docker, you could still basically use the script as standalone. I just wanted to have everything neatly packaged :)

I use a VPS as my public endpoint, but the tunnel is established from my network, as it's based on reverse SSH port forwarding. So no port forwarding in my router required and would even work with CGNAT and whatsoever. Sample configs I've published under https://github.com/TamCore/ssh-punchhole

If you don't want to mess around with port forwarding, I'd recommend just getting a cheap VPS somewhere close to you, and hosting Traefik and something like my ssh-punchhole (see https://github.com/TamCore/ssh-punchhole) for tunneling inbound traffic to your service.

Using haproxy (lightweight and quickly configured) was an easy fix for that issue. I've included the relevant parts from my configs in https://github.com/TamCore/ssh-punchhole/blob/main/README.md :)