In IPFS, your data is stored in 'nodes'. Every file is sharded and stored into multiple nodes connected to the network. 
However, nodes have limited capacity. Nodes will routinely empty themselves to make room for new data to be stored on them. (By default, the threshold is set at 90% but you can manually edit this)
This is concerning, are your files really permanent on IPFS? The answer: Yes, but with one extra step - File Pinning.
You can manually pin your IPFS files, but that's arguably tedious. Additionally, most people lack the technical know-how to do it.
Check how to do it yourself here: docs.ipfs.tech/how-to/pin-fil…
Check how to do it yourself here: docs.ipfs.tech/how-to/pin-fil…
Creating permeance is possible, but if Web3 is to replace Web2: Accessibility is a must, and this doesn't really seem that accessible.
That's where file pinning services come in, such as yours truly: @DolpinIPFS / dolpin.io - we are at large a media management solution for decentralized storage & content solutions - and file pinning is step 01.
Besides @DolpinIPFS - other companies have been working day and night to help solve similar problems, and it would be unfair if we didn't mention them.
Shoutout to @pinatacloud @Filebase @FleekHQ and many more who have been building alongside us!
Shoutout to @pinatacloud @Filebase @FleekHQ and many more who have been building alongside us!
Thank you for listening.
*Dolpin noises*
*Dolpin noises*
• • •
Missing some Tweet in this thread? You can try to
force a refresh
