I think some people might be a little wary of storing some of their rig information on a third party site.
Understandable I guess. But is it really any different to say public pool information on a mining pool like users hashrates and what not. There isn't any private or sensitive information stored by the site or the remote app you install on your local network. A benefit of the remote app is that it removes the need to publicly port forward the miners to the outside world (and having to open up multiple ports). Additionally, the remote app can only do what you've given it access to do via the cgminer api which a user has to set on the miners that they want to collect data from. Currently it doesn't use elevated API privs as it does not make any changes to the miners. I thought it might be useful to be able to remote control them but I was thinking that people may have a problem with this. Thus the information sent to the web server is just what you see on cgminer and doesn't really represent anything overly sensitive in nature.
So far as releasing the source code I didn't have any plans to do it immediately as there is a bit of code cleanup and re-design on a few components I want to do before I check it into GitHub but don't see any problems with doing so. At this stage I was just trying to gauge whether or not there was actually any interest in a publicly hosted service for the community. I'm not trying to hide or sell anything to anyone so I have no problem being completely open and transparent. There's nothing in it for me other than providing a service to others that they may find useful...much like say pvoutput.org which is used by owners of pv solar systems to log, record and compare their electricity usage.
So far as a remote monitoring solutions go though I haven't seen anything that allows a user to get up and running within minutes and only requires installing one little light weight console application. I also have plenty more features planned.
Thanks for the feedback.
