Dare asked a good question in the comments below. What is the license for BlogX? I put a copyright at the top of each file, but I didn't think about enough of what I really want here. I guess I'm looking for a license that provides the following:

• Free (no charge) use by anyone with or without modification (free)
• Anyone using the source or binaries I provide must hold me harmless (no warranties)
• Any product that uses the source or binaries can use any license they wish (no viral licensing)
• No limitations on usage in acedemic or commercial spaces (for your use anywhere)

Given that it only took me ~15 hours of coding, I can't imagine there is all that much IP in the source, but I don't want this to come around and bite me in the ass. :)

Any suggestions on a good license? GPL won't work because of the viral stuff... MS Shared Source won't work because of the acedemic limitations... other suggestions?

10:32:26 AM    comment []

Gary makes an interesting point... at a minimum why don't I use RSS 2.0 as the native XML format for my blogging tool... hmm...

At this point i'm convinced that the "per-day" or "per-entry" debate is largely moot... either way I'll end up with a cache for the other direction...

3:20:52 AM    comment []

I'm not happy with the source, it's mostly slapped together on various late nights, but I figure there is nothing like a little peer review to clean your act you. You can download the source and binaries (one zip).

There are no instructions, almost no comments, no support, and no warrenties on any of this - it works on my machine, and that's all I can say :)

Please post feedback in the comments for this, or, of course, on your blog! :)

2:56:24 AM    comment []

More web frontend work... referrers are now being tracked. I just write out the UrlReferrer and Url from the request when pages are hit. This seems like the wrong model... is there a better way to track referrers?

Also did some minor HTML cleanup (more divs, etc.) and also added support for navigation links like Radio has.

2:46:35 AM    comment []

One of the designs that I'm not happy with is how i'm handling file path resolving. Right now I've got a static (re: global) delegate that is called to resolve files. This allows me to map this to a Server.MapPath in the web case, and a Path.Combine on the client. The problem is that the "map" ends up being per app domain - which works great for ASP.NET, but sucks for WinForms... At this point I'm not going to rewrite it, but I'm just not happy with the design.

Note I've created a BlogX category for tracking progress and comments on this specifically.

2:42:12 AM    comment []