Live data from Hacker News

Filecoin Foundation Successfully Deploys IPFS in Space

fil.org

201–210 of 215 posts

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#201
post #139

Earlier quoted context omitted.

Crypto isn't internet. At best, crypto is Juicero

Within 20 years Ethereum will be used as a global coordination and settlement layer, and is well on its way to achieving that. But whatever helps you sleep better at night.

> Within 20 years Ethereum will be used as a global coordination and settlement layer

Of course it won't

> and is well on its way to achieving that.

Of course it isn't

> But whatever helps you sleep better at night.

Well, we all know what lullabies you sing to yourself

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#203

Sure space is cool (or maybe not, but don't want to upset the HN consensus), but this seems like a total gimmick and waste of money, time, and PR.

> waste of money, time, and PR

That's exactly what cryptomoney has been about for years now, so it fits right in.

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#204
post #10

Earlier quoted context omitted.

Has it? I have never seen anybody using IPFS in the wild, even projects for which it should be well suited (archive.org, Linux package distribution, Git, Lemmy, Imgur, CivitAI), don't use it. Worse yet, IPFS still provides no real way to deal with private or local data, which drastically limits its use. I love the idea about data being addressable by hash, but I don't feel IPFS has actually delivered anything meaning…

I was working on the same building as the team from Protocol Labs. I talked with a couple of devs and it seems like they never even considered that most people who would be interested in running a node would like to have control over who gets access to the pinned files. I think I opened a ticket asking for an ACL system, but it got closed. I really had high hopes for it, but I realized that all I really want is an ob…

We've been pioneering privacy and access control on top of IPFS since 2015 in Peergos [0].

We have block level access control for example: https://peergos.org/posts/bats

As well as E2EE, sharing, trustless servers and more [1].

[0] https://github.com/peergos/peergos

[1] https://book.peergos.org

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#205
post #77
post #10

Earlier quoted context omitted.

Has it? I have never seen anybody using IPFS in the wild, even projects for which it should be well suited (archive.org, Linux package distribution, Git, Lemmy, Imgur, CivitAI), don't use it. Worse yet, IPFS still provides no real way to deal with private or local data, which drastically limits its use. I love the idea about data being addressable by hash, but I don't feel IPFS has actually delivered anything meaning…

Wouldn't all those examples also work just as easily with torrents/magnet-links? I think in all those cases a central server distribution model has unfortunately been "good enough" for the majority of users (even though their data is mined and ads are injected) When it comes to FOSS, I personally don't understand why something like a package manager isn't P2P by default. It feels very aligned with the hacker culture…

There has been attempts at doing torrent-based package distribution, see the notes of debian testing it here: https://wiki.debian.org/DebTorrent. There are basically 2 problems:

Packages are a lot of small files, and not everyone is interested in them all. Torrents are good for large content that everyone wants. The two are in opposition and there needs to be a balance: do you need to make One Unique Torrent with everything, but then peers have to individually ask each and every other peer if they have the content they're looking for, making it unscalable ? Or do you make one torrent per package, meaning peers have to track thousands of torrents ? (That's the direction IPFS took, which is why it's extremely inefficient and resource-heavy). DebTorrent has made the choice to go in the middle.

The real problem, to me, is that content-addressed content is the anti-privacy protocol: since you ask everyone "do you have this content", you're basically telling everyone what you want. In the case of installing packages, this means telling everyone what the version of your packages is, and is potentially a security issue.

But the real "problem" is that it fails at being much more better than the existing solution. Bandwidth is cheap, storage is cheap, so hosting everything on a few independent but centralized servers is good enough.

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#206

Earlier quoted context omitted.

I was working on the same building as the team from Protocol Labs. I talked with a couple of devs and it seems like they never even considered that most people who would be interested in running a node would like to have control over who gets access to the pinned files. I think I opened a ticket asking for an ACL system, but it got closed. I really had high hopes for it, but I realized that all I really want is an ob…

We've been pioneering privacy and access control on top of IPFS since 2015 in Peergos [0]. We have block level access control for example: https://peergos.org/posts/bats As well as E2EE, sharing, trustless servers and more [1]. [0] https://github.com/peergos/peergos [1] https://book.peergos.org

Ok, that is really cool. I worry though that this is too tied into the whole peergos architecture? Can you give some pointers on what would I need to do to have a node with the extended protocol and nothing else?

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#207
Maybe initiatives like that will finally help transitioning to IPv6. We're out of address space here on Earth, and now we're going with TCP/IP to space.

If we won't be wasteful with IPv6 space, it'll suffice for all inter-planetary and inter-galactic communication. Considering 1 trillion stars per galaxy and 1 trillion galaxies in the universe, we're safe with more than 340 trillion addresses per star.

We would be able to address between 1/3 to 1/2 of all atoms in the universe with IPv6.

Now that's a safety margin!

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#208

Earlier quoted context omitted.

We've been pioneering privacy and access control on top of IPFS since 2015 in Peergos [0]. We have block level access control for example: https://peergos.org/posts/bats As well as E2EE, sharing, trustless servers and more [1]. [0] https://github.com/peergos/peergos [1] https://book.peergos.org

Ok, that is really cool. I worry though that this is too tied into the whole peergos architecture? Can you give some pointers on what would I need to do to have a node with the extended protocol and nothing else?

The block auth is very generic, just an extra top level key in cbor maps or a small prefix in raw blocks. The protocol is S3 V4 signatures.

There is a Java implementation of the modified bitswap for this in Nabu [0] and a Go one in ipfs-nucleus [1]. With both of these you can use whatever auth verification protocol you like.

[0] https://github.com/peergos/nabu

[1] https://github.com/peergos/ipfs-nucleus/

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#209

Earlier quoted context omitted.

One doesn't exclude the other. Theranos and enron doesn't mean all companies are scams.

Yet the majority of crypto companies are scams.

The majority of stocks are scams, they're called penny stocks

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#210

I'm still a little lost. Could someone more knowledgeable than me explain how operations in space would benefit from a public content-addressable filesystem? This seems like the kind of application that works best when bandwidth and storage are cheap, and I would have assumed that that, in space, both are about as far from cheap as you can get.

It's quite the opposite. We've sketched out a school platform using IPFS that allows very remote villages in third world countries that have little to no internet to still have viable "google drive" like experiences for school home work. The idea is that a single USB drive that contains all the updated files for the google drive is sufficient for the entire network (that exists in the village, that is decent, but has…

Have you actually used it? The usb with random information is a very versatile distribution method, I am not sure IPFS is much better than this.
Post reply on HN