Live data from Hacker News

Filecoin Foundation Successfully Deploys IPFS in Space

fil.org

31–40 of 215 posts

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#31

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…

ACLs are fundamentally incompatible with blockchains. Your only solution is to encrypt those files, and have off-chain key management if you ever want to revoke access.

IPFS and distributed filesystems have nothing to do with blockchains.

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#33
post #10
post #7

Filecoin is probably one of the few cryptocurrencies with intrinsic value, even if the amount is debatable. IPFS has stood the test of time and seems like a good protocol; and a cryptocurrency that can be used to pay for storage is not valueless.

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…

> Has it? I have never seen anybody using IPFS in the wild

Every time someone downloads a book from a shadow library like Library Genesis, it's through IPFS most of the time, often via an IPFS gateway such as Cloudflare's IPFS gateway, so you don't even notice it's using IPFS. These shadow libraries have millions of users per day, especially academics.

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#34
post #7

Filecoin is probably one of the few cryptocurrencies with intrinsic value, even if the amount is debatable. IPFS has stood the test of time and seems like a good protocol; and a cryptocurrency that can be used to pay for storage is not valueless.

So is Storj and Sia. It raises the question, though: I can pay Storj S3 with STORJ tokens, and I can also pay for renterd space with Sia tokens, and I can also pay for IPFS with Filecoin, and all of them still work with good old credit cards. What "intrinsic" value is there for any of these tokens, if they can only be used on their own internal economies? And before the "but permissionless, so I can pay with crypto!"…

I’ve earned Storj for years by renting excess hard drive space to store other people’s files. Having a native currency lets you innovate in some unique ways.

Microtransactions are not practical with credit cards and other traditional settlement methods.

The reasons not to use something like DAI are fundraising (unfortunately - crypto VCs really like seeing a token), network bloat/decentralization, and leadership risk. Your own currency is less likely to collapse by other people’s bad decisions.

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#36
post #7

Filecoin is probably one of the few cryptocurrencies with intrinsic value, even if the amount is debatable. IPFS has stood the test of time and seems like a good protocol; and a cryptocurrency that can be used to pay for storage is not valueless.

Sounds like bullshit to me.

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#37
post #24
post #18

Earlier quoted context omitted.

> there is also the legal problem that IPFS conflicts with copyright. Redistributing anything is illegal by default I think you might misunderstand how IPFS works, or possibly confuse it with Freenet. When you use IPFS, nothing is automatically distributed, unless they happen to know the hash of the content you've added locally. It's not until someone starts to explicitly request data from you, that you start sharing…

Everything in your local cache is redistributed, meaning every single website you view through IPFS ends up getting potentially redistributed. Can you guarantee that each and every item you view on the Web allows redistribution?

I don't know how it works legally, but if you publish your own content to a distributed protocol like IPFS you should expect it to be distributed. If content that shouldn't be redistributed is put on the public IPFS, it should be the person who added it's fault, imo.

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#38

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.

The internet traditionally uses location-addressing. A DNS name pointing to a IP which has a specific location your computer tries to reach in order to fetch the content. This means that particular node needs to respond to you, and the bandwidth is depending on the bandwidth available on the particular path to that specific node.

Instead, IPFS uses content-addressing, where the content is hashed and given a ID based on the content itself. So "foo" could have the ID A, while "bar" could have the ID B. No matter who added the content to the network, if the content is the same, the ID will be the same.

The benefit of this is that you can fetch the data from anywhere, and you'll get the data you wanted guaranteed (assuming the content is available somewhere on the network).

In terms of space, imagine being on the moon and requesting some website. With location-addressing, you have to be able to reach that particular node, and the data has to travel from there to you. With content-addressing, that content can be fetched from anywhere, maybe another node on the moon has it already, so it can fetched quicker from there, or some node in-between the moon and earth.

More reading about content-addressing: https://en.wikipedia.org/wiki/Content-addressable_storage

Magnet links and git are two fairly common technologies that uses content-addressing with lots of benefits.

(edit: of course, this is a simplification of both how IP, networks, IPFS, DNS and more works, but I hope it provides a fair overview at least)

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#39

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.

I think the idea behind content addressable databases like this is that they are supposed to be permanent. Putting it out into space may be a way of saying "its never going down".

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#40
post #38

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.

The internet traditionally uses location-addressing. A DNS name pointing to a IP which has a specific location your computer tries to reach in order to fetch the content. This means that particular node needs to respond to you, and the bandwidth is depending on the bandwidth available on the particular path to that specific node. Instead, IPFS uses content-addressing, where the content is hashed and given a ID based…

Torrents with extra steps, eh?
Post reply on HN