Oddbean

The limitation is primarily due to the lack of mirrors in IPFS. If I use IPFS Desktop, I can see everything that I share and it all works really well. But trying to share a link with someone else is extremely slow because the network has to hunt and find my server across the entire network. Combining that with Nostr nodes that are specifically designed to help with large file mirrors using the Filecoin and IPFS infrastructure would work, but it would take a serious effort to make the connections between the layers.

yup 100% good analysis - any kind dir. svcs means centralization. havenot dig much in Filecoin - but a combination of IPFS / Filecoin or similar / Nostr relay solution may be so long as coin based very small reward basis is worked out. any total volunteer basis is not scalable eventually if demand quality disk space grows. decentralized solutions dnot need compete with centralized performance basis so long as it works with some delay. imagine when youtube or amazon is down for whatever reason - slow n reachable IPFS or self-hosted ones may still work outside of outage zone

I can imagine an add-on module for IPFS Desktop that allows it to double as a Nostr node, providing hosting for any files being shared and making those files easier for the overall network to find because anyone doing that kind of hosting would just share the Content ID (CID) and the node would take care of the rest automatically. Whether the packet flow would come from IPFS, Torrent or any other method would be up to network flow, whichever is best. If a file becomes popular, the system could see the demand and mirror the file on another node, and when the demand goes down it could clear space for something else but still know where to go for the original file.

The original intention for IPFS and Filecoin is to use FIL as the utility token, but with nostr that wouldn't work and we would want to use sats instead. So maybe the concept can be studied and duplicated on the Nostr network, learning from FIL and IPFS but not limited by it.

The problem with all these self hosted options is you lose all the incredible tools from YouTube and other centralized providers. Playback speed, auto captioning, end cards, analytics on watch time, discovery algorithms, etc Nobody is building a proper YouTube for a decentralized world. There have been slight attempts like Flare, but I have asked multiple times for help setting it up and have gotten nowhere with finding any documentation or peer help Until then I try my best with self-hosting but it only makes sense for short form content or livestreaming

videos (recorded / live) backend CDN is expensive n complex should be kept outside of core wss n txt based nostr codes. use any or combo of options keepit simple - self-host in own hardware - nostrcheck.me or other foss code or service - use paid service - nostr.build, satellite.earth , flare.pub, primal, current n others - use ad-based youtube rumble