Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

HTTP is obsolete – it's time for the distributed, permanent web (2015)

ipfs.io

Post reply on HN
Print view View original

211–220 of 337 posts

Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)

#211

Post by perl4ever »

lovemenot wrote: post #185
muxator wrote: post #149

Earlier quoted context omitted.

I do not understand the downvotes here. "It was obvious to everyone watching that the technology was going to change everything": how to disagree?

I wasn't a down-voter, but I didn't have 56k in 1994. 14.4 baud iirc. You wouldn't call it fast.

I think something regulatory changed about 1995, such that there were instantly tons of ISP startups, and I think that 33.6k modems were available about then.

I had a 14.4K Zoom modem, but I'm pretty sure the ISP I worked for around '95-'96 was buying lots of US Robotics 33.6 modems.

I agree that 56k came a bit later, and didn't necessarily work on any particular phone line.

Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)

#212

Post by kbumsik »

noman-land wrote: post #50
jeroenhd wrote: post #3

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…

I love IPFS. It's one of my favorite recent technologies, but I think people have unrealistic expectations about such a young idea. Decentralized tech doesn't work well until the network effects build up. IPFS has the interesting quality that the more popular a piece of content is, the easier it is to get ahold of. If millions of people were using IPFS, the most popular content would be being served by many thousands…

> If millions of people were using IPFS

You criticize that people have unrealistic expectation, and then you are making an unrealistic claim...

Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)

#213

Post by sam345 »

Taek wrote: post #186
thomashop wrote: post #178

Earlier quoted context omitted.

I would have preferred IPFS to do the storage and propagation of data really well and not implemented stuff like IPNS in the core. To me this should be a separate codebase. And I see this in other features they have been including too. I'm using IPFS quite heavily to store content generated on https://pollinations.ai but there is no way I could run it without a centralized node that I have control over at the moment…

Have you had a chance to try Skynet? It provides all of the same features as IPFS, but it's also a lot more performant and higher uptime. You wouldn't need a centralized node that you run yourself.

Do you have any good links to Skynet? I could just find an old GitHub repo. Is it in active use ?

Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)

#214

Post by garrickvanburen »

Gigachad wrote: post #140
BiteCode_dev wrote: post #62

Earlier quoted context omitted.

Imagine if we said that about web sites at the begining. The Web needs to decide what it want to be? A plaftorm to sell stuff? Contact people? Write? Listen to music?

It's been 6 years now and IPFS is still stuck with the same problems it had at the start with no real pathway to being useful. Most technology does something useful early on. I don't know the timeline for the web but I don't imagine it involved 6 years of marketing and selling to investors while not serving any purpose well.

HTTP was invented in 1989.

Netscape was founded in 1994.

So, if you’re comfortable with either of those a starting point, 6 years is somewhere in the dot com boom.

Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)

#215

Post by noway421 »

davidgerard wrote: post #165
CharlesW wrote: post #23

The 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.)

It absolutely guarantees nothing of the sort. A big problem in the NFT space of late is that OpenSea sells NFTs that link to an IPFS URL, then doesn't bother seeding the image after it's sold - so a pile of NFT images no longer exist anywhere on the IPFS. https://www.vice.com/en/article/pkdj79/peoples-expensive-nft...

One benefit is that you or anyone for that matter can seed NFT images on IPFS.

You also gotta look into the smart contract code and see if baseURI an IPFS link or someone's proprietary website.

Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)

#216

Post by bawolff »

acdha wrote: post #141
noman-land wrote: post #50

Earlier quoted context omitted.

I love IPFS. It's one of my favorite recent technologies, but I think people have unrealistic expectations about such a young idea. Decentralized tech doesn't work well until the network effects build up. IPFS has the interesting quality that the more popular a piece of content is, the easier it is to get ahold of. If millions of people were using IPFS, the most popular content would be being served by many thousands…

> think people have unrealistic expectations about such a young idea. This interesting given your description: > IPFS has the interesting quality that the more popular a piece of content is, the easier it is to get ahold of. If millions of people were using IPFS, the most popular content would be being served by many thousands of people, and finding it and downloading it would be extremely fast. This idea hasn’t been…

> This idea hasn’t been new since the turn of the century (BitTorrent offered exactly that in 2001)

I feel like freenet (2000) is maybe a better comparison

Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)

#217

Post by ntr-- »

BiteCode_dev wrote: post #62
adfrhgeaq5hy wrote: post #58

IPFS needs to decide what it wants to be. Is it about being a decentralized caching layer? Is it about permanently storing content? Is it about replacing my web server? Is it about replacing DNS? Is it about censorship resistance? Right now it does none of those things well. The client chews through CPU and memory when seemingly doing nothing. If I try to download content, it is far slower than BitTorrent unless I go…

Imagine if we said that about web sites at the begining. The Web needs to decide what it want to be? A plaftorm to sell stuff? Contact people? Write? Listen to music?

- A complex system cannot be “made” to work. It either works or it doesn’t

- A simple system, designed from scratch, sometimes works.

- Some complex systems actually work.

- A complex system that works is invariably found to have evolved from a simple system that works.

- A complex system designed from scratch never works and cannot be patched up to make it work. You have to start over, beginning with a working simple system.

Systemantics, John Gall, 1978

Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)

#218

Post by [deleted] »

sebastos wrote: post #102
adfrhgeaq5hy wrote: post #58

IPFS needs to decide what it wants to be. Is it about being a decentralized caching layer? Is it about permanently storing content? Is it about replacing my web server? Is it about replacing DNS? Is it about censorship resistance? Right now it does none of those things well. The client chews through CPU and memory when seemingly doing nothing. If I try to download content, it is far slower than BitTorrent unless I go…

IPFS's design makes it so that it's all of those things, or none of them. Picking one of them doesn't fit the shape of the technology. IPFS is basically the answer to the question "what is the RIGHT way to decentralize the web?". If you think about that question hard enough, then anyone can see that their way of doing it is the "right" way. It's just obvious. The problem is that all of these mutually supporting compo…

[deleted]

Re: HTTP is obsolete – it's time for the distributed, permanent web (2015)

#219

Post by remram »

mayli wrote: post #111

ironically, few links on this 2015 post are dead, and most of them being ipfs releated. https://ipfs.io/ipns/QmTodvhq9CUS9hH8rirt4YmihxJKZ5tYez8PtDm... https://ipfs.io/ipns/ipfs.git.sexy/

> It's time for ... (2015)

The title shows clearly that they were wrong.

Post reply on HN