2 ms·
Nothing in the architecture of those protocols requires everyone to republish, especially publicly. The difference is in the namespace of those protocols. Rath
by mindslight 10y ago
Nothing in the architecture of those protocols requires everyone to republish, especially publicly.
The difference is in the namespace of those protocols. Rather than just reusing L4 addresses, they create addresses that are conducive to decentralization.
The problem with site mirroring services is once again fundamentally comes down to the naming. Either the site operator has to setup and incorporate the mirrors, or site visitors have to discover and visit each mirror manually. There is no middleground where you can ad-hoc casually ask a peer for a copy and have the exact same functionality.
- viraptor 10y agoIf you skip the P2P aspect of those networks, I'm not sure how much it really differs from distributing HTTP traffic over multiple domain names with possible anycast on IPs. You even get an automatic DNS split per region. What's the reason to go with IPFS / BT for distribution from only the endpoints that you control on the internet? (I do see good reasons for it in private networks) Yes, it is non-trivial to setup, but if you need it, then automating this part may be more trivial than getting clients to switch to a new protocol.
- mindslight 10y agoThe pathological case is the same (fill up publisher's pipes -> no publishing), but by giving clients flexibility on how to retrieve, they can set their own policy for how to augment this. Some possible general alternatives: - Wait to retrieve from publisher directly, never from third party cloud services - Ask friends, if this conforms to their privacy goals. Perhaps via store-and-forward mix. - Ask public altruistic peers. - Ask for-profit "cache providers". - Retrieve from multiple independent cloud service(s) using a technique such as PIR