141–150 of 286 posts
Does IPFS come with some kind of content filter or firewall to protect its users? When child porn inevitably shows up, how do you protect yourself from accidentally downloading and then seeding it?
In IPFS you do not automatically relay things, you have to explicitly decide to.
I have a truly naive question about the distributed web: what makes the supporters of it think it will be any different from the original web. I mean, isn't it likely that at some point, there will be the need for a centralized search engine for it? Isn't it unavoidable that big companies like facebook runs their own non-distributed subnetwork, so that it can deliver standard functionality to all its users? The origi…
I am a novice, but I'll do my best to answer. IPFS isn't a replacement for the existing web like many of its predecessors, for the purposes of your question, it really works more like a drop-in shared caching system. The site host doesn't have to participate in IPFS for this to work. As an example: You host a blog. As an IPFS user, I surf to the blog and store your content in my cache. When another IPFS user attempts…
Say I have a site that sells Awesome Products. L337Hacker mirrors my site, does a DDOS on the original and lets IPFS take over, redirecting the shopping cart to his own site.
Is this a potential scenario? If so, is there any way to prevent it?
Most content is not written in simple english, and there's just not much incentive for somebody who may not know how to think critically/complexly (due to lack of western education) to engage with the internet.
I think distributed web is an interesting idea, and that IPFS really lists out some issues with the internet that we'd all win in solving, but I think maybe some of these, like developing nation web access, are solvable with current tech, and more culturally based solutions
Earlier quoted context omitted.
How so? IPFS so only as resilient as you are good at dodging DMCA notices.
Because mirroring content on IPFS is trivial and transparent to the consumer. All it takes is a single user (or an arbitrary number) outside of US jurisdiction and the content is more or less DMCA-immune. The equivalent is not practical in traditional HTTP, where content at risk of being taken down is scraped from the server and that snapshot-in-time is hosted as a mirror, generally at a different domain.
Which is also why a regular consumer should never use IPFS and why prosumer should immediately disable caching and seeding upon install.
> All it takes is a single user (or an arbitrary number) outside of US jurisdiction and the content is more or less DMCA-immune.
Perhaps so, but if your plan for resiliency is based on the kindness of strangers in countries where the DMCA nor censorship does not apply, it's not much of a plan.
Plus you'll still have to seed the original which opens you up to liability, as IPFS does not provide any kind of anonymity.
So, while better than traditional HTTP, IPFS isn't really immune to takedowns nor very resilient.
Earlier quoted context omitted.
The idea is that some fraction of users will be configured to reshare content, which helps distribution for popular content scale. This seems to work in practice for bittorrent.
Yes, but only for suitably popular content, as all the dead torrents will testify. This doesn't make IPFS very appealing to Joe Blow, content maker unextraordinaire.
I believe this could work amazingly well for netlabels and indie bands.
Earlier quoted context omitted.
Private networks is something that we're working on (track it here: https://github.com/ipfs/notes/issues/146 ) but it would be private-private, only access+upload between your nodes. "Accessible by anyone - upload only by you" is not gonna be supported since it doesn't really make sense. If someone has a hash of a file, they can rehost it because they can access it. In IPFS you're not locating files based on WHERE th…
> Private networks is something that we're working on Pretty sure you can already do it by setting up your a node on e.g. a Digitalocean droplet, removing all bootstrap nodes from its config file, and having everyone on the network replace the bootstrap node addresses in their config file with your server's address. Granted that's not a very user-friendly way to do it, but when I tried it it seemed to work.
With your current setup, if/when a node gets connected to someone else (maybe someone connects directly to you), your entire network will connect from that, since the connections will be shared with the peers.
Earlier quoted context omitted.
I am a novice, but I'll do my best to answer. IPFS isn't a replacement for the existing web like many of its predecessors, for the purposes of your question, it really works more like a drop-in shared caching system. The site host doesn't have to participate in IPFS for this to work. As an example: You host a blog. As an IPFS user, I surf to the blog and store your content in my cache. When another IPFS user attempts…
How would you prevent fraud? Say I have a site that sells Awesome Products. L337Hacker mirrors my site, does a DDOS on the original and lets IPFS take over, redirecting the shopping cart to his own site. Is this a potential scenario? If so, is there any way to prevent it?
Does IPFS come with some kind of content filter or firewall to protect its users? When child porn inevitably shows up, how do you protect yourself from accidentally downloading and then seeding it?
By simply not downloading and seeding it. ;) In IPFS you do not automatically relay things, you have to explicitly decide to.
You seem to have glanced over the qualifier I used: accidentally.
Given a hash for an IPFS resource, how do you know it does not contain child porn before you retrieve it?
Once you have downloaded it you have committed a crime. There are no take backs with strict liability crimes and IPFS provides no anonymity, so there is a record of you downloading and seeding child porn.
> In IPFS you do not automatically relay things, you have to explicitly decide to.
Really?
Correct me if I'm wrong, but I was under the impression that immediately once you retrieve a hash via IPFS, you cache it and start seeding it.
Earlier quoted context omitted.
Yes, but only for suitably popular content, as all the dead torrents will testify. This doesn't make IPFS very appealing to Joe Blow, content maker unextraordinaire.
Joe Blow would just need to find some fans who think that keeping his content available for others is worth their while. I believe this could work amazingly well for netlabels and indie bands.
But let's roll with it anyway. How does IPFS solve this problem, and more specifically how does IPFS solve this problem any better than just publishing a torrent of Joe Blows collected ramblings?