Live data from Hacker News

Filecoin Foundation Successfully Deploys IPFS in Space

fil.org

151–160 of 215 posts

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#151
post #144
post #124

Earlier quoted context omitted.

For your example, sending one copy to space is better than sending three copies.

Not seeing how starlink can’t just put a hd and serve stuff.

You'll need a way to find which starlink has the hdd that has the data you need to access.

Content-based indexing (as in IPFS) handles that. Plus the data gets cached in the starlink you locally accessed, in your example.

It might help to think about IPFS as a public CDN operating on an open specification protocol and an open-source implementation.

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#152

Earlier quoted context omitted.

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

I’ve recently observed that both IPFS and the Cloudflare gateways are extremely unreliable on Libgen.

That's besides the point. The point being made was that IPFS is being used in production.

You bring up a valid point though. From my experience, IPFS suffers from a tragedy of the commons issue. It's performance is generally terrible because the free providers are overloaded.

Re: Filecoin Foundation Successfully Deploys IPFS in Space

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

Hi, PL-funded founder here.

This was one of the things that made IPFS a non-starter for us. We ended up grafting Hashicorp Vault into kubo (the go-ipfs implementation) so that we could use IPFS and have things like detetes and access revocation that actually work.

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#154
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.

Is there actually a way to use filecoin to pay for IPFS pinning yet? Last time I checked a couple years ago Filecoin was worth more than Disney and the actual use case was vaporware.

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#155
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.

Why the torrents didn’t move to IPFS already? I think it looks more like DoA than standing the test of time. From my experience it’s a “heavy tech”/resource hog hog that does not appeal neither to developers nor to end users(it has no killer app)

Because torrents work, so they don't need to switch to IPFS.

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#156

Earlier quoted context omitted.

It's not. They pay out via zksync (layer 2 system) to avoid fees, but they only accept payment in the main chain. So if you want to cash out or use the tokens you receive, you need to eat the fees. It's ridiculous and a clear mechanism for them to restrict the circulating supply.

It's an evolving ecosystem. Rollups are fairly new so imagine fully migrating to L2 is a work in progress.

What I mean is that they could do things on their business side, off-chain, completely independent from the "protocol" or smart contracts. If they already accept use a "traditional" payment processor to accept credit cards, why could't they add zksync as an option for payment on Tardigrade?

It's really not hard - I've done a PoC when I was working on https://hub20.io - but it doesn't help with their "tokenonomics", so they just ignore it.

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#157

Earlier quoted context omitted.

I’ve recently observed that both IPFS and the Cloudflare gateways are extremely unreliable on Libgen.

That's besides the point. The point being made was that IPFS is being used in production. You bring up a valid point though. From my experience, IPFS suffers from a tragedy of the commons issue. It's performance is generally terrible because the free providers are overloaded.

Not really:

> Every time someone downloads a book from a shadow library like Library Genesis, it's through IPFS most of the time

I would like to see evidence this is actually true. My theory is that IPFS's "success" in hosting Libgen is roughly turning ICO proceeds into free hosting. Paying for dedicated servers might have been more cost efficient and, given the performance issues, more robust!

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#158

Could it be to avoid content liability laws? Pirate bay used to run servers from balloons above a certain altitude for this reason.

And like those failed projects, this has the same fatal flaw: you need that offshore or high altitude server to connect to a base station on Earth in order to connect the server to the rest of the Internet. The authorities where those base stations are located don't look kindly on this one weird trick to evade sovereignty.

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#159

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 does not in any way involve a blockchain.

There's a separate "layer on top of IPFS" called Filecoin that does involve a blockchain. (From a technical point of view, it's not really a layer on top, more of a re-implementation of IPFS with a blockchain.)

I've worked on IPFS and know many of the key people at PL. They really are not blockchain people or cryptobros. They are much different from anyone else in crypto I have encountered. But ultimately they have to fund their activities somehow, and this is the reality of where the business potential is in P2P circa mid-2020s.

Re: Filecoin Foundation Successfully Deploys IPFS in Space

#160
post #24

Earlier quoted context omitted.

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?

Perhaps it should use the fact that any file A can be written as the XOR of two files B and C, where B and C look like complete noise. If you only host B and another person only hosts C, then there can be no copyright infringements, while you can still reconstruct A by simply XORing the other files together. Of course at the expense of having to store and transfer twice the amount of data.

This is engineer logic. This kind of thing would never fly in court. If you want an example, go back and look at what happened to Aereo back in 2014. They came up with a clever hack to work around broadcast TV copyright. It went to the U.S. Supreme Court and got shot down.
Post reply on HN