I'm sorry about this — it's difficult to strike a balance between preventing abuse and respecting user privacy. If anyone here is facing attacks, we're available to hop in a call any time.
Thanks for pointing that out. I've shut down the stream for now. For those that want a demo, we're still hanging around in https://gg.hyperbeam.com/invite/w0c6n-Ko
To add to mwcampbell's response, my cofounder Amby proposed a possible solution:
> 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.
> Have you considered the accessibility ramifications of this, e.g. for blind people using screen readers?
We are considering the accessibility ramifications now since we've pivoted toward a general API. We didn't focus on accessibility for blind people initially because we were building a watch party platform.
I think offering accessibility features would give us a massive edge against technologies like screenshare! Is there a specific use-case you're thinking of?
It's up to 6. For most programs, 4 is the minimum.