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
The MeshChat software is sensitive to too much time change between the nodes and as a result will cause the message database not to be synchronized between nodes. This has been noted several times in the kn6plv/meshchat issues (no longer accessible).
The proposal is to have the API updated to also transfer the timestamp from the instance running MeshChat so that it can be displayed on the status page.
Note: this may become a breaking change and there will need to be investigation into if the v1.x or v2.x code bases will have a problem with adding the timestamp into the API.
The text was updated successfully, but these errors were encountered:
Initial inspection of the status.js code does indicate that adding the timestamp information to the status API will not have any backwards compatibility issues. Will need to update the API version references, so all API changes should be coordinated to be in the same release.
Contact Details
No response
Enhancement Type
API improvements
What is your idea or what can be improved?
The MeshChat software is sensitive to too much time change between the nodes and as a result will cause the message database not to be synchronized between nodes. This has been noted several times in the kn6plv/meshchat issues (no longer accessible).
The proposal is to have the API updated to also transfer the timestamp from the instance running MeshChat so that it can be displayed on the status page.
Note: this may become a breaking change and there will need to be investigation into if the
v1.x
orv2.x
code bases will have a problem with adding the timestamp into the API.The text was updated successfully, but these errors were encountered: