rtctunnel
ns-remote
| rtctunnel | ns-remote | |
|---|---|---|
| 2 | 1 | |
| 428 | 116 | |
| 0.9% | - | |
| 8.5 | 0.0 | |
| 8 days ago | over 3 years ago | |
| Go | JavaScript | |
| MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rtctunnel
-
Show HN: Web-P2P-tunnel, WebRTC+ServiceWorker HTTP tunnel to localhost
Hey HN, web-p2p-tunnel is a hobby project I built over the past month.
It enables you to expose a local web server to devices on different networks. Nothing to install on the consuming devices - just a web browser. And no server in the middle. It uses a Service Worker to intercept HTTP requests and WebRTC to tunnel requests/responses directly between consuming devices and the device running the local web server.
To use: install the web-p2p-tunnel CLI program which receives requests, reverse proxies them, and tunnels responses. See the README for details. The website is deployed using Github Pages at https://tunnel.andrewt.io/. Additionally, a signaling server is deployed at https://signal.andrewt.io/.
I've tested on a number of OSs and browsers and with simple static web sites and more complicated apps. A lot of it just works, but there are kinks and edge cases and almost certainly bugs. Let me know :) Currently, there are no TURN servers configured, so connections may fail under certain network conditions.
Motivation: I built some media features using WebRTC at my last job. It's a bit of a pain to use, but it's a powerful technology. On the media side of things, however, P2P quickly turns into more of a client-server situation w/ something like an SFU for common use cases. From my understanding, WebTransport might become the better technology for this use case. This got me thinking about use cases that would specifically benefit from the P2P aspect of WebRTC, which led me here. I was inspired in part by this project: https://github.com/rtctunnel/rtctunnel.
Excited to share the project - I think it could be a useful dev tool. Feedback appreciated!
-
WebRTC ➕ Build Yet another Chatting app💭 but P2P/E2EE🤯.!!
LiveShare type application from VScode
ns-remote
-
WebRTC ➕ Build Yet another Chatting app💭 but P2P/E2EE🤯.!!
Stream your Nintendo switch into Oculus
What are some alternatives?
webrtc - A pure Rust implementation of WebRTC
werift-webrtc - WebRTC Implementation for TypeScript (Node.js), includes ICE/DTLS/SCTP/RTP/SRTP/WEBM/MP4
Neko - A self hosted virtual browser (rabb.it clone) that runs in docker.
netbird - Connect your devices into a single secure private WireGuard®-based mesh network with SSO/MFA and simple access controls.
amazon-kinesis-video-streams-webrtc-sdk-c - Amazon Kinesis Video Streams Webrtc SDK is for developers to install and customize realtime communication between devices and enable secure streaming of video, audio to Kinesis Video Streams.
webtty - Share a terminal session over WebRTC
aiortc - WebRTC and ORTC implementation for Python using asyncio
neko - A self hosted virtual browser that runs in docker and uses WebRTC.