webwormhole VS infinite-app-cache

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!

> the other uses client-server cryptography pretending to be end-to-end

This is misleading and false. Wormhole.app uses end-to-end encryption. It's factually incorrect to imply otherwise.

To address the larger point – auditing a web app is indeed challenging with current web technologies. In the past, I experimented with a technique using App Cache to permanently cache a web app on first use [1]. Later, that technique was expanded into hyperboot [2] to give users the benefits of explicit, immutable versioning with control over upgrades using the html-version-spec while preserving the simplicity of passing around a URL.

With the impending removal of AppCache from most browsers, the web is currently missing a way to "pin" a site to a specific version and only update it with user consent. Service Workers come close but they mandate a 24 hour maximum cache time before refetching from the server.

We'd love to offer the usability benefits of web apps – you can give someone a URL and they can immediately load the app – with the security of installed apps – doesn't change without warning – once web standards catch up. This is something that I care deeply about.

In the meantime, use magic-wormhole if you prefer a locally-installed command line tool and you're sending files to someone who understands the command line. Use Wormhole.app if you want usable end-to-end encryption, similar to what Firefox Send used to provide.

[1]: https://github.com/feross/infinite-app-cache

[2]: https://github.com/substack/hyperboot