No. Similar to a Distributed Hash Table. It won't matter if people go https://mysite or https://yoursite`. With a DHT, all you need is the hash of the file, and your node will be able to locate all servers who have the relevant pieces of data and send it to you.
I actually do know how it works, but I sure have a hard time understanding the usefulness.
Then we are going to go in circles: people already described use-cases and your knee-jerk reaction is to respond with "but I can do *something vaguely related* with OVH".
This gets tiring, and I'd rather do something else with my time. Have a good one.
Maybe you're right, and I fail to find any kind of usefulness for this distributed hash table. I really try though, sorry to inconvenience you, but it sure feels like a BTC ledger without the security nor the longevity.
As with a lot of things in the crypto adjacent space, they’re offering a solution looking for problems. Some problems (such as storing and distributing files) are essentially solved (many cheap providers for both storage, distribution, and/or both to choose from), while others (such cryptographically secured immutable ledger for provenance tracking in specific use-cases) might benefit from the technology. Knowing which is which and where to adopt what tech is the challenging part.
I'm 100 percent with you here, I definitely feel like the IPFS "crowd" is trying to find a usefulness, and I hope they do. I'm all for decentralized, protected communication, storage and so on! If you need a proof of that just ask and I'll deliver.
But it feels like they are still looking for that usefulness.
I'm not even here saying "prove me this or that", but I do question the usability which I understand can be felt like an attack for some people.
You are really failing to understand how it works, and I am failing to explain it properly.
No. Similar to a Distributed Hash Table. It won't matter if people go
https://mysiteor https://yoursite`. With a DHT, all you need is the hash of the file, and your node will be able to locate all servers who have the relevant pieces of data and send it to you.I actually do know how it works, but I sure have a hard time understanding the usefulness.
Then we are going to go in circles: people already described use-cases and your knee-jerk reaction is to respond with "but I can do *something vaguely related* with OVH".
This gets tiring, and I'd rather do something else with my time. Have a good one.
Maybe you're right, and I fail to find any kind of usefulness for this distributed hash table. I really try though, sorry to inconvenience you, but it sure feels like a BTC ledger without the security nor the longevity.
As with a lot of things in the crypto adjacent space, they’re offering a solution looking for problems. Some problems (such as storing and distributing files) are essentially solved (many cheap providers for both storage, distribution, and/or both to choose from), while others (such cryptographically secured immutable ledger for provenance tracking in specific use-cases) might benefit from the technology. Knowing which is which and where to adopt what tech is the challenging part.
I'm 100 percent with you here, I definitely feel like the IPFS "crowd" is trying to find a usefulness, and I hope they do. I'm all for decentralized, protected communication, storage and so on! If you need a proof of that just ask and I'll deliver.
But it feels like they are still looking for that usefulness.
I'm not even here saying "prove me this or that", but I do question the usability which I understand can be felt like an attack for some people.