[deleted]
[deleted]
HTTP is obsolete – it's time for the distributed, permanent web (2015)
11–20 of 337 posts
Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)
#12> All the static content stored with the site still loads, and my modern browser still renders the page (HTML, unlike HTTP, has excellent lasting power). But any links offsite or to dynamically served content are dead. For every weird example like this, there are countless examples of incredibly useful content that have also long since vanished. Perhaps I missed it, but I don't see where they claim that IPFS can prov…
It won't, but much of the web could work well on JAMStack, and there's no reason that couldn't be supported.
JAMStack isn't much of an option for services that can't trust the clients and cannot rely on high latency consensus algorithms.
It's also brutal for battery life.
Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)
#13I 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…
Wonder if it's practical to "buffer" popular content on IPFS by copying it to normal HTTP servers. Requesting an IPFS document would query a few popular repositories, then revert back to normal IPFS if it's not found. These buffer servers would also track what's popular and shuffle around what they store accordingly.
I think this is exactly what Cloudflare's and ipfs.io's web proxies do. They won't cache your stuff forever, but they'll cache it as long as someone requests the content again before the content gets removed from cache.
The downside of this approach is that it only works with popular nodes and you'd be back to the old, centralised internet architecture for all real use cases.
I don't think you can accurately gauge what is and isn't popular in a P2P network like IPFS. You never have a view of the entire network, after all.
There's also the problem of running such a system. Who pays for the system's upkeep and do we trust them? If we'd use Cloudflare's excellent features, who says Cloudflare won't intentionally uncache a post criticising their centralisation of the internet, forcing the views they disagree with to the slow net while the views they agree with get served blazingly fast.
I don't think such a system would work well if we intend to keep the decentralised nature of IPFS alive. Explicit caching leads to centralization, that's the exact reason caching works.
Instead, the entire network needs a performance boost. I don't know where the performance challenges in IPFS lie, but I'm sure there's ways to improve the system. Getting more people to run and use IPFS would obviously work, but then you'd still only be caching only popular content.
Edit: actually, I don't really want to see caching happen through popularity of the service either, because as it stands IPFS essentially shares your entire browsing history with the world by either requesting documents in plain text or even caching the documents you've just read. I wonder if that IPFS-through-Tor section on their website ever got filled in, because the last few times I've checked that was just a placeholder in their documentation.
Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)
#14Is 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.
Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)
#15(2015)
Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)
#16> All the static content stored with the site still loads, and my modern browser still renders the page (HTML, unlike HTTP, has excellent lasting power). But any links offsite or to dynamically served content are dead. For every weird example like this, there are countless examples of incredibly useful content that have also long since vanished. Perhaps I missed it, but I don't see where they claim that IPFS can prov…
It won't, but much of the web could work well on JAMStack, and there's no reason that couldn't be supported.
JAMStack != static site served entirely by a CDN. There’s an A for API in there. Where’s the A for IPFS? There’s no such thing.
Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)
#17This is very cool! Also should be noted this is from 2015, would love to hear a follow up to this.
Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)
#18I 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…
Wonder if it's practical to "buffer" popular content on IPFS by copying it to normal HTTP servers. Requesting an IPFS document would query a few popular repositories, then revert back to normal IPFS if it's not found. These buffer servers would also track what's popular and shuffle around what they store accordingly.
The irony is that this and other IPFS problems will (must?) be fixed by recentralization. Cloudflare is doing this with IPFS Gateway, and Google will surely embrace/extend/usurp IPFS if it becomes popular. The user experience of bare IPFS is just not good enough.
Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)
#19[deleted]
Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)
#20Is 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