Closed rogerlzp closed 5 years ago
The whole stack probably is too much to run on a mobile device. It requires an IPFS server, an RTMP transcoding server and a player.
However it would be possible to use the stack from a mobile device.
Watching the live stream on mobile is should not be a problem in the current state. The player works on most of the devices we tested. I think there were one or two weird exceptions.
As for uploading a video (or publishing from the phone). The current model uses openvpn as an auth mechanism. (which does exist for android). Then you just find an app to publish an RTMP stream from the camera. So it should be possible.
There is another authentication mechanism available for the RTMP server we use, it would take a bit of work to activate it. But it is possible.
This is very promising
IPFS on android is OK, I have completed it on my app. But what to do next, and where can we use it is the current issue. Maybe this is one that can have a try.
What is your app?
I'm working right now on a blog-platform which every channel can issue their own subscription in a erc-20 format token. This will allow users to earn money on content they create instead of being exploited by brutal corporations like Facebook. And also make subscription 'giftable'
So I think to use IPFS as IPFS can't be blocked, and I thought that I need a streaming functionality because I want to start with gamers audience. - This is why I was looked into solution on live streaming on IPFS, and as we know now, that it can be playable on mobile device too, I can fit this issue to my project very well
So my point is this solution is fit into usecases like gaming audience stream platform, or studio blog format streams, decentralized tv as well. It doesn't fit into other stream-blog usecases like "instagram stories" or other, where users actually want to make translation exactly from their own phone (not pc)
interesting, we are doing quite near.
My app is like the following: There are two roles in the app, one is the provider, and the other is the consumer. The provider process is like the following:
The consumer process is like the following:
This is the whole process of what we are doing.
So my point is this solution is fit into usecases like gaming audience stream platform, or studio blog format streams, decentralized tv as well. It doesn't fit into other stream-blog usecases like "instagram stories" or other, where users actually want to make translation exactly from their own phone (not pc)
my skype is rogerlzp. Maybe we can talk on that.
As @darkdrgn2k pointed out, the video.js player we use work on most mobile browsers, and the backend is a RTMP endpoint, allowing devices (mobile or otherwise) to stream into it. Though the current code does not deal well with changing streams, which could be a problem for mobile type of unreliable connections.
I believe this discussion about another app is out of scope for a ticket in this repo. I am closing this issue as the original questions seems to be addressed.
Most of the time, people use their phone to watch the video or upload a video. Is this possible to use in Mobile, Android or IOS?