30 second caveats:

- You still have to host yourself, since you don't get free hosting.

- Not encrypted, so you gotta add the encryption in yourself.

Decentralized doesn't mean you need to host it yourself.

Decentralized simply gives you the additional option to host it yourself. It also does not preclude free hosting.

Example: email.

Not true. IPFS is encrypted and with pluggable PKI too!

https://youtu.be/HUVmypx9HGI?t=3210

And you do not have to host yourself once your content is distributed. That is what makes it permanent!

Here's an IPFS issue about Keybase integration: https://github.com/ipfs/notes/issues/48

You don't have to, but unless someone decides to "pin" it it might just disappear at any time. So you better pin it yourself or find someone reliable to pin it for you.

> or find someone reliable to pin it for you.

The Internet Archive will eventually be the "pin" of last resort.

And/or someone will make a business out of pinning files.

For public files, I hope that there will be several organizations organizing multiple long-term pins of files.

That's the best part! Anyone could be paid to pin!

Home users with enough bandwidth and storage. Existing CDNs. New cloud storage entrants (Backblaze).

Literally anyone with an internet connection and storage would be able to securely serve your content.

EDIT: I just saw your profile :) Thanks for the work you do at the IA!

For encrypted personal files?

No, this was IPFs being discussed (content addressable web).

Yes, but we were talking in the context of the grandparent post "IPFS is encrypted and with pluggable PKI too!", not of publicly accessible files.

I'm all for IPFS, but I think you're missing the forest for the trees. Crypto is hard, especially PKI. KeybaseFS is crypto first, global FS second, while IPFS just says "do crypto yourself" - which, as we've seen with email and texting and literally everything else, doesn't work.

I would love for KeybaseFS to work via IPFS instead of their own servers. But pointing at IPFS as a /replacement/ for this crypto+FS project is disingenious.

I think parent only wanted to give examples of what direction we should be looking in.