ambyjkl

Thanks, we vehemently oppose bloat in our JS files ;)

Thanks :)

If you're on linux, you most likely need the H.264 ffmpeg codec package and things like the Cisco OpenH264 plugin for Firefox. Also, try unblocking WebRTC if you block it

Yea sorry it's our bad, we didn't implement cursor time-slicing in the demo, even though we actually support it on the API: https://www.npmjs.com/package/@hyperbeam/web#setting-permiss...

The problem with VP8 is it's almost never hardware accelerated, neither on the encoding nor on the decoding side, so it's undesirable. Also, the software encoder x264 is quite far ahead of libvpx vp8 in terms of the encoding cost vs bitrate vs quality tradeoffs in our testing. We really hope AV1 solves all these issues once and for all in the years to come.

Thanks for the feedback. We already have this feature, it's just not implemented in this demo currently, but we'll be sure to add it. More info here: https://www.npmjs.com/package/@hyperbeam/web#setting-permiss...

You most likely need this plugin: https://support.mozilla.org/en-US/kb/open-h264-plugin-firefo...

Seems like in Firefox, H.264 in WebRTC is supported in an entirely different fashion than other kinds of H.264, like in an MP4 file.

Also which OS? I have a hunch your version of Firefox doesn't have the H.264 codec which we need

Thanks! I'm intrigued by what you built (long-time Linux user here), can you share a link?

webrtcbin is nice for one-to-one, but we were looking for something that's a better fit for one-to-many, which is where mediasoup came in. That being said, mediasoup is quite complex from a maintainability perspective since it's designed to handle several use cases, so we plan on making our own webrtc streaming solution in the future that's designed with only one-to-many in mind

Thanks, I'll go look at what's happening

Hi HN! I'm the CTO of Hyperbeam, happy to answer all the technical questions :)

Thanks! Actually it's neither: we run full Chromium rather than CEF and Mediasoup for webrtc. We have looked into webrtcbin as well, but it wasn't the best fit for us.

Which version of iOS are you on?

We'll be sure to fix the demo video on Firefox :)

Thanks! That name took a lot of thinking for sure :D

Good luck for YC, and don't give up if you get rejected, it took us three tries to get in haha.

We don't use VNC, we send an H.264 stream over WebRTC. Also, checked out your demo, and it seems you use VNC?

Currently, we do not have accessibility support for the browser, we only do the video stream. The reason we haven't worked on this yet is because of our focus on watch parties, and the video stream being streamed was usually that of a video itself, so not a lot of accessibility could be added to that use case. But now that we are looking at the bigger picture, we could implement full-fledged accessibility support where we serialize the accessibility tree and send that over instead of the video stream.

This is quite interesting, a very elegant struct hack. Dlang is working on an RFC for implementing this feature right into the language, which would probably make it the first systems language to implement this without structs.

https://github.com/dlang/DIPs/blob/master/DIPs/DIP1030.md