# wg show wg0 transfer | awk '{r += $2; s += $3} END {print "In: " r/1024^3 " GB, Out: " s/1024^3 " GB"}'
In: 31.3264 GB, Out: 276.019 GB

# wg show wg0 transfer | awk '{r += $2; s += $3} END {print "In: " r/1024^3 " GB, Out: " s/1024^3 " GB"}'
In: 53.2848 GB, Out: 1279.89 GB

@waweic They don't want to provide an inconsistent user experience using their network. If you want to connect to Signal's servers, you need to use their client. Going back to XMPP, UX consistency is critical. Outdated, buggy, or feature incomplete clients impact that UX.

Otherwise, the client and server code is open source, so you could host your own, and open up access for all the 3rd party clients you want.

@waweic XMPP has some serious shortcomings that make it less attractive to Signal.

I think the largest shortcoming with XMPP are the XEP standards.

Sure, XMPP is a fully federated and decentralized protocol, but one client or server not implementing a specific XEP affects all users connecting to that client or server.

XEP inconsistencies mean uncertainty, which translates into a shaky foundation to build privacy and security.