This is interesting for me for several things.
Is this using webrtc or something similar?
Is there stun / turn servers?
Is the ip address of the streamer findable by the receiver?
I've never seen a firefox permissions popup saying 'website X wants to see your screen, okay or choose a window" - something like that - interesting to know that is baked in there somewhere.
Hey thanks for your interest. It is not using webrtc it is using GUN decentralized database see https://gun.eco/ and some custom implementation to able to stream
To elaborate a bit about the tech. De site is plain html and plain javascript. No node server just a heroku instance that host the GUN instance.
The website itself is very simple and uses MediaSource Extension https://www.w3.org/TR/media-source/ to make the streaming go smooth. This is often used by players that use dynamic bitrates for different network etc.. Such as HLS, Shaka player.
This is all brought together in this project. Webrtc is only used for getting the screen and microphone. There is no signaling stun server etc needed for this to work.
I have to come back to you about finding the IP address. I am not sure about this. Will ask the GUN community. Maybe you can explain why this case is interesting and for which cases?
- Someone has to stream on the same username as you are viewing
- Indeed no devices is not throwing an error. Handling happy cases only at the moment.
To bad the viewer side did not work. Probably because after an hour I stopped streaming and there was actually not to show for anymore. Feel free to let me know if you want to give it another try and we set a day and time.
I've never seen a firefox permissions popup saying 'website X wants to see your screen, okay or choose a window" - something like that - interesting to know that is baked in there somewhere.