When starting the original meshcore.app (on MacOS) after using of Remote-Terminal-for-MeshCore, most of the favorited repeaters are missing in the contact list, only those recently heard while using Remote-Terminal-for-MeshCore remain.
When starting the original meshcore.app (on MacOS) after using of Remote-Terminal-for-MeshCore, most of the favorited repeaters are missing in the contact list, only those recently heard while using Remote-Terminal-for-MeshCore remain.
<!-- github-sync-id:4208058369 -->
Yes, that is expected behavior. RemoteTerm handles 100% of the processing and storage (hence so you can exceed the limits of the radio) but is intended as a semi-permanent installation because it takes over management of the radio and contact/channel storage. Sorry if this was unexpected; I could probably stand to make a slightly clearer warning in the Readme.
Yes, that is expected behavior. RemoteTerm handles 100% of the processing and storage (hence so you can exceed the limits of the radio) but is intended as a semi-permanent installation because it takes over management of the radio and contact/channel storage. Sorry if this was unexpected; I could probably stand to make a slightly clearer warning in the Readme.
<!-- github-comment-id:4189249721 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When starting the original meshcore.app (on MacOS) after using of Remote-Terminal-for-MeshCore, most of the favorited repeaters are missing in the contact list, only those recently heard while using Remote-Terminal-for-MeshCore remain.
Yes, that is expected behavior. RemoteTerm handles 100% of the processing and storage (hence so you can exceed the limits of the radio) but is intended as a semi-permanent installation because it takes over management of the radio and contact/channel storage. Sorry if this was unexpected; I could probably stand to make a slightly clearer warning in the Readme.
Alrighty I've added a clearer warning about that to the readme. Sorry if that caught you off guard!
No problem, thanks for the explanation