Closed GUVWAF closed 7 months ago
@GUVWAF what do you think of having both a text_broadcast
and text_direct
oneOf added?
this way we can separate broadcasts from direct messages like the Delayed
field was designed (below): text_broadcast
we replace the to
with the broadcast node number; text_direct
is a DM for us.
we would then need to pick the oneOf based on packetHistoryTXQueue[packetHistory_index].to
here
Good idea. Or should we add two RequestResponse tags instead? One for text_direct
and one for text_broadcast
? Currently I'm using the UNSET
.
Good idea. Or should we add two RequestResponse tags instead? One for
text_direct
and one fortext_broadcast
? Currently I'm using theUNSET
.
commented on https://github.com/meshtastic/firmware/pull/3194#issuecomment-1937766213
This will replace the currently unused "empty" variant of the StoreForward message to "text", such that clients know how to handle the history from the server. Technically a breaking change, but the "empty" variant was not used in the firmware.
Also updated some of the comments of other fields.