rtctunnel
neko
rtctunnel | neko | |
---|---|---|
2 | 69 | |
430 | 5,577 | |
1.4% | - | |
8.5 | 7.1 | |
5 days ago | 16 days ago | |
Go | Go | |
MIT License | Apache License 2.0 |
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
neko
- A self hosted virtual browser that runs in Docker
- N.eko – open-source self-hosted virtual browser
- BrowserBox Pro goes open-source
-
I want to have to have a watch party using my media server with someone from another country
I personally use neko-rooms with my friends for this purpose. Just let's all share a browser in a browser with plenty of options (Firefox, Chromium, Brave, etc.). You can also just use standard neko if you don't need multiple rooms.
- Teleparty without subscriptions?
-
Ask HN: Shittiest Hosting Experience?
Hey, you do you. It just sounds like an expensive way to avoid owning the hardware you want to debug to me.
Also, not to burst your bubble, but there are a few projects out there that do more-or-less what you're describing:
- https://store.steampowered.com/remoteplay/#together
- https://github.com/m1k1o/neko
If you're having fun, then continue by all means. I've just been nerd sniped by your cloud costs and I'm having flashbacks to seeing six-figure monthly AWS bills at startups that refused to buy their own GPU compute.
-
Is there any way to let a client test website without giving them the code?
You could spin up something like Kasm Workspaces, Neko or Docker Webtop.
-
Aither: Containerized Multiplayer Linux Desktop Environment
I ran into neko https://github.com/m1k1o/neko recently which has similar. It's more application centric than desktop centric, but both offer multi-player experiences & I just think that is the absolute coolest.
- m1k1o/neko
- Neko – A self hosted virtual browser that runs in Docker and uses WebRTC
What are some alternatives?
webrtc - A pure Rust implementation of WebRTC
docker-ubuntu-vnc-desktop - A Docker image to provide web VNC interface to access Ubuntu LXDE/LxQT desktop environment.
werift-webrtc - WebRTC Implementation for TypeScript (Node.js), includes ICE/DTLS/SCTP/RTP/SRTP/WEBM/MP4
docker-kasm - Kasm Workspaces platform provides enterprise-class orchestration, data loss prevention, and web streaming technology to enable the delivery of containerized workloads to your browser.
netbird - Connect your devices into a single secure private WireGuard®-based mesh network with SSO/MFA and simple access controls.
Code-Server - VS Code in the browser
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.
rdpgw - Remote Desktop Gateway in Go for deploying on Linux/BSD/Kubernetes
webtty - Share a terminal session over WebRTC
taisun - Application for a Docker enabled device with an emphasis on providing a web based interface for managing a single server.
Neko - A self hosted virtual browser (rabb.it clone) that runs in docker.
syncplay - Client/server to synchronize media playback on mpv/VLC/MPC-HC/MPC-BE on many computers