You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: