I'm an openKapow novice.  I joined a while ago, but still haven't played with openKapow much or seen all the demos yet.  I'm curious how openKapow handles security.  (Or does it?)  The idea of putting a custom robot out onto a shared site just doesn't sound secure.  Is openKapow intended only for open, ...

HotmailClip.robot Web Clip robot that clips Hotmail to only show the most essential funtionality.

This demo illustrates how clipping robots can be used to clip content and functionality from existing webpages and reuse it in gadget based interfaces. We are using the hotmail web interface and clips it into a Google Gadget to display on a personalized Google page. The robots also shows and example of parsing ...

Let you see your hotmail inbox in a Google Gadget on your personalized Google startpage. This is done by using a Web Clip robot on openkapow. In the Google Gadget you can read your hotmail, respond to mails and send new mails.    This is a demo of openkapow's capability to clip and transform content from ...

If the traffic between your robot (on the openkapow server) and the web site it is interacting with is encrypted or not depends on if you are using HTTP or HTTPS to interact with those sites. If your robot is using HTTPS in all URLs in Load Page steps etc, then all the traffic between the robot and the site is encrypted. Basically it is the same ...

Thanks for your quick answer! So using https in the robot URL will use SSL to encrypt the traffic from the client (my browser for example) to the openkapow server that executes my robot. But what about the traffic from the robot to the web sites it logs into? The whole thing must use https to be secure.

Just use https to call your robots instead of http. For example: https://service.openkapow.com/Andreas/addtodotobasecamprest.rest?...  It is that simple.    

I am not too keen on calling robots using plain HTTP since I plan to do robots that will use usernames and passwords to login to different sites. Can I use HTTPs instead somehow?