The next step would be exchanging messages via NFC.
E.g. say for a p2p-twitter app, users A and B go into the exchange with their own versions of the global p2p-twitter feed, and exit the exchange with a merged version.
You could do federated, store-and-forward direct messaging, too. We already have a protocol for a very similar use-case: SMTP. :) Of course, with a sometimes-offline P2P mesh you usually don't know if any given hop decreases the distance to the destination.
You'd probably end up just merging all existing messages, so that everyone has everyone elses "email", and filter out the messages belonging to you via asymmetric encryption. So it's just an application of the above p2p-twitter thing. Public messages could be unencrypted.
I think some blockchain-based messaging systems work in a similar way, since there everybody has everybody elses messages per definition. Maybe a blockchain-based protocol is a good fit anyway, probably not though since I'm not sure how it would do the merge(A,B) function.
There were also systems designed for the BBS days that expected to have zero connectivity most of the time. They would dial other computers periodically and exchange data. e.g. http://en.wikipedia.org/wiki/FidoNet
E.g. say for a p2p-twitter app, users A and B go into the exchange with their own versions of the global p2p-twitter feed, and exit the exchange with a merged version.
You could do federated, store-and-forward direct messaging, too. We already have a protocol for a very similar use-case: SMTP. :) Of course, with a sometimes-offline P2P mesh you usually don't know if any given hop decreases the distance to the destination.
You'd probably end up just merging all existing messages, so that everyone has everyone elses "email", and filter out the messages belonging to you via asymmetric encryption. So it's just an application of the above p2p-twitter thing. Public messages could be unencrypted.
I think some blockchain-based messaging systems work in a similar way, since there everybody has everybody elses messages per definition. Maybe a blockchain-based protocol is a good fit anyway, probably not though since I'm not sure how it would do the merge(A,B) function.