P2P is not really solved. Not to the true satisfaction.
For example, there are tens of millions of images uploaded to Twitter daily. They all have to be stored, and then retrieved for nearly arbitrary tweets and arbitrary users.
All this content has to be stored somewhere and retrieved fast enough to be useable.
This comment is underrated. The theory is solid but piped piper doesn't exist in reality. Striping content across the network is the way to go. STORJ apparently is working on it as is the Interplanetary internet idea. It reminds me of FidoNet back in the day.... The internet we have exists because of low latency networks.. the question is how do we maintain that illusion?
Because anyone who tried that got burned with child porn and the threat of real prison time.
p2p tech is fundamentally incompatible with American morals. You will never see a p2p based firm be successful in the US any more than you could have had the industrial revolution in Ancien Regime France.
Each user storing what they post doesn't really scale. If I have a 100kb image in a post that gets popular, then the following technical things are needed:
1) It needs to work reasonably fast when the suddenly popular post is seen by, say, 10000 people in a short time. My home uplink won't handle that.
2) It needs to work when my computer is turned off or disconnected from the internet.
3) (optional, but still important) People on the other side of the world should be able to get popular data from a cached copy that's physically closer, both for latency and bandwidth reasons.
"Store what you post" isn't sufficient, all that I post needs to be stored also by someone else (e.g. a CDN) - but that immediately rises all kinds of issues about liability. If only I am storing what I post, then the system can afford to not care if that image turns out to be child porn, but if someone else is storing what I post, then that's a problem for everyone.
Comments
P2P is not really solved. Not to the true satisfaction.
For example, there are tens of millions of images uploaded to Twitter daily. They all have to be stored, and then retrieved for nearly arbitrary tweets and arbitrary users.
All this content has to be stored somewhere and retrieved fast enough to be useable.
PiedPiper solved this
This comment is underrated. The theory is solid but piped piper doesn't exist in reality. Striping content across the network is the way to go. STORJ apparently is working on it as is the Interplanetary internet idea. It reminds me of FidoNet back in the day.... The internet we have exists because of low latency networks.. the question is how do we maintain that illusion?
https://www.wired.com/2017/06/pied-pipers-new-internet-isnt-...
Storing images in multiple, decentralized servers and making them available to arbitrary users instantly? Pretty sure that's a solved problem. </IMG>
Jeez man, most sites have trouble putting static text on a page without showing a spinner.
That’s for different reasons :)
I'm not sure they're as different as you might think.
I'm pretty sure no major service (petabyte+ scale) functions this way.
Because anyone who tried that got burned with child porn and the threat of real prison time.
p2p tech is fundamentally incompatible with American morals. You will never see a p2p based firm be successful in the US any more than you could have had the industrial revolution in Ancien Regime France.
If it's actually p2p, you don't need petabyte scale. You just need to store what you post, which for most people is megabyte-to-gigabyte scale.
Each user storing what they post doesn't really scale. If I have a 100kb image in a post that gets popular, then the following technical things are needed:
1) It needs to work reasonably fast when the suddenly popular post is seen by, say, 10000 people in a short time. My home uplink won't handle that.
2) It needs to work when my computer is turned off or disconnected from the internet.
3) (optional, but still important) People on the other side of the world should be able to get popular data from a cached copy that's physically closer, both for latency and bandwidth reasons.
"Store what you post" isn't sufficient, all that I post needs to be stored also by someone else (e.g. a CDN) - but that immediately rises all kinds of issues about liability. If only I am storing what I post, then the system can afford to not care if that image turns out to be child porn, but if someone else is storing what I post, then that's a problem for everyone.