2 ms·
Which essentially means you node is now a web server with all the responsibilities that entails (keep backups, always connected, etc). It feels fragile - I can
by DougN7 9y ago
Which essentially means you node is now a web server with all the responsibilities that entails (keep backups, always connected, etc). It feels fragile - I can't imagine pinning everything I ever read (or think might possibly be important some day).
What about all the .EXEs (games, etc) and SDKs I download? I'll bet over the past 10 years I've downloaded and viewed a few hundred GBs (or more) of content.
If I ever want to see anything again, I have to pin (cache it locally). I could do _that_ (cache locally) with today's web.
I like the idea. But just don't see it working well at scale.
- y4mi 9y agoyou need to review the technology if you think ipfs is more fragile and needs data nodes to always be up. you need one data node up. You can have as many as you want. if nobody wants to keep the old exes, they'll be lost forever. ipfs was never meant to keep everything forever. Its meant to guarantee you that the file you're viewing (if it still exists) is the same one that was published under this hash. With no regard as to the source of the file. It could be shared with you by your neighbor or the original uploader. And, if you see value in the content, you can also share it with others by pinning it. its essentially bittorrent as a filesystem. as long as nodes exists, the files will be available.