PageKite is interesting - how do you mitigate the risk of security vulnerabilities that could exist by running on a potentially unpatched machine that you use for everything else (i.e. your typical PC)?
Your personal IP address is not exposed, so you "only" have to worry about the security of the HTTP server itself.
How good or bad that is depends on what you are doing. For someone demoing static files (e.g. a web designer), running a mature HTTP server like Apache in static-only mode is almost entirely without risk.
I am also planning to add some access controls to PageKite itself, so only authenticated users' traffic is passed through to the HTTP server, but that's just vapour at the moment. :-)
How good or bad that is depends on what you are doing. For someone demoing static files (e.g. a web designer), running a mature HTTP server like Apache in static-only mode is almost entirely without risk.
I am also planning to add some access controls to PageKite itself, so only authenticated users' traffic is passed through to the HTTP server, but that's just vapour at the moment. :-)