> Your grandmother would have to run her own node!
Imagine if she had to have her own USPS mailbox, or worse, if she had to setup and manage a globally visible server[1] on an incredibly complex circuit-switched telephony network. POTS telephone service used to be more complicated, but it quickly became very easy to setup and use because a lot of the complexity was successfully hidden behind various goods and services.
The same should be true for basic network, but true network software was only developed for professional or niche use cases because NAT severely damaged the network. Imagine if the telephone network was almost always "party lines"[2] in residential areas. Entire categories of telephone-related goods and services wouldn't have happened.
> as their available bandwidth slows to almost nothing!
That's why there used to be a lot of research into different types of multicast[3]
routing. We even see
> pay for it
Just like POTS.
> you would either ... or it'd turn
You're trying to apply examples from our current, highly centralized network services, when a truly decentralized Facebook would be very different, both as a service and the environment in which the service exists.
[1] where "server" is anything that listens for requests (in this case, the "called party")
Imagine if she had to have her own USPS mailbox, or worse, if she had to setup and manage a globally visible server[1] on an incredibly complex circuit-switched telephony network. POTS telephone service used to be more complicated, but it quickly became very easy to setup and use because a lot of the complexity was successfully hidden behind various goods and services.
The same should be true for basic network, but true network software was only developed for professional or niche use cases because NAT severely damaged the network. Imagine if the telephone network was almost always "party lines"[2] in residential areas. Entire categories of telephone-related goods and services wouldn't have happened.
> as their available bandwidth slows to almost nothing!
That's why there used to be a lot of research into different types of multicast[3] routing. We even see
> pay for it
Just like POTS.
> you would either ... or it'd turn
You're trying to apply examples from our current, highly centralized network services, when a truly decentralized Facebook would be very different, both as a service and the environment in which the service exists.
[1] where "server" is anything that listens for requests (in this case, the "called party")
[2] https://en.wikipedia.org/wiki/Party_line_%28telephony%29
[3] https://en.wikipedia.org/wiki/Multicast