Well I wouldn't copy and paste the code into your apps, but it can be useful for educational purposes.

Well yes and no. A good developer will know to read the code and understand it first. A bad developer might cut and paste the code, but they might do that with MSDN examples and other samples.

Bad developers will do bad things. There's no stopping that. But good developers will use tools effectively and do the right thing.

Interesting! I like that approach. The reason I use an array is because it appears to be the convention. If you follow the convention, it just works.

However, with your approach, if I follow the convention, I'll get a runtime error. But, I'll see the BaseState property and hopefully figure it out and do it the right way. That's a real nice benefit of your approach. It's strongly typed and forces me to do the right thing. Well done!

Many of these web utilities are useful for web development in general. Such as streamlining the bandwidth used by a website. Etc...

Better yet, who tests the tester?

Some ideas for minor improvements:

1. Search
2. A javascript kick-it box like digg and reddit have. The kind where a user doesn't t have to leave your site to kick your site (assuming it's already been submitted).
3. Gravatars for submitters and comments

Umm.. that's it.

Gavin, I think Open Sourcing the code is a great idea! When I visit the site, I sometimes want to make small tweaks to make the site look a little cleaner or more polished.

Heck, I could see myself adding code from Subtext into here and vice versa, where it made sense.

In any case, adding ads is also a good idea. Done well, it can cover your hosting costs and then some. Perhaps put some text links right above or below the comment box. Keep up the good work.

Hello, but Paul Haack is my dad's name. My name is Phil Haack.