What problem does IPFS actually solve?
IPFS is the Distributed Web
81–90 of 286 posts
Re: IPFS is the Distributed Web
#82If I try to host a javascript application that uses LocalStorage for saving data, it would be visible to any other ipfs JavaScript application because they all exist under the same domain, right? Have you thought about having the URLs be something like ipfs:///index.html instead of http://local host//index.html so browsers keep the LocalStorage for each ipfs hash separated?
Re: IPFS is the Distributed Web
#83If I try to host a javascript application that uses LocalStorage for saving data, it would be visible to any other ipfs JavaScript application because they all exist under the same domain, right? Have you thought about having the URLs be something like ipfs:// /index.html instead of http://local host/ /index.html so browsers keep the LocalStorage for each ipfs hash separated?
We're planning to use Same-origin policy to prevent this. It was first brought up here: https://github.com/ipfs/go-ipfs/issues/651
You can read more about same-origin policy here: https://developer.mozilla.org/en-US/docs/Web/Security/Same-o...
Re: IPFS is the Distributed Web
#84Earlier quoted context omitted.
I work with IPFS so it would be very handy to know what you feel is slow exactly. We're working our hardest to make it as fast as possible but sometimes we fall through, so more information so we can fix it would be wonderful!
Most "slowness" is related to content that is either relatively fresh on the network or or rare content. If my node is the only one seeding the file, accessing it via gateway.ipfs.io is slow but it's pretty obvious why; I'm the only provider. So while for very public content IPFS is rather fast, if you share a couple files with a few friends, it's a bit slower. Of course, this all depends on upload/download speeds, m…
Ah, I understand. Yeah, it's not much we can do about that but in the future it can be expected that you'll be able to use some sort of service to help you with the initial seeding of the content.
So instead of you sharing a file from your home connection and five friends have to share that, you'll share your file with some hosting provider and once they have the file, you'll just send the same hash to your friends and you'll have at least 2 nodes providing the file.
Re: IPFS is the Distributed Web
#85Earlier quoted context omitted.
What do you suggest?
There's the million-dollar question. I've been bashing my head against it for a few years now. I think an important thing is to give everyone a say in how these large computer networks affect their lives. How to do that in the context of a broken political system isn't clear to me at all.
Any bashing on Named Data Networking? https://en.wikipedia.org/wiki/Named_data_networking
Rather than the system getting less reliable exponentially as it scales up, it gets more reliable exponentially as it scales up. https://www.youtube.com/watch?v=gqGEMQveoqg&t=1667
Integrity and trust are properties of the data; not of the way that you obtain it. https://www.youtube.com/watch?v=gqGEMQveoqg&t=3006
There's no routing. You get rid of all of the routing chatter. You get rid of all of the routing brittleness. https://www.youtube.com/watch?v=yLGzGK4c-ws&t=5071
We wanted to turn around the incentive structure where right now senders have a lot of power and receivers have basically nothing, they have to eat what they're fed. https://www.youtube.com/watch?v=Yth7O6yeZRE&t=23890
Re: IPFS is the Distributed Web
#86Suppose I'm poking around IPFS and unintentionally download some unauthorized copyrighted content. Is my computer going to automatically start sharing this content, exposing me and my ISP to legal action? Or if there is a way to prevent sharing particular content that I've accessed, what's to stop me from leeching everything and never sharing anything? (Edit: Ah, now I see "BitSwap" as possibly addressing my second q…
For #1, yes. For #2, also yes, and there's nothing to stop you from leeching save the goodness of your heart and your own personal laziness.
Since it's impossible to know who owns, claims to own, or has licensed any particular content, #1 is a fatal flaw unless users can officially receive immunity (which seems doubtful). Otherwise we'll have a situation like speeding on the highway, where "everyone does it" at the risk of a random ticket, but in this case the fines are thousands to millions of dollars.
Re: IPFS is the Distributed Web
#87If I try to host a javascript application that uses LocalStorage for saving data, it would be visible to any other ipfs JavaScript application because they all exist under the same domain, right? Have you thought about having the URLs be something like ipfs:// /index.html instead of http://local host/ /index.html so browsers keep the LocalStorage for each ipfs hash separated?
We're planning to use Same-origin policy to prevent this. It was first brought up here: https://github.com/ipfs/go-ipfs/issues/651 You can read more about same-origin policy here: https://developer.mozilla.org/en-US/docs/Web/Security/Same-o...
Putting a hash in the hostname/domain would also be using same-origin policy. The issue you linked refers to using suborigins, which seems to still be a draft proposal with no implementer buy-in outside of Chromium [1].
Re: IPFS is the Distributed Web
#88IPFS appears here every 6 months, every 6 months the same questions get asked, the same problems get raised, the same collective sigh of bewilderment/disappointment appears to emanate from the comments, and it goes away again for another 6 months. Everybody wants something this clever and community-spirited to work, but the basic problem is, I don't want my data to be vulnerable to slow, unreliable endpoints, or peop…
I would say the impermanence is one of the most appealing aspects of the system. Content that no one uses and that no one is willing to sustain gets culled from the network, what more could you ask for?
Re: IPFS is the Distributed Web
#89So I've been thinking about creating a basic site running on IPFS and here's my dillema. The hash of each page is a sha256 of the contents right? So lets say you have 3 pages A, B and C, A links to B, B links to C, C links to A. How do you create all 3 pages with correct links to each other? When you create page A you have to have the SHA of page B, but then to create page B you have to have the SHA of page C and fin…
This is about IPLD (so data linking to each other instead of files, but the concepts are the same): https://github.com/ipfs/pm/blob/master/meeting-notes/2016-09...
Also, you can use relative paths :P
Re: IPFS is the Distributed Web
#90Earlier quoted context omitted.
> where you trust all the nodes Why do you think that's needed? Of course if majority of nodes cheated and said "sure, I've got that file" and send you random garbage instead so you have to retry, that would be bad. But if majority are running proper implementation, you don't really need to trust anyone.
You need just one node to send you the right data. No need for the majority.
You need a reasonable number of nodes. Likely a large majority. Otherwise you'll just keep redownloading garbage data and discarding it. And likely doing it slower than bad nodes can leave/rejoin the network with new ips.