I just came across this “dat protocol”, which seems to be yet another iteration of things like #ipfs and all the rest.
And one wonders: what problem exactly does that solve that hasn't been solved before?
@61 Well they are very different: If the webdav or FTP server goes down, you're fucked. Meanwhile with IPFS you can fetch data so long as at least one peer has it, and you can even fetch it if multiple peers only have parts of the data each.
I understand that, but just how many hosts exactly are likely to have a copy of your family holiday pictures or whatever it is that you care about but hardly anybody else does? And for anything that people do care about, we already have redundancy as a neatly separated layer.
So to repeat the question, I am interested to know what *new* development does the DAT protocol (or IPFS for that matter) bring to the table and what problem do they solve that is not already solved in practice.
I am genuinely interested, but whereas I could immediately see how #torrent was uniquely useful when it came out, for example. I cannot get any enlightenment as regards these new projects.