Comment by ssl-3
1 month ago
FidoNet has a lot of it solved, for sure. But doesn't it rely upon pre-configured paths between nodes in order to handle message routing?
If so, then: Wouldn't it fall down completely when operating in the ever-shifting and inherently disorganized environment that a sea of pocket supercomputers represents?
I don’t take concepts as a 'full package'. I evaluate what is worth taking based on the requirements. The brilliant part of FidoNet is the asynchronous persistence.
In a 'sea of supercomputers,' a real-time mesh (like Bluetooth) fails because it requires an end-to-end path right now. Store-and-Forward allows a node to hold a message until it 'sees' any valid peer, turning every 'meat-bot' into a mobile post office.
My main concern with this entire discussion is the reliance on Bluetooth to achieve the result.
If we truly want to build a free and open intercommunications system, we must put all ideas on the table, establish clear targets (a doomsday system or inviting a friend for a drink), and evaluate what is truly available versus what is not.
Only from that foundation can we begin to define a project that survives the real world.
Yes. There's a lot of things to work out.
Here's one scenario:
Node A has a message to send to node H, but A is disconnected (no peers). Node A stores this message for eventual delivery.
Eventually, node K (ie "any valid peer") appears. Node A gives them the message that is intended for node H and rinses its hands of it.
Does node K's possession of this message actually improve the odds of node H ever receiving the message?
In theory, yes. There are now two nodes with the message for H.
In practice? A and H might live in the town and K might be just visiting for business, they might never come back.
1 reply →