overpass
p2p-webtransport
overpass | p2p-webtransport | |
---|---|---|
7 | 1 | |
344 | 154 | |
- | 0.6% | |
0.0 | 7.0 | |
over 1 year ago | 6 months ago | |
Python | HTML | |
MIT License | GNU General Public License v3.0 or later |
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.
overpass
-
Video Live Streaming: Notes on RTMP, HLS, and WebRTC
Have you tried LL-DASH? It's somewhat more available for usage in tools like ffmpeg. I'm looking to experiment more with it on my own streaming platform.
https://github.com/GOATS2K/overpass
- A self-hosted streaming platform with Discord authentication, auto-recording and more
- Show HN: Overpass – a self-hosted video live streaming app
- Overpass – a self-hosted video live-streaming app
p2p-webtransport
-
Video Live Streaming: Notes on RTMP, HLS, and WebRTC
> I just wish WebRTC wasn't so prescriptive of DTLS/SRTP.
There was a webrtc-webtransport spec, but it got renamed to p2p-webtransport[1]. I'm not sure when the rename happened. Feels like a pretty strong indicator of webrtc being deconstructed, but whose to say this goes anywhere. We'd also need webcodecs.
It's somewhat scary & also somewhat exciting thinking of the one good, working, browser supported standard being ripped into pieces (p2p-webtransport, webcodecs, more) & being user-implemented. Having the browser & servers have a well-known target is both great but also perhaps confining. If we leave it up to each site/library to DIY their solution, figure out how to balance the p2p feeds, it'll be a long long time before the Rest of the World (other than the very big few) have reasonable tech again. WebRTC is quite capable & a nice even playing field, with lots of well-known rules to enable creative interopation. We'd be throwing away a lot. I'd hoped for webrtc-webtransport, to at least keep some order & regularity, but that seems out, at the moment. But Webrtc-nv is still ultra-formative; anything could happen.
The rest of the transport stack is also undergoing massive seismic shifts. I feel like we're in for a lot of years of running QUIC or HTTP3 over WebRTC Data-Channels and over WebTransport, so we can explore solutions the new capabilities while not having to ram each & every change through with the browser implementers. It feels like a less visible but far more massive Web Extensibility Manifesto moment, only at sub-HTML levels[2]. The browsers refused to let us play with HTTP Push, never let appdevs know realtime resources had been pushed at the browser, so we're still debating terrible WebSocket vs SSE choices; terrible. I think of gRPC-web & what an abomination that is, how sad & pointless that effort is; all because the browser is a mere glimmer of the underlying transport. I feel like a lot of experimentation & exploration is going to happen if we start exploring QUIC or HTTP3 over WebTransport. Attempts to reimagine alternatives to WebRTC are also possible if we had specs like p2p-webtransport, or just did QUIC over DataChannels. Running modern protocols in the client, not the browser, seems like a semi-cursed future, but necessary, at least for a while, while we don't yet know what we could do. The browsers are super laggy, slow to expose capabilities.
[1] https://github.com/w3c/p2p-webtransport
[2] https://github.com/extensibleweb/manifesto
What are some alternatives?
mirotalksfu - 🏆 WebRTC - SFU - Simple, Secure, Scalable Real-Time Video Conferences Up to 4k, compatible with all browsers and platforms.
ffplayout - Rust and ffmpeg based playout
FitTrackee - Self-hosted outdoor activity tracker :bicyclist:
webrtc-nuts-and-bolts - A holistic way of understanding how WebRTC and its protocols run in practice, with code and detailed documentation.
discord.py - An API wrapper for Discord written in Python.
rtp-over-quic-draft