Live data from Hacker News

Nebulus: An IPFS-Less IPFS

nebulus.dev

21–30 of 42 posts

Re: Nebulus: An IPFS-Less IPFS

#21
post #12

This entire project can be replaced in two different ways with just IPFS. You don't have to run IPFS to be able to add files or retrieve them (if you've added them on the same computer), so simply add the files without running the daemon and you're already "Offline and Private" and "IPFS without the Network". If that's not enough, you can also run your IPFS daemon with `--offline` and it won't connect to any network,…

Hi there, just want to clarify that Nebulus is not a replacement for IPFS or competes with IPFS. In fact it internally uses all the features you just mentioned. In fact it's even powered by JS-IPFS and makes use of the "--only-hash" features and other features you mentioned. I needed a programmatic way to do all these things (as well as many other user friendly features that the IPFS raw protocol will never provide)…

This is really great stuff, thank you for making this!

Re: Nebulus: An IPFS-Less IPFS

#22

What I really want is a private, secure IPFS. I do want the network functionality, but I want it to exist only between my nodes. I know I can pin encrypted blobs, but I want something that handles this transparently. Is this possible somewhere?

You can run a private network by configuring all your nodes with a pre-shared "swarm key" and running your own bootstrap nodes.

There's some documentation here: https://github.com/ipfs/go-ipfs/blob/release-v0.9.0/docs/exp...

Re: Nebulus: An IPFS-Less IPFS

#23
post #12

This entire project can be replaced in two different ways with just IPFS. You don't have to run IPFS to be able to add files or retrieve them (if you've added them on the same computer), so simply add the files without running the daemon and you're already "Offline and Private" and "IPFS without the Network". If that's not enough, you can also run your IPFS daemon with `--offline` and it won't connect to any network,…

Hi there, just want to clarify that Nebulus is not a replacement for IPFS or competes with IPFS. In fact it internally uses all the features you just mentioned. In fact it's even powered by JS-IPFS and makes use of the "--only-hash" features and other features you mentioned. I needed a programmatic way to do all these things (as well as many other user friendly features that the IPFS raw protocol will never provide)…

So, it isn't an IPFS-less IPFS but a layer on top of IPFS?

Re: Nebulus: An IPFS-Less IPFS

#24
post #23
post #12

Earlier quoted context omitted.

Hi there, just want to clarify that Nebulus is not a replacement for IPFS or competes with IPFS. In fact it internally uses all the features you just mentioned. In fact it's even powered by JS-IPFS and makes use of the "--only-hash" features and other features you mentioned. I needed a programmatic way to do all these things (as well as many other user friendly features that the IPFS raw protocol will never provide)…

So, it isn't an IPFS-less IPFS but a layer on top of IPFS?

It's full on IPFS with a bit of IPFS on top.

Re: Nebulus: An IPFS-Less IPFS

#25
post #20

What's the use-case for this kind of usage of IPFS? Is it just a generic content addressable store for local use? Like perhaps use it to compile and install packages that you symlink into your system path a bit like DIY nix?

I wrote a dedicated section in the documentation just for this, it can be pretty powerful: https://docs.nebulus.dev/#/?id=use-cases

Looks great, thank you for presenting it so thoughtfully too.

Do I read correctly to mean Nebulus could potentially be used as a replacement for p2p file xfer, such as per wormhole? Any caveats with such a usecase?

(Also, just FYI there's a one-letter typo with the first sub-title under API)

Re: Nebulus: An IPFS-Less IPFS

#26

Very confused by the name. I thought this was related to the Nebulous Labs (the startup behind the Sia storage network) and their work around IPFS: https://blog.sia.tech/skynet-summer-2021-update-86ed8db21eae

A couple of days ago I’ve released an IPFS DHT crawler and named it Nebula [0] if I knew that this was such a crowded place…

[0] https://github.com/dennis-tra/nebula-crawler

Re: Nebulus: An IPFS-Less IPFS

#27

This entire project can be replaced in two different ways with just IPFS. You don't have to run IPFS to be able to add files or retrieve them (if you've added them on the same computer), so simply add the files without running the daemon and you're already "Offline and Private" and "IPFS without the Network". If that's not enough, you can also run your IPFS daemon with `--offline` and it won't connect to any network,…

Any ideas on the future of reduced-size IPFS utilities. For example, the go-ipfs Linux packages are somehere around 24MB. Is this a problem anyone is working on.

Re: Nebulus: An IPFS-Less IPFS

#28

This entire project can be replaced in two different ways with just IPFS. You don't have to run IPFS to be able to add files or retrieve them (if you've added them on the same computer), so simply add the files without running the daemon and you're already "Offline and Private" and "IPFS without the Network". If that's not enough, you can also run your IPFS daemon with `--offline` and it won't connect to any network,…

Any ideas on the future of reduced-size IPFS utilities. For example, the go-ipfs Linux packages are somehere around 24MB. Is this a problem anyone is working on.

People are working on smaller unixy tools to do fewer things well, but at least for the main codebase we are limited by go itself. Making binaries smaller is not simple at all...

You might be interested in checking out the rust implementation: https://github.com/rs-ipfs/rust-ipfs

Im not actually sure how well it would work for what youre after, but it is an option!

Re: Nebulus: An IPFS-Less IPFS

#29

Earlier quoted context omitted.

Any ideas on the future of reduced-size IPFS utilities. For example, the go-ipfs Linux packages are somehere around 24MB. Is this a problem anyone is working on.

People are working on smaller unixy tools to do fewer things well, but at least for the main codebase we are limited by go itself. Making binaries smaller is not simple at all... You might be interested in checking out the rust implementation: https://github.com/rs-ipfs/rust-ipfs Im not actually sure how well it would work for what youre after, but it is an option!

I was thinking more along the lines of splitting up the whopping 56MB single binary into smaller, individual programs.

There is a version of libp2p, which is the library used by IPFS, that is written in C++. Perhaps that is another option.

Re: Nebulus: An IPFS-Less IPFS

#30

This entire project can be replaced in two different ways with just IPFS. You don't have to run IPFS to be able to add files or retrieve them (if you've added them on the same computer), so simply add the files without running the daemon and you're already "Offline and Private" and "IPFS without the Network". If that's not enough, you can also run your IPFS daemon with `--offline` and it won't connect to any network,…

Any ideas on the future of reduced-size IPFS utilities. For example, the go-ipfs Linux packages are somehere around 24MB. Is this a problem anyone is working on.

what platforms are you targetting that cant take 24mb?
Post reply on HN