Sean-Der

I work on WHIP support in https://obsproject.com I find it disappointing to see people still struggling with the things that I hoped it would solve. I also maintain a https://github.com/glimesh/broadcast-box as a demo server to run it against.

Increasing user control/interoperability is best for users. I tried to show off even more use cases in https://webrtcforthestreamer.com/

I see P2P working 80%+ of the time for my deployments. Other people have posted data about this also https://medium.com/the-making-of-appear-in/the-most-likely-t...

P2P is better then TURN/Iroh Relay. Even if traffic is encrypted the size of what you are passing through is valuable metadata. Or the time at what you send things. P2P is always better for users.

I chose the name because of the particle.

I sent a letter to the Soviet Union asking if they were ok with me using the name, never heard back!

I am waiting for my trillion dollar offer to buy https://pion.ly !

Then I am all done fixing WebRTC bugs for life :')

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 love to hear your thoughts! Should be available soon in pion/dtls@v4 :)

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?

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't see the results yet. The frustration outweighs results.

I am underwater dealing with it. I am getting outlandish PRs against Pion. So I spend my time triaging and feel burned out. The 'AI future' I was expecting would be people swooping in and clearing up the backlog in high quality ways.

Instead I get people trying to add new APIs when it can already be done with existing APIs and then arguing about it with me.

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 this with agents.

I wonder how carpenters felt when powertools started taking off?

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-one and forget as you go. its annoying

Excited that the next generation learning WebRTC (for VoiceAI) has better tools.

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 means I don't really share it with my friends. I hope something like this getting baked into self-hosting flows is killer.

My other pet peeve is that people use 'Cloud Services' for File transfer. Sometimes when they are in the same LAN!

Nice work again and I hope it catches on/people understand how great this really is :)

Write up about the architecture is here https://openai.com/index/delivering-low-latency-voice-ai-at-...

What's not easy about it? Would love to hear about the gaps in software/education that could make it easier to use.

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 focused on just getting their feature in. The impact on the larger project isn't as much a concern.

* New contributors often don't have the grit to see it out. They will disappear before things are done. So I am left picking up the pieces (which is harder then doing it all myself)

----

What I try and remember is that their happiness/experience matters more then any code. I try to help the contributor learn/grow as much as possible and even see some career benefits out of it. Pion will cease to matter eventually, so I hope to help as many programmers with it as possible.

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 you to do it!

Does WebRTC not work inside/outside of the browser anywhere?

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...

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) this could have been fixed years ago. The hardcoding we all settle for is tragic.

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 you are curious or have feedback I would love to hear.

[0] https://github.com/glimesh/broadcast-box

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

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 YouTube video for it.

After that I want to spend the weekend just closing out Pion bugs/relaxing :)

I can add it! What format would like to see?