[Feature Request]: Store and Forward DMs

[overkillthemighty]

Platform

Cross-Platform

Description

I was pondering the usefulness of store and Forward, and I see the application as it is, but it is only useful for a specified channel. Another "channel" that I feel has been overlooked is DMs. I keep a router_late over my house and it would be amazing if I could register the public key of my EDC with it and have it store any DMs directed at me, and release them to me when requested.

[RCGV1]

With PKI we cannot tell if it's a dm or other encrypted directed message

[overkillthemighty]

Could we register our private with the node we want to do S&F so it can decrypt? This is a process you would do with a node you trust and is arguably more secure than your EDC.

[shalberd]

@thebentern @jp-bennett

Hi all, can store & forward only be used with Device Role Router, or also with role Router_Late?
I am asking because we have a community member that currently uses Router role due to his affinity for S&F, but
in the code here
https://github.com/meshtastic/firmware/blob/master/src/mesh/Router.cpp#L90

is_router is defined as either of the 3 infra node roles ...

I guess that is a different feature, 0-cost-hops, right?

Cause in the S&F Store and Forward Code section, I see
https://github.com/meshtastic/firmware/blob/master/src/modules/StoreForwardModule.cpp#L593
only Router mentioned.
Why e.g. not Router_Late?

In our experience, I know, special mountain node and dense node situation, Router_Late plays much better with overall mesh behavior than Router, so we'd like to give S&F aficionados a reason to switch over to Router_Late, which I guess currently, they cannot.