4 ms·
IPFS isn't hosting, it's transport. You can't "put something on ipfs" and expect it to stay there any more than when you "put something on http".
by sneak 5y ago
IPFS isn't hosting, it's transport. You can't "put something on ipfs" and expect it to stay there any more than when you "put something on http".
- codetrotter 5y agohttps://ipfs.io/ https://ipfs.io/ says: > Here's what happens when you add a file to IPFS — whether you're storing that file on your own local node or one operated by a pinning service or IPFS-enabled app. Notice that wording: “Add a file to IPFS”. It’s likewise fine to say, then, that you “put something on ipfs”.
- donkeyd 5y agoThat's odd, since the TP in HTTP stands for transfer protocol, but the FS in IPFS stands for file system. You'd expect to be able to store data on a file system. That's what I use my file system for anyway.
- Workaccount2 5y agoA file system is simply a system for storing files. The filing cabinet is the storage, the way I organize files in the cabinet is the filing system.
- mpeg 5y agoMost IPFS gateways allow you to pin content, plus they will automatically pin popular content to keep it available.
- sneak 5y ago> plus they will automatically pin popular content to keep it available This is false. Popular content is cached temporarily. Pinning persists the data until unpinned; the ipfs daemon does not automatically pin anything.