3 ms·
> A crappy computer, no; a crappy server, yes. The available network is part of a server. A URL that points to a machine that can't be accessed whenever the own
by lgierth 9y ago
> A crappy computer, no; a crappy server, yes. The available network is part of a server. A URL that points to a machine that can't be accessed whenever the owner goes into a tunnel, is a URL nobody will link to.
This is one of the very points that IPFS tries to address: decoupling content from location, so that additional copies of the same content in different locations of the network can actually strengthen the content's availability, instead of being non-addressable and thus wasted.
- derefr 9y agoWorks if you're serving a static webpage; doesn't work if you're serving, say, a private chatroom. This is what decentralized execution environments like Ethereum seek to solve, but running an Ethereum node on your phone is not the same thing as actually serving a private chatroom from your phone. In fact, Ethereum is much closer to the cloudlet side of the spectrum of solutions, insofar as your client (the phone) is just sending commands to a computer "somewhere else" (in this case, ~everywhere) that then acts as the server.
- lgierth 9y agoWorks with IPFS if you use Pubsub, cryptographic capabilities, and CRDTs :) Check out PeerPad: https://peerpad.net https://peerpad.net edit: what I also meant to say is, a chat room doesn't need computation (although there certainly use cases that do)