Show HN: A website that converts any IPFS file to HLS and reups it to IPFS
ipfs-converter.com
ipfs-converter.com
Github: https://github.com/TimDaub/ipfs-hls-converter
Edit: I haven't chosen I license for this yet, sorry.
Right now I'm just spawning sub processes like crazy and hope they don't overwhelm my machine. In the future, I plan to use a queue and also to monetize on API queries.
I haven't looked into queues in Javascript yet. If you have recommendations, that be appreciated :)
This is really just an MVP to see how the internet crowd reacts to it. I'm glad it does in a positive way :)
[1] https://nats.io
When I run the demo, the video plays as expected. However, I wanted to check the network tab to see what it's doing under the hood.
Based on the description, I expected to see a bunch of HTTP GET requests to ipfs.io, fetching the different segments of the movie. However, instead, I see a varying number of websocket connections to ipfs.team, soundclart.com and libp2p.io.
Could someone explain what is going on here? Is this just another IPFS-to-web proxy (based on websockets instead of http) or is this already part of the HLS streaming mechanism?
The main benefit on earth, as far as I understand, is reducing bandwidth required of a single person to share media by distributing hosting, similarly to torrents.
Utility: https://github.com/ipfs/js-ipfs/tree/master/examples/browser...
I like that you can take something that is effectively on your disk, ping some endpoint, and it will get "pulled" by the service as a peer and process it.
Next step could be to make the "ping" step as an IPFS pubsub thing.
We keep a list of some applications and other things over here too: https://awesome.ipfs.io/
I'd argue eternum is not quite at the same level since it just takes an IPFS object as an input (but no IPFS output). Op made a thing that takes an IPFS object as an input and produces a different IPFS object as an output.
There are certainly many IPFS-based apps.
I'd say IPFessay (https://gitlab.com/stavros/IPFessay) is much closer to an IPFS-based API, since it can run entirely on IPFS with no outside servers.
Also, what is HLS?
Yes you're absolutely right. I just changed the description on the website.
> Also, what is HLS?
Someone else answered that already here: https://news.ycombinator.com/item?id=18132277
Already a seed of thought in place for this: https://github.com/ipfs/notes/issues/116
Currently nothing is stopping you from uploading a 10TB video except that maybe my DigitalOcean droplet would run out of space and crash.
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.
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.