Although I've done various bits of testing on 350.com, I'm usually responsible for layout of the various bits of the user interface, so most of my testing consisted of "does this chunk of HTML render correctly in IE6".

I've finally found time to make a small website. In the process of course found various minor bugs, and missing features, that would make it a better, and easier tool, for building websites.

Building an affiliate type system I found that many of the features, like drag resizing of photos in a web page aren't available. Perhaps we need an affiliate system integrated to fix that.

There are too many things we need to integrate, and too little time, I now see more clearly why Google created Gadgets as a way of getting third parties to integrate features into both your home search page, and the Google site builder.

The first thing I wrote for 350.com was a server side reimplementation of Google gadgets, so that your own web server (if it runs Perl) can deliver Google gadgets, with customizable settings, without involving Google hardware in any way, and without the usual Google wrapper (that you get if you embed a Google gadget, from Google, in your own website). That project seems to have been shelved for the moment, but perhaps it is time to dust it off. Of course midway through writing it Google released a major update to the Google gadgets specification, introducing all sorts of complex features that we didn't have time to implement. Hosting the Google server side functionality means effectively becoming an open relay (admittedly with arbitrary caching) as the Gadgets have to fetch themselves, and other content, but presumably it is reasonably safe to do that if you cache at least as aggressively as Google, since then abusers will abuse Google's resources and not yours.