Sean-Der

6 ms·

1.
by Sean-Der 15d ago
DTLS 1.3 has quite a few cool features/upgrades. Wrote some down so you can see the cool stuff coming your way. Also a few notes on stuff that was surprising or frustrating while building it. If you get a chance to try it out would lov
2.
DTLS 1.3 in Go: An Implementer's Perspective(pion.ly)
2 points by Sean-Der 16d ago|1 comments
3.
by Sean-Der 16d ago
We would love your help on Pion WebRTC! What motivates you, certain topics or building things in a certain area? what are you most interested in?
4.
by Sean-Der 17d ago
Here is another thing I find frustrating, but I don't know the right way to express it. A lot of this AI tooling/coding seems self-indulgent? 'I built a better software factory!'. The tools are very powerful, but I don&#
5.
by Sean-Der 17d ago
I personally used to enjoy the challenge of it. I enjoyed the craftmanship. I am so glad I got to enjoy the challenge of implementing IETF specs and the debugging interop etc... it's so sad to me now that people just bruteforce all thi
6.
by Sean-Der 20d ago
This is fantastic! I have wanted something like this for years. When people are learning WebRTC they are really confused by the Offer/Answer. You have this big blob of text and no idea what it actually does. You look up values one-by-o
7.
We built a realtime system for responsive voice AI in six months(openai.com)
2 points by Sean-Der 1mo ago|0 comments
8.
by Sean-Der 2mo ago
Fantastic work on this. This idea has so much promise, I hope this is the project that makes it take off. Self-hosting is pretty these days with docker. Exposing it to the internet is the annoying part. I do Jellyfin via netbird, but that m
9.
by Sean-Der 2mo ago
Write up about the architecture is here https://openai.com/index/delivering-low-latency-voice-ai-at-...
10.
by Sean-Der 3mo ago
What's not easy about it? Would love to hear about the gaps in software/education that could make it easier to use.
11.
by Sean-Der 3mo ago
Thanks Woodrow :) Accepting 'Big Changes' from people is VERY frustrating. These thoughts run through my head. * Idea is usually good! Even if I don't understand it could help lots of others users. * The contributor is very f
12.
by Sean-Der 3mo ago
NLNet is a wonderful organization. They have supported two Pion projects! I am grateful the code got written, but even better people got careers out of it/learned new stuff. If you are on the fence about taking on a project I encourage
13.
by Sean-Der 3mo ago
Does WebRTC not work inside/outside of the browser anywhere?
14.
by Sean-Der 3mo ago
This should be fixed! I added this in Pion here[0] and I remember testing against Chrome + FireFox and it seemed to work great! [0] https://github.com/pion/webrtc/commit/e4ff415b2bff31382bdb80...
15.
by Sean-Der 3mo ago
Amazing debugging, I loved reading that. HN doesn't get enough good posts like this anymore :) If https://github.com/pion/sctp/issues/12 had happened (not just in Pion but across all implementations) thi
16.
Server-Side WebRTC Noise Reduction with Pion, FFmpeg, and RNN Models(lodan.me)
2 points by Sean-Der 4mo ago|0 comments
17.
Vibe-Coding WebRTC(webrtchacks.com)
3 points by Sean-Der 4mo ago|0 comments
18.
by Sean-Der 4mo ago
I work on WHIP in OBS and an open source project Broadcast Box[0]. I made this site/video to talk about the reasons why https://webrtcforthestreamer.com I hope this site can convince more people to check this stuff out. If
19.
[video] WebRTC for the Streamer – How Whip/WebRTC Can Improve Streaming(youtube.com)
3 points by Sean-Der 4mo ago|1 comments
20.
by Sean-Der 4mo ago
I work on WHIP in OBS and an open source project Broadcast Box. I see a future where streaming is better. I hope this site can convince more people to check this stuff out. If you are curious or have feedback I would love to hear
21.
Show HN: webrtcforthestreamer.com – How WHIP makes streaming more connected(webrtcforthestreamer.com)
5 points by Sean-Der 4mo ago|1 comments
22.
by Sean-Der 4mo ago
I have been working on making streaming cheaper/more private/lower latency (via WebRTC) in OBS. Been working on this site to get people excited https://webrtcforthestreamer.com/ after it is done want to record a Y
23.
by Sean-Der 4mo ago
I can add it! What format would like to see?
24.
by Sean-Der 4mo ago
The spirit is alive with https://github.com/m1k1o/neko The 'co-watching/co-streaming' is the best. I love watching a crappy horror movie with friends and bantering.
25.
by Sean-Der 4mo ago
You run one encoder for all the viewers. CPU usage won't scale up from 1 -> 15 viewers. I could get it lower by encoding once and then syncing to keyframes. It would make the code more complicated though. If someone asks for it&#x2F
26.
by Sean-Der 4mo ago
The 'Seek' is done server side. So if you go to `n` seconds it is done server side and done for everyone. I should reword the README though. If someone is savy enough they could totally grab the video. For most users it is like a
27.
by Sean-Der 4mo ago
That is 100% controllable! By setting Playout Delay Header[0] you can pick between 'drop everything to stay live' or buffering up to ~40 seconds! In this project I don't set anything though. [0] https://webrtc.goog
28.
by Sean-Der 4mo ago
1.) Latency vs quality doesn't come up enough to make people want to A/B test it unfortunately. At work I would say ~5 people care about WebRTC vs QUIC vs X. All effort is around the models (how can I provide tools to be support t
29.
by Sean-Der 4mo ago
That is not the case. See get-realtime-translate[0 that's doing it as a trickle instead (not turn based). [0] https://developers.openai.com/api/docs/models/gpt-realtime-t...
30.
by Sean-Der 4mo ago
Responding to some technical points first, but then after that I do see a future that isn't WebRTC. I don't think it matches where WebTransport+WebCodecs etc is going though. > …but as a user, I would much rather wait an extra

More ›