31–40 of 48 posts
Earlier quoted context omitted.
I just came back from a run and the website was down. Sorry. It's up again. Utility: https://github.com/ipfs/js-ipfs/tree/master/examples/browser...
Anyone know how js-ipfs is able to load files without it showing up on the chrome dev tools' network tab?
I don't understand in which situation I should be using that.
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...
I though, why not make this a SaaS.
Hi this is Tim. I made this website. It's currently running on a $5 droplet on DigitalOcean so conversions will take a while. I'm testing out the waters here on HN to see if there's anyone interested in it. Please let me know if you have any questions regarding it. Github: https://github.com/TimDaub/ipfs-hls-converter Edit: I haven't chosen I license for this yet, sorry.
I don't understand in which situation I should be using that.
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-ip…
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.
Earlier quoted context omitted.
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-ip…
So 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.
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.
Hi this is Tim. I made this website. It's currently running on a $5 droplet on DigitalOcean so conversions will take a while. I'm testing out the waters here on HN to see if there's anyone interested in it. Please let me know if you have any questions regarding it. Github: https://github.com/TimDaub/ipfs-hls-converter Edit: I haven't chosen I license for this yet, sorry.
Did you look into using something like ffmpeg.js to do the heavy lifting client-side? Note I have no idea if ffmpeg.js supports all the features you need (ie HLS).
Does this require resources on your server? (Apologies because I don't understand what this is.) What's to stop me from uploading 10TB of video files and using all your resources?
Currently nothing is stopping you from uploading a 10TB video except that maybe my DigitalOcean droplet would run out of space and crash.
Earlier quoted context omitted.
So 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.
My 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.