Q: Jörg Ott: Distributed/Disconnected application – how well does it work with Kademlia (connected)?
- A: Current version of IPFS is not directly supporting offline comms. There is interest in IPFS community to support offline communication, but this will not use the DHT as the content routing infrastructure
Q: Jörg Ott: in non-local network, with occasional connectivity – how to differentiate failure from longer disconnection periods?
- A: Provider Records have to be sent periodically. You could still provide content locally (e.g., via Bluetooth) – would be built on top of libp2p
Q: Jörg Ott: how to manage ID space?
- A: The PeerID space will not be managed in the same way as in the DHT. Offline communication will have to have different techniques to manage and connect peers. These techniques are not clear at this point – deferred to offline discussion
Q: Dirk Kutscher: real-time interactive?
- A: The main focus of IPFS at this point is content sharing, but there are several other use-cases that it has been used for. For instance, PeerPad is a real-time, P2P collaborative editor that does not use or depend on any central server. Some of these application are (or can be) supported by an efficient PubSub protocol, called goosipsub. Details on gossipsub can be found here: https://github.com/libp2p/specs/tree/master/pubsub/gossipsub