Replies: 1 comment
|
@attermann I have added your rns link idea for upcoming v4.8.0 and a plugin system. https://github.com/Quad4-Software/MeshChatX/blob/dev/docs/en/rns-link-api.md https://github.com/Quad4-Software/MeshChatX/blob/dev/docs/en/plugins.md Its early and might change, let me know if this is what you have in mind. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I would love to integrate some microReticulum transport node provisioning/management features with MeshChatX to make it easier to track and manage remote transport nodes. There are at least a couple of ways to do this that come to mind and I was hoping to get your input about which make the most sense.
First is to interface directly with the exposed MeshChatX API (via REST and/or WS) from another web app and just use it as an RNS transport. This is the path I'm currently on, but it has required adding some more generic Link management features to the existing MeshChatX API, so hopefully you're open to considering accepting a PR to add this to the official dist.
Second is to embed a microReticulum transport node management interface directly in MeshChatX. I haven't really explored this yet, but a tool like this would make it super convenient to manage remote transport nodes. Curious if you'd consider adding a tool like this to the official dist as well, or if you've considered a general plug-in style interface for adding tools to MeshChatX.
Also out of curiosity, have you considered rolling this REST/WS interface into RNS itself? I know that's probably a long-shot, but it would really nice to have a universal interface to RNS that does not require Python as a shim.
Looking forward to hearing back and exploring this further.
All reactions