[Feature Request]: Ability to add custom label to long/short name.

[gbdabomb]

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

Node short names and long names are often maintained with a default or cryptic name to provide privacy in a Primary Channel Unencrypted context, but this naming may not include the relevant personal context that I have as a user connecting with friends and family. I’d like a way to allow me to quickly identify which node represents the person I want to message.

Proposed Solution

Offer the ability to maintain additional locally stored contact information such as an alias name for any given node in the NodeDB. This info is not shared over Meshtastic with the greater community, it should be kept locally with the NodeDB as a personal Alias. This would allow me to add a “friendly” name to Nodes in my NodeDB, simplifying the user experience for a casual user. This could be further implemented to allow a linking to a contact object from a contacts app on the device being used.

For example, I could alias a node ‘Meshtastic xb7n’ as ‘Jane Smith’ or equally as valid, ‘Mom’, to make it clear to me who I am messaging.

Current Alternatives

Users are forced to memorize and interpret the naming of nodes based on the convention set by the Node owner. Other messaging also allows for consideration of the needs viewed from the messaging partner’s point of view.

Importance

Nice to have

Additional Context

Node Alias, if maintained, would supersede the node Long Name in the User Interface.

[b8b8]

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

[github-actions[bot]]

This issue is stale because it has been open for 60 days with no activity.

[danditomaso]

bump