OK, this is interesting. I think peer-to-peer file storage is probably a good optional feature, with HTTPS as a fallback. I don't know if IPFS is the right storage solution, but it's probably worth exploring. I'm somewhat agree.
@evan i think a case can be made that torrents have the best track record and are super stable in terms of where the development is. its very straightforward how to seed data , and you can do all of this on your servers so its completely invisible to the user.
downside of torrents is they are immutable . eg cannot change ,, you could chunk your torrent creations possibly or you could use one of
@evan the downside of holepunch is it is in heavyyy active development and almost no one can keep up with its changes .. so maybe when it settes it will be usable.. that said i have used its predecessors dat / hypercore and they worked incredibly well.
also cabal runs on hypercore and is the most rock solid p2p chat application that no one knows about.
@evan holepunch , i really really think that this is the current best in class p2p tech but it also has drawbacks !
i think its holepunching is still better than libp2ps
also it was setup initially to be used with mutable data in mind moreso than ipfs which i prefer. ipfs really wants an immutable filesystem and i just dont jive with that. ( ipns exists but its kind of a cludge imo)
@evan ive run into this problem quite a bit as my server has very very low amounts of storage because i cannot afford more.
ive looked at primarily ipfs and hypercore/holepunch ..
biggest issue initially with ipfs is holepunching for edge devices.. this has gotten a lot better .. besides that i think it has a bit of complexity in areas i do not prefer but it obviously is working at scale *filecoin*