meaning of the icon in a received message?

[carl-mempool]

In this received message (see image) there is an icon and the number "2". What does this mean? Is it documented anywhere? I cannot find where the icons in a received message are documented anywhere.
Using my image editor I captured it and blew it up big and I guess it might be a bunny. In which case maybe what I am being told is that it required two hops for the message to reach me.

[roberthadow]

Hello @carl-mempool --

I earlier suggested a guide to iconography in Meshtastic. Some icons are not intuitive. Different user interfaces use different icons for the same condition.

I understand why icons are so atractive. Instead of a twenty character message, an icon only takes one character space. What is inturitve to the developer may not be obvious to the user. A guide would help everyone...and encourage similar use across the various UIs-- on the device, the Web, Android or IOS.

The specific icon you included is a rabbit. The standard use of a rabbit icon indicates high speed. It contrasts with the turtle, which indicates retarded throttle. Take a peak in the cab of any piece of heavy equipment, whether made in the U.S., Europe, or Asia.

Robert

[roberthadow]

Hello @carl-mempool --

There is a more-or-less complete explanation of Android message icons here: https://meshtastic.org/docs/software/android/usage/

• UNKNOWN: Not known for this message.
• RECEIVED: Message delivered and acknowledged by the intended node.
• QUEUED: Message waiting to be sent to the mesh as soon as the device connects.
• ENROUTE: Message delivered to the radio, but no ACK or NAK received yet.
• DELIVERED: Message successfully delivered and acknowledged to the mesh (ACK received).
• ERROR: Message not delivered (NAK received or other error).

[carl-mempool]

Thank you for your comment. Yes, in my original posting I ought to have mentioned that I already knew about that place where the sent-message icons are explained. But that place says nothing about what I was asking about, namely a received-message icon along with a numeral. Again, thank you.

[roberthadow]

Hello @carl-mempool --

Here is my suggestion about how the project should proceed.

I suggest that we create a series of Meshtastic documentation pages with similar content and identical look and feel that describe icons and actions for three different user interfaces:

• Web Application Usage
• [Android Application Usage](Android Application Usage) (update as required)
• Apple Application Usage (update existing)
• -- and to extent it makes sense, Python CLI Application Usage

One side effect will be this: When we compare the documents, we'll feel compelled to standardize the use of icons and their explanations.