Open chrishobcroft opened 6 years ago
This is a good idea, but currently the limitation is that the Livepeer node can only receive RTMP video. If it could support WebRTC video, we could stream from the browser. Also, who runs the broadcast node in this situation?
@iSasFTW thanks for the feedback.
In an ideal world, a Peepiscope client would be a mobile app, in order to integrate the cameras and microphones on modern smartphones.
As for the broadcast node, again, I think an ideal world scenario is that there is some kind of "light node" for mobile broadcasting, which can run on the device itself. It can then do the marshalling of content to Transcoder nodes, and eventually, to Content Distribution mechanisms.
So, we are all aware of Twitter... (except maybe my Mother)
And many of us know that Periscope came from Twitter as their mobile-based livestreaming offering.
Now, only some of us will be aware of the recent growth in popularity of the Peepeth's blockchain-powered social network, promoting mindful engagement, both online and in the world.
So I propose Peepiscope... a mobile-based end-user livestreaming application, integrated with Peepeth for brand and user identity, and IPFS for storage, and introduce Livepeer as the livestreaming component in the Web 3.0 stack.
Because let's face it, livestreaming video is where it's heading to... we are all broadcasters now, with cameras and microphones in our internet-connected smartphones...
So, let's start building the next generation of open applications to support a future community.