Definitivelly, commander needs better documentation and a special note about security. However, if you currently *only* install commander without prior reading the documentation, you will see soon that commander won't work unless you setup some preferences, specially a list of authorized email addresses and/or domains. As you see, the "sendMeDocs.scpt" module will return the user the requested archives from the client computer. But "sendMeDocs.scpt" will be executed only if the order comes from an authorized mail account, and will send back the requested information only to such address. Well, I'll add a "security" entry into the docs very soon!

To begin with, I looked at this then threw it away. With the poor and scattered documentation and sketchy information, I did get the sense that it was more for a Unix Geek or a developer than an end user. I also got the impression that it had the possibility of opening up a freeway to the outside world through which someone on the outside with this tool and knowledge could gain access to my machine. So I chose not to install and try it. With some cleaning up and more information about it that an end user could understand this product may have some potential, provided the security issues are addressed. However, in its current form, I do not believe it is quite ready for a wide distribution and general use. It currently does not seem to be a tool for the plug and play user.