i am reminded of something nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk was saying recently on the notedeck call about using webrtc for sharing files and blobs between users p2p.

making media and filesharing censorship resistant is something I want to invest heavily into notedeck and damus android. blossom is cool, but so is p2p tech like bittorrent v2 and webrtc filesharing.

Reply to this note

Please Login to reply.

Discussion

Would it be a hybrid model of relays and peers?

i am a creative not an engineer but i was looking into ipfs for this for video—a way to share & distribute files of films and issue as a collection. your thoughts or are you chatting abt diff issue?

unfortunately ipfs is retarded and doesn’t have the right incentive structure. we would likely need some structure to find peers that would most likely have content you’re interested in.

how to do this effectively is a hard problem and will take lots of thought and care

well, that explains why it was a dead-end for me. otherwise, for now, server plus jellyfin i guess.

As others mentioned, IPFS is great in theory and quite a pain in practice. Here in NOSTR there is Blossom which tends to work far better and just about anywhere.

Making media uncensorable is huge for long term comms. Blossom plus p2p like WebRTC or bittorrent v2 feels like the right stack - tools like PRobot would happily build on that.

This reminds me of this piece of nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk

https://mmalmi.github.io/how-to-fix-everything-thats-wrong-with-the-internet

missed this one. will read!

i built a poc that uses nostr as the signaling layer for webrtc. it works well for signaling but webrtc is a huge pita once you get outside of the lan.

it’s probably broken but here’s the design doc: https://peerfile.link/about