Can we think about how to establish some message storage within the "mesh" until a node comes back "online"? Use case would be distributing information for nodes or even groups although they are temporarily offline, such as out of reach, no power or i.e. in emcomm/off grid situations, running on a lean power budget. An implementation could work similar to JS8Call, where one "online" node A is advised by a specific message format to save a message for later retrieval by another node B. As node B comes back online, it ask for "any message for me" and then gets a message delivered by node A - this would likely even work across the mesh, provided only that the retrieval request from node B reaches node A and the answer is delivered vice versa.
Can we think about how to establish some message storage within the "mesh" until a node comes back "online"? Use case would be distributing information for nodes or even groups although they are temporarily offline, such as out of reach, no power or i.e. in emcomm/off grid situations, running on a lean power budget. An implementation could work similar to JS8Call, where one "online" node A is advised by a specific message format to save a message for later retrieval by another node B. As node B comes back online, it ask for "any message for me" and then gets a message delivered by node A - this would likely even work across the mesh, provided only that the retrieval request from node B reaches node A and the answer is delivered vice versa.