Filecoin Foundation Successfully Deploys IPFS in Space

Post by anthk » Tue, Jan 16, 2024, 8:26 PM UTC

geokon wrote: post #77

grumbel wrote: 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…

Post by jnthnvctr12 » Tue, Jan 16, 2024, 8:37 PM UTC

rglullis wrote: post #25

grumbel wrote: 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…

Post by pclmulqdq » Tue, Jan 16, 2024, 8:49 PM UTC

rglullis wrote: post #31

pclmulqdq wrote: post #29

Earlier quoted context omitted.

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.

Post by amelius » Tue, Jan 16, 2024, 8:56 PM UTC

fulladder wrote: post #160

amelius wrote: post #150

Earlier quoted context omitted.

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 by [deleted] » Tue, Jan 16, 2024, 9:03 PM UTC

diggan wrote: post #101

hasty_pudding wrote: post #93

Earlier quoted context omitted.

How do you mark something for deletion? Or once its in the network thats it? Seems easy to DDOS by changing one character many times in a file which generates a new id each time

> How do you mark something for deletion? The same as you'd delete anything from any protocol essentially, you delete it locally. If you've shared it on the internet, you ask people nicely to delete it, if they refuse, you either pursue them legally or give up. Basically, just like how you delete a picture from the internet today. > Seems easy to DDOS by changing one character many times in a file which generates a n…