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

IPFS 0.5

blog.ipfs.io

Post reply on HN
Print view View original

11–20 of 145 posts

Re: IPFS 0.5

#11

Post by gunshai »

mad44 wrote: post #4

Here is a summary of IPFS white paper http://muratbuffalo.blogspot.com/2018/02/paper-review-ipfs-c... The improvements announced are substantial.

You mean TRON /s

Edit : makin jokes about plagiarism people.

Re: IPFS 0.5

#13

Post by momack2 »

LockAndLol wrote: post #8

Hold up... You can pull docker images from ipfs? How? And do IPNS entries finally last more than 30 seconds? It would be nice to not have to constantly keep a node up just to have an IPNS entry.

IPNS records still have a default 24hr lifetime, but republishing your IPNS records is now much MUCH faster, so it should be much cheaper to run a process to republish these regularly. I assume you can also bump up your lifetime to >24hr if you want - but note that will mean nodes not using pubsub (aka getting updates pushed to them proactively) might be slow to get new updates.

Here's what's new for IPNS in the release: https://github.com/ipfs/go-ipfs/blob/master/CHANGELOG.md#ipn...

Re: IPFS 0.5

#15

Post by willscott »

omginternets wrote: post #12

I have a Go project that imports IPFS and libp2p libraries. What's the recommended way of upgrading those dependencies?

The release notes contain a pretty extensive list of what APIs have changed.

The path to upgrade the dependencies is probably to run `go get -u ` for the direct dependencies you're including, and then fixing errors that pop up from doing so.

Re: IPFS 0.5

#16

Post by whyrusleeping »

espadrine wrote: post #7
jarfil wrote: post #5

Earlier quoted context omitted.

The ping from Earth to Mars varies between 360 and 2600 seconds, so 30 might still be fast enough for an "interplanetary" thing.

Doesn’t IPFS still rely on Kademlia? Since node IDs are random, node lookup may require multiple interplanetary hops, no? For instance, from N1 on Earth to the nearest XORwise node in its routing table which might be N2 on Mars, whose routing table finds the target node N3 on Earth.

In an actual interplanetary setup, we would definitely not be using a single DHT across the entire space. The main idea once we get to that scale is either a different content routing system altogether, or sharded coral style DHTs (https://en.wikipedia.org/wiki/Coral_Content_Distribution_Net...)

Re: IPFS 0.5

#18

Post by echelon »

lachlan-sneff wrote: post #17

I wish they hadn't picked go. Go isn't a bad language really, but it's a huge pain to integrate a go library into an app written in another language.

C or Rust would be perfect. No GC runtime, no name mangling, fast, great ffi story.

Rust needs to start edging out Go for new tools. Kubernetes, Envoy, IPFS, etc. would have benefitted from it.

It might not have been time four years ago, but it's time now.

Post reply on HN