Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: Add a Node/Node user status to one of the periodic broadcast packets #586

Open
Nestpebble opened this issue Sep 13, 2024 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@Nestpebble
Copy link

Platform

Cross-Platform

Description

Nodes would benefit from a "status" in the same way that other chat platforms have a user status, e.g. Available, Away, Busy, etc.

However, Meshtastic nodes can be in many more states than just the user, e.g. Currently Unattended, Totally Unattended, Autoresponder only, Answering Machine only, Store & Forward Server, etc.

Adding a suitable set of statuses to a node would also improve the out-of-the-box experience for new users, who would be able to see that although there is a mesh around them, none are attended at the moment.

As more complex status messages are involved, bandwidth consumption increases and so do basic concerns like security and passive surveillance. However, with a few carefully selected statuses, I think this might be a valuable addition to the overall system.

@Nestpebble Nestpebble added the enhancement New feature or request label Sep 13, 2024
@thebentern
Copy link
Contributor

This is a really interesting idea. I suppose it would live on User and could exist as a somewhat computed state at points, for instance receiving a text message would transition from a node we previously had as Away to Available, in addition to the user setting things explicitly

@thebentern thebentern self-assigned this Sep 14, 2024
@caveman99
Copy link
Member

please make that a bitfield, that way a node can have more than one status. :-)

@Nestpebble
Copy link
Author

I've just thought this could also be a place to put stationary/mobile, or at least permanent station/mobile resting/mobile moving.

@thebentern thebentern transferred this issue from meshtastic/firmware Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants