Mike N8OOU here with a general Kiwiclientd usage question. A brief background first. I operate two FCC Part15 QRSS beacons that run 24/7. I have been working on modifying the kiwiclientd.py program to turn it into a remote kiwi qrss grabber. I have it working and have been testing on various kiwisdr's. Not many people monitor and provide signal reports in these bands , so this gives me the capability to monitor my beacons from remote locations.
A new discussion that has just come up is concerning for me in using this process. Please refer to this thread;
In my testing I have used a couple kiwi receivers, and I contacted the owners to make them aware of my activity, and get their ok to use their machines. That initial testing was more frequent than a normal usage pattern. I normally have my callsign specified in the user field, but the program does default to "kiwiclientd". I had not planned to ask permission from every kiwi owner in the future, I assumed the owner granted that permission automatically by making their kiwi publicly access-able. I am to the development stage where I will be accessing remote kiwi's to learn where my beacons are propagating to.
This thread makes me concerned that my grabber will be viewed as an intruder and my ip possibly blacklisted. This seems to me that this is a legitimate use of the kiwi network. I can perform the same access thru a browser, and use the same resources on the kiwi. Accessing a kiwi either way will use a kiwi slot and if all slots are filled, prevent local access.
My grabber process is still in development and additional features still need to be added so it is not publicly available. I am developing it for my personal benefit in the operation of my beacons, and not as a commercial product. It may be of benefit to other beacon operators.
I am posting this to document another possible use of the network of KiwiSDR's like the TDOA or WSPR services. If I access your kiwi will I be welcomed, or banned?