Back to matrix

F31-MT: No

Rationale

The selected Meshtastic CLIENT composition explicitly disables Store & Forward. Ordinary mesh forwarding and transient packet retention do not provide another remote requester with a cache-serving interface for reusable content. The optional Store & Forward module has a history request/response service, but it is not active in this composition.

Assessment method

Primary specification and pinned code review; no runtime experiment

Source context

Pinned cjdns source, BP forwarding and Meshtastic store-forward

Outstanding qualification

The optional module can return retained text history within a requested time window and configured limits; its existence is documented rather than attributed to the disabled profile. A local phone/client history cache and forwarding or duplicate-suppression buffers are not, by themselves, a cross-requester mesh service. Selecting the module would require reassessing its roles, authorization, retention and serving rules; no universal claim against Meshtastic content reuse is made.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.