Breaking the 100bps barrier with Matrix, meshsim and coap-proxy (2019)

This work has progressed a lot since 2019, although the blog post here describes the original spurt of work on it. Nowadays Matrix has MSC3079 to formally spec low bandwidth transports: <a href="https:&#x2F;&#x2F;matrix.org&#x2F;blog&#x2F;2021&#x2F;06&#x2F;10&#x2F;low-bandwidth-matrix-an-implementation-guide" rel="nofollow">https:&#x2F;&#x2F;matrix.org&#x2F;blog&#x2F;2021&#x2F;06&#x2F;10&#x2F;low-bandwidth-matrix-an-i...</a> and we’ll be building it into clients &amp; servers by default in future.<p>The final major unsolved problem is that the sync API doesn’t support pagination yet, so on a big account you can end up burning bandwidth (and cpu) syncing data for rooms or room members that the client doesn’t care about. This is the final piece of the puzzle, and the lowbandwidth team is working on it right now - and will probably be the most exciting and fundamental improvement in Matrix in years :)

This is so awesome. I&#x27;m thrilled to see work progressing at the other end of the bandwidth spectrum.

This is awesome. Hope this will be adopted eventually for their P2P project - would do wonders over slow mesh networks, additionally to stuff like Tor.

I&#x27;m sorry if I miss it, but no protocol in this millennium should be without mitigation for denial of service. DJB&#x27;s curveprotect uses fixed sized packages (refusing small ones) to kill amplification attacks. I wonder if they considered such issues.

There is also <a href="https:&#x2F;&#x2F;comatrix.eu" rel="nofollow">https:&#x2F;&#x2F;comatrix.eu</a> which I think implements this.