peerflix VS ipfs

When I used a Chromecast, I was fond of an even more direct method. I used a Node CLI called "peerflix" [0] to stream a video file while downloading its torrent (so there wasn't even a need to wait). Then I just opened my browser to the local network address where peerflix was hosting the h264 playlist, and used the Cast button to stream it to my device (which I believe technically means Chromecast "takes over" downloading the playlist, rather than my laptop pushing the video to it, so I just needed to use a URL with the LAN IP of my computer).

At some point I also used a tool to stream to the Chromecast directly from the CLI (castnow?) - or maybe Peerflix even had this option, I can't remember. Nowadays I prefer to watch content on my phone in bed, which is why I like Jellyfin, because the iOS client can easily stream a video I downloaded onto my computer.

[0] https://github.com/mafintosh/peerflix

It actually use peerflix as torrent streamer, github

peerflix - Streaming torrent client.

It’s this repo: https://github.com/mafintosh/peerflix

This is something I've repeated like 10 times on this subreddit, but you don't need to wait for a torrent to finish to start watching it. Literally every torrent client in the past decade supports downloading first piece files first, so you don't have to wait for the download to finish and can start watching it immediately. There's even stuff like peerflix which makes it easier.

maybe try peerflix? just put the url it gives into vlc on the chromecast

I don't mind pinning, but back in the day I was having issues using IPFS to transfer small files between devices. I admit I haven't investigated to see if the problems were ever resolved.

I've been watching https://github.com/ipfs/helia which is going to replace https://github.com/ipfs/js-ipfs and hoping they can get an IPFS node working in the browser.

I haven't tried https://js.ipfs.tech/ (js-ipfs) in a while, what is the state of it?

On the topic of IPFS, but also slightly tangential -- how has nobody written an Activity Pub client/server in Javascript and distributed it as a Browser Addon?

If IPFS can be literally hosted via a Firefox Extension[1], how has nobody done the same for an arguably easier protocol like Activity Pub?

1: https://github.com/ipfs/js-ipfs

If you can load them up in js-ipfs that might be better?

Store the content in ipfs and just put the hash in the URL? I haven't used https://github.com/ipfs/js-ipfs in this capacity but I'm under the impression that that's what it's supposed to do.

js.ipfs.tech

You need an import statement instead of require since Node has upgraded to the new module system. Use import * as IPFS from 'ipfs-core'. Read more here: https://github.com/ipfs/js-ipfs

Please take a look at https://github.com/ipfs/js-ipfs/blob/master/docs/core-api/FILES.md for more understanding

You could include js-ipfs[0] and fetch all your resources from IPFS without going through a gateway. However, this approach would make the site fully dependent on JavaScript.

A PWA with a Service Worker could perhaps implement its own client-side "gateway", translating public gateway URLs into direct IPFS access. Without the Service Worker (or without JS) it would fall back to using the gateway.

[0] https://js.ipfs.io/

Of course,You can try it out. You can create some Hash to IPFS from this link Adding data to IPFS https://js.ipfs.io/ and then browse the hash in https://ipfs-gateway.cloud/ It is directly connected to IPFS Node.