4 ms·
I built this mainly because I was feeling the pain while implementing a website for a customer that is allowing their users to upload and stream files in the br
by timdaub 8y ago
I built this mainly because I was feeling the pain while implementing a website for a customer that is allowing their users to upload and stream files in the browser.
As the file upload should accept any kind of input, but the streaming only allows for certain files to be played back in the browser I researched different codecs that are available on the web for streaming and came across: https://github.com/ipfs/js-ipfs/tree/master/examples/browser-video-streaming https://github.com/ipfs/js-ipfs/tree/master/examples/browser...
I though, why not make this a SaaS.
- fiatjaf 8y agoSo your customer is using IPFS on his site? How do you manage that? Do you run the IPFS node for him and put the uploaded videos on your node? Is your SaaS fetching from IPFS, then reuploading because your customer's visitors upload using js-ipfs, then you fetch from your node, totally unrelated to the website's backend? Just wondering.
- timdaub 8y agoMy customer is using ipfs-api-js on their website and it uploads to an ipfs node (in our case Infura). In the future we might run a node if the customer requires it. For now Infura is very convenient. My Saas is fetching from IPFS, then reuploading so that the upload and conversion of the file both could potentially be triggered on the client side. Many Dapp architectures I've seen so far have no backend component.