webwormhole VS simplexmq

I'm sure it could be misused, but by itself it's fine - https://github.com/saljam/webwormhole

AV1 support is already available in libwebrtc!

So when I started building Pion the target use case was to make it easier to build scalable servers. Instead of interacting with a WebRTC servers REST API to query information/load balance I wanted to have it all in one code base. It also is really useful to have Media+Transport decoupled. Lots of use cases I didn't realize grew out of that.

* Teleoperation/robotics (https://github.com/Ragnar-H/TelloGo)

* Control remote software (https://github.com/m1k1o/neko)

* Cross platform file sharing (https://github.com/saljam/webwormhole)

* Sending pre-recorded media (RTMP/HLS/RTSP -> WebRTC)

* Custom DataChannel servers/bridges (https://snowflake.torproject.org/)

Lots of other cool ones in https://github.com/pion/awesome-pion I need to update it. It has been a bit since I have looked through https://pkg.go.dev/github.com/pion/webrtc/v3?tab=importedby

Fair question, this server or the code is not owned by me and is available on GitHub. Though after reading up on it, if the server was ever to be compromised it would be possible to inject malicious code in between, this, however, could be mitigated if you were to use the command-line utility mentioned on the Github page. Or you could use Chrome and Firefox extensions, as there is no remote code loaded and no extra permissions needed.

You can use https://github.com/saljam/webwormhole if you want P2P file transfer.

It only has a CLI tool right now for desktops. It works in the browser though, so that is great for users looking for a GUI!

Of course https://github.com/simplex-chat/simplexmq

It's about ntf-server-ubuntu-20_04-x86-64 https://github.com/simplex-chat/simplexmq/releases/tag/v5.1.3

Also, it is covered in whitepaper here: https://github.com/simplex-chat/simplexmq/blob/stable/protocol/overview-tjr.md

Please review the whitepaper and / or website home page. I also wrote this post some time ago about why I believe that using pairwise identifiers should be a minimal requirement for a communication system to be considered private.

For more information see Simplex development roadmap xftp branch in github

The source code: https://github.com/simplex-chat/simplexmq/tree/xftp

You can download XFTP CLI (Linux) to send and receive files via the command line here - you need the file named xftp-ubuntu-20_04-x86-64, rename it to xftp.

We absolutely should assume they can be compromised, but as SimpleX servers do not participate in the initial key exchange for e2e encryption, the server compromise will not lead to the compromise of e2e encryption security. I wrote more on MITM issue in this post. Further, the threat model here explains other consequences of compromised SimpleX servers.