Hacker News Reader

Comment by Sean-Der | Hacker News Reader

I wrote this to make Reverse Engineering WebRTC services easier. Will also let you save/send arbitrary media from WebRTC sessions. The idea is you do all your auth/interaction in the browser, but then do all WebRTC in Go. So you have lots more control. More to do with it, but it is far enough along to share at least.

In the README is an screenshot of sending my webcam, but replacing outgoing video with a ffmpeg testsrc. Handoff sits between so it can replace with any arbitrary video.

View on HN

Interesting and novel project. I don't have anything constructive to add, but well done.

Thanks :)

No better feeling to work on something and hear it is novel! So many projects that I think will be useful miss the mark.

Connect it to an AI talking head and you have a customer service center - users browsing a store can click to talk with 'someone'.

I've bookmarked your project years ago to attempt implementing webrtc fully in a niche programming language. But I think I may have vastly underrated how difficult this is.

Have you come across https://github.com/elixir-webrtc/ex_webrtc ?

Wasn't sure if they used Pion as a guide

What language? Would love to help :) especially with AI Coding I think it would be a lot more accessible these days.

ex_webrtc is super cool. They have a cool built-in dashboard/analytics flow. It is way more 'operations friendly' then Pion it seems. I haven't used it heavily myself though.

I am kind of a WebRTC noob but... this means after I define my input channel (audio track, video, etc.) and establish a peer connection I can send data from a different source?

Are there any complications with that or is it kind of on me to not confuse the other peer by sending unexpected formats?

Yep exactly! After it starts you can slice in any media you want.

You need to make sure you are sending the same codec that the remote expects, otherwise nothing else! You can do a different resolution, bitrate etc...

Reply on news.ycombinator.com