[Feature Request]: Clearly delineated message types

[ford-jones]

Prerequisites

• [x] I have searched existing issues to ensure this feature hasn't already been requested
• [x] I have checked the documentation to verify this feature doesn't already exist

Problem Statement

Currently there is no way to tell whether a message in the primary channel was received via MQTT or LoRa. In areas where the mesh is spread thinly, having the ability to tell that a message was actually received over LoRa instead of through the MQTT module would make it a lot easier to coordinate with other nodes in your localised area.

Proposed Solution

Create an icon to display next to the message sender's name that indicates the message was sent over LoRa as opposed to MQTT . (e.g. something like 📶)

Current Alternatives

• Checking whether a node has the MQTT module enabled with the python cli (e.g. the node list as displayed by meshtastic --info reveals the values of the lastHeard and viaMqtt properties)
• Looking for the node in the various mesh-maps
• Asking the person directly if I suspect they're a local

Importance

Nice to have

[philon-]

With Meshtastic Protobufs >= 2.7.5 we have the TransportMechanism enum in MeshPacket we can use for this

[domusonline]

I opened a duplicate for this one. Just want to add that the feature already exists for Android:

https://github.com/meshtastic/Meshtastic-Android/issues/2028

Just hoping to maintain some consistency around the behavior if feasible.

[roberthadow]

As you approach the design task, please consider deeply each time you add a new icon. While an icon uses the minimum amount of real estate, asking a new user to learn a score or two icons is not productive.