New Functions #78

New Issue

2026-10-05T01:56:22+02:00

adam commented

2026-10-05 01:56:22 +02:00

Firstly, Thanks for this app. It is great. MQTT,packet analyze, python bots. Its server that i was looking for.
And i hope my suggestions will make them more even better...

Please consider add other usual Meshcore Tools, like Analyze noise floor ( important for debug in big cities) or just actual number. Same as Trace path on map. It can be done via buttons when we click on certain repeater or node on node map

Consider add multibytes pings and etc. Our city has already use 2bytehash all over the city and it is frustrating to view that app warns about collisions etc( even if i choose 2 or 3 byte in experimental settings)

Discover nearby repeaters... Its obvious that if we already know that repeater, it has his own name and even [AA] or [AAAA] or [AAAAAA] prefix, not only 64 hex public key.

I can set private Key and reboot, but i cant get private key for store it elsewhere

Finally, i think it will be a good idea to preparing to translation UI to several languages

Firstly, Thanks for this app. It is great. MQTT,packet analyze, python bots. Its server that i was looking for. And i hope my suggestions will make them more even better... Please consider add other usual Meshcore Tools, like Analyze noise floor ( important for debug in big cities) or just actual number. Same as Trace path on map. It can be done via buttons when we click on certain repeater or node on node map Consider add multibytes pings and etc. Our city has already use 2bytehash all over the city and it is frustrating to view that app warns about collisions etc( even if i choose 2 or 3 byte in experimental settings) Discover nearby repeaters... Its obvious that if we already know that repeater, it has his own name and even [AA] or [AAAA] or [AAAAAA] prefix, not only 64 hex public key. I can set private Key and reboot, but i cant get private key for store it elsewhere Finally, i think it will be a good idea to preparing to translation UI to several languages

adam closed this issue

2026-10-05 01:56:22 +02:00

adam commented

2026-10-05 01:56:23 +02:00

Ooh lots of requests! Glad that app has been serving you well. I'm going to include my thoughts on these below; generally some I'm on board with, some I'm not going to do right now, and some are not going to be done ever. For the first two categories, feel free to open separate issues, one per request. I'll eventually get to the first category, and am open to seeing the demand for the second.

Analyze noise floor

Reasonable; I can surface that in settings somewhere.

Trace path on map

I think for right now I'm going to keep the map as a visualization-only layer. I don't think I want to start overloading that display with commands right now. However, I'm open to an issue to gauge general demand.

add multibyte pings

Super reasonable; we should be reading the radio prefix mode and using that for pings. I'd even go so far as to call that a bug.

Discover nearby repeaters... Its obvious that if we already know that repeater, it has his own name

For sure; I can wire that up.

i cant get private key for store it elsewhere

Private key export will not be a feature I implement. I'm already uncomfortable with how we extract it and keep it in memory; I definitely don't want to make it any easier than it already is to dump out private keys. They should generally remain secret forever.

i think it will be a good idea to preparing to translation UI to several languages

I'm broadly open, but don't speak any other languages (and am definitely not paying for services; this project already takes up far too much of my life lol). If there are people that can commit to doing ongoing translation work, I'm open to adopting a translation framework, but this is a very, very low priority for me right now while we're focusing on active product dev.

So, thanks for the thoughts! Please make issues for at least the ones I've mentioned I'm willing to do now and I'll action them as I'm able.

Ooh lots of requests! Glad that app has been serving you well. I'm going to include my thoughts on these below; generally some I'm on board with, some I'm not going to do right now, and some are not going to be done ever. For the first two categories, feel free to open separate issues, one per request. I'll eventually get to the first category, and am open to seeing the demand for the second. > Analyze noise floor Reasonable; I can surface that in settings somewhere. > Trace path on map I think for right now I'm going to keep the map as a visualization-only layer. I don't think I want to start overloading that display with commands right now. However, I'm open to an issue to gauge general demand. > add multibyte pings Super reasonable; we should be reading the radio prefix mode and using that for pings. I'd even go so far as to call that a bug. > Discover nearby repeaters... Its obvious that if we already know that repeater, it has his own name For sure; I can wire that up. > i cant get private key for store it elsewhere Private key export will not be a feature I implement. I'm already uncomfortable with how we extract it and keep it in memory; I definitely don't want to make it any easier than it already is to dump out private keys. They should generally remain secret forever. > i think it will be a good idea to preparing to translation UI to several languages I'm broadly open, but don't speak any other languages (and am definitely not paying for services; this project already takes up far too much of my life lol). If there are people that can commit to doing ongoing translation work, I'm open to adopting a translation framework, but this is a very, very low priority for me right now while we're focusing on active product dev. So, thanks for the thoughts! Please make issues for at least the ones I've mentioned I'm willing to do now and I'll action them as I'm able.

adam commented

2026-10-05 01:56:23 +02:00

I've made issues for the ones I'm willing to do at some point 🙂 I'll keep this open for your response/thoughts but otherwise those will supersede this issue.

I've made issues for the ones I'm willing to do at some point 🙂 I'll keep this open for your response/thoughts but otherwise those will supersede this issue.

adam commented

2026-10-05 01:56:24 +02:00

Actually, I'm going to close this one. Feel free to open issues for the others in accordance with what I mentioned; for the ones I haven't ruled out, issues are welcome.

Actually, I'm going to close this one. Feel free to open issues for the others in accordance with what I mentioned; for the ones I haven't ruled out, issues are welcome.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#78