I have found you were able to implement remote admin mode that is nice.
While testing i have found some unclear moments:
Even nodes in one room, it seems message about remote requesting stays for a long time before status messages appears about config reading.
Sometimes it says about timeout or even stays there on screen.
Why that so, and how can we cancel it, it seems esc doesn't work here.
Why it reads all the configs and not partially as app do?
It seems fine for stable connection, but when node is under 2-3 hops it seems hard to read everything in one time.
I have found you were able to implement remote admin mode that is nice.
While testing i have found some unclear moments:
1. Even nodes in one room, it seems message about remote requesting stays for a long time before status messages appears about config reading.
Sometimes it says about timeout or even stays there on screen.
Why that so, and how can we cancel it, it seems esc doesn't work here.
2. Why it reads all the configs and not partially as app do?
It seems fine for stable connection, but when node is under 2-3 hops it seems hard to read everything in one time.
<!-- github-sync-id:4977918062 -->
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.
I have found you were able to implement remote admin mode that is nice.
While testing i have found some unclear moments:
Even nodes in one room, it seems message about remote requesting stays for a long time before status messages appears about config reading.
Sometimes it says about timeout or even stays there on screen.
Why that so, and how can we cancel it, it seems esc doesn't work here.
Why it reads all the configs and not partially as app do?
It seems fine for stable connection, but when node is under 2-3 hops it seems hard to read everything in one time.
a cancel option would be good
yeah, whoops
@mesb1 great ideas!
043418bfde7d2092e25f