Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Add support for Content-Addressable Asset Storage (IPFS, etc.) #2322
The current implementation of Known stores most media assets in a local filesystem and creates UUIDs to reference them. As an alternate I would like to propose supporting Content-Addressable storage. That is, storage based on the Hash of the content. This is used by IPFS and other systems. It can be applied to both user uploaded content and especially for embed content that is fetched and rendered.
With this in place it will be possible to use a public IPFS gateway instead of a CDN (Content Delivery Network) Read more on how CloudFlare supports this in their blog post.
Ideal scenario is that core has the right hooks and then an IPFS plugin (or DAT, or Swarm, or other future system) can use these for to do their job.