These questions relate to our community post here https://discuss.ipfs.io/t/gt-systems-building-blust-spa-the-world-s-first-legal-approved-peer-to-peer-movie-sharing-network-exploring-ipfs-libp2p-and-filecoin-as-a-tool-set/2049
Our requests, questions and what we first need to understand at a high level before diving deeper. It may be better to split these off into separate threads, but wanted to get some wholistic, high level views first.
- We would love to hear from anyone with experience implementing IPFS and libp2p for large date sets and transfers, particularly real time data and particularly video.
- Our initial platform is PC/Windows. Believe it or not, that’s for security (PlayReady 3 in hardware and SGX) as well as the massive installed base of PC’s. Are there any plans for a Universal Windows Platform (UWP) app environment version of IPFS?
- Can we “merge” IPFS with our Secure Peer Assist (SPA) architecture? One specific and high priority requirement is that our architecture uses a combination of P2P and CDN to “fill gaps”. This allows us to implement a “most needed packet” rather than “rarest packet” algorithm. This is very useful for real time or near real time playback of video and for seeding. It also combines the strengths of centralised and decentralised storage and provides a role for all in future. We are partnered with EdgeCast (Verizon).
- Our video files are packaged with Dynamic Adaptive Streaming over HTTP (DASH) using Common Encryption (CENC). Hopefully that isn’t a problem?
- It seems that IPFS encrypts the source files at rest. Is this correct? That is good, but we use encryption that is approved by the studios. Specifically, we need to support PlayReady 3 (PR3) SL3000 encrypted video segments, packaged in DASH CENC and fMP4 containers. We need to understand how IPFS encryption affects and works with PR3.
- Very interested to discuss “routing” options. We have some ideas there.
- Can we implement a secure sub-community within the larger IPFS community (we’d prefer not to do this but see next question).
- How can we ensure no “undesirable” content is stored on our users’ IPFS “beside” Hollywood content? E.g. pirate movie BitTorrent files or porn. This is a “perception” issue, given this happens already on shared environments, but it is a very real and high priority concern of Hollywood, especially some of the security people in the more conservative studios. We’ve seen a bit of discussion around this but haven’t found a clear and definitive answer yet.
- We very much like the open transport model. If we provide reliable transport, optimised for large file transfer, presumably that can use UDP?
- A little off topic, but highly related (and we can’t find a forum): we love Filecoin. It solves our problem of ‘incenting’ disk sharing and file sharing and creates a currency for our platform. Love their work. Does anyone know if we can create our own, branded version? Even just in name only? The underlying purpose of Blust+SPA is the same, but it would be good to have a currency that reflects our application.
- We haven’t been able to find any official Filecoin forums. We would love to participate if anyone can point us to one. Particularly around the economic/business models being contemplated.
- Given positive answers to the above (which seems likely), how do we work together to build the world’s first legal, approved, peer to peer movie (and other) file sharing system?
8 February 2018