I like IPFS, I really do, but whenever I try to use it, it's either too slow to become usable or sometimes it plain doesn't work. I pinned a whole bunch of files on IPFS a while back to experiment with it and the system seems to work, but every time I try to fetch those resources from a location that hasn't cached the content yet, it takes several seconds to show me the HTML/JSON/PNG files. HTTP may be inefficient fo…
HTTP is obsolete – it's time for the distributed, permanent web (2015)
31–40 of 337 posts
Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)
#32The author claims that IPFS enables a "permanent web" and eliminates 404-like experiences. How does IPFS guarantee that all published content will be available forever? (In my beginner-level knowledge of IPFS, this is the first I've heard that claim. It seems absurd.)
Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)
#33Well, we’re all dependent on the Internet which can be shut down at any time by any government, and normally almost completely dependent on FAANG companies.
I applaud the freedom activist spirit but the only exciting technologies in this regard must be P2P and not Internet carried.
Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)
#34Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)
#35Is there a way to install something on my local machine and host IPFS content to help "the swarm". If they combine this with some kind of crypto monetary incentive it would go a long way for people to help "the swarm". Odysee is looking into adding crypto to your balance when you serve content that helps viewers.
Maybe FileCoin is what you're looking for? https://filecoin.io
Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)
#36I like IPFS, I really do, but whenever I try to use it, it's either too slow to become usable or sometimes it plain doesn't work. I pinned a whole bunch of files on IPFS a while back to experiment with it and the system seems to work, but every time I try to fetch those resources from a location that hasn't cached the content yet, it takes several seconds to show me the HTML/JSON/PNG files. HTTP may be inefficient fo…
I agree that the http caching layers are currently needed to achieve decent UX. But it’s also possible that won’t be necessary forever. The network could expand and get to the point where resolution time comes down to accessible levels. Only time will tell I suppose.
Will the network be faster the more people join it?
Is centralized infra inevitable for fast things because of all assumptions and insight a centralized provider can use? BTC is also slow, I don't know of any cryptocurrency that can provide VISA transaction volumes, even if they use more power than some countries alone.
Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)
#37Like this IPFS, you'd connect to a hub (IPFS calls this a node) and get what people were sharing. This IPFS only takes that step a little further with hashing and distributing. Also, if this gets implemented widely, hash collision is going to be wild
Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)
#38Earlier quoted context omitted.
Maybe FileCoin is what you're looking for? https://filecoin.io
Note that the system requirements are way out of the league of the average home user (32GB RAM, 8 cores, several TB disk space). Plus, if the chain is growing at 38GB/day (as the Filecoin website suggests), that’s a traffic average of 3.8Mbit/s 24 hours a day.
[0] https://github.com/ipfs/distributed-wikipedia-mirror#cohost-...
Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)
#39Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)
#40Earlier quoted context omitted.
Maybe FileCoin is what you're looking for? https://filecoin.io
Is this legitimate or just a shitcoin scheme? The website looks very sketchy.