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

331–337 of 337 posts

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

#331

Post by skyde »

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…

I agree with you but I think compared to Http or even bittorrent It’s extremely easy to attack IPFS.

Anyone can register a lot of fake “seeder” for a file chunk making it hard to download that chunk.

Same problem for the name server.

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

#332

Post by perl4ever »

nl wrote: post #328
perl4ever wrote: post #324

Earlier quoted context omitted.

>The idea of Donald Trump as President of the USA I find this disturbing, because not only is it not true, that it originated in 2015, and many people have commented on how The Simpsons predicted it in 2000... https://en.wikipedia.org/wiki/Bart_to_the_Future ...but the reason they predicted it had a lot to do with Trump running in 2000, and more recently, he's reportedly been saying he is such a winner he won the fir…

You are missing the point of what I'm saying. Trump wasn't taken seriously as a candidate in 2015. He didn't declare his candidacy until July 2015 at which point his odds were 150/1 and it didn't get above 66/1 in 2015. https://www.bbc.co.uk/news/newsbeat-36392621 In 2000 his run wasn't taken seriously either. He had a approval rating of 7%. https://en.m.wikipedia.org/wiki/Donald_Trump_2000_presidenti...

Ok, fine, you wrote "the idea" and you meant "taking seriously".

But I suspect you had it right the first time. I sort of think "the idea" is the relevant stage. And that adds ~15 years to that particular thing.

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

#333

Post by easrng »

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

Earlier quoted context omitted.

> 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…

IPFS is basically BitTorrent if all the torrents could share with each other. IPFS is as if each "torrent" is a single chunk of data instead of a siloed collection of stuff. IPFS expands BitTorrent into a global filesystem. You can mount IPFS on your filesystem and address files by pointing at local resources on your machine. So you could have an HTML file say ` `. You can't do that with BitTorrent.

BitTorrent v2 shares dedups chunks between torrents as a side affect of changes to the hashing algorithm.

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

#334

Post by vmception »

zerocrates wrote: post #260
a1369209993 wrote: post #234

Earlier quoted context omitted.

> suddenly all of that traffic is hitting nodes with far fewer resources. One of the points of IPFS (and bittorrent before it) is that this is not a problem; each node that downloads the data also uploads it to other nodes, so having lots of traffic actually makes it easier to serve something (indeed, if it was already widely seeded by Google's mirror, there wouldn't be any sudden traffic).

I'm not particularly familiar with IPFS: does it have some solution for free-riding? BitTorrent as many have noted is great for popular things, even not-particularly-popular things, but absent incentives to continue seeding (i.e. private trackers' ratio requirements) even once-popular things easily become inaccessible as the majority of peers don't seed for long, or at all. I guess what I don't quite is what IPFS add…

Bittorrent use breaks Tor, IPFS download does not.

so that's one advantage to one audience

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

#335

Post by drdeca »

andrecarini wrote: post #203
drdeca wrote: post #197

What I would like, I think, is the ability to specify both the multihash and a place to request the data from. Like, if I’m talking to someone over some chat setup which doesn’t have a built in “send this file directly to this person” feature, it would be nice to be able to say, give them a multihash of the file and my external ipv6 address (+ port? I’m not quite sure how routing works), and have them request the fil…

You have just invented torrents! > give them a multihash magnet URIs > place to request data from trackers > try local network first Already baked in!

Just learned that apparently BitTorrent 2 supports multihash in magnet URI , including the merkle tree thing, so yeah that does sound like, exactly what I’m looking for?

So, sounds like I ought to learn to use bit torrent.

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

#336

Post by cyanydeez »

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…

as in government, even if you have the mythical unicorn, the actual behavior of the users is what decides what is right and will push that forward.

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

#337

Post by noman-land »

kbumsik wrote: post #212
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…

> If millions of people were using IPFS You criticize that people have unrealistic expectation, and then you are making an unrealistic claim...

I don't think that's necessarily true. Ethereum 2 is using libp2p to facilitate p2p communication between nodes. IPFS also uses libp2p. That means that every Ethereum node could easily become an IPFS node so people may end up running an IPFS node without even realizing it.
Post reply on HN