So, you found the site
If you’re here, you found it. Have a look around. It don’t cost nothing. Leave a comment or ping something. Gotta check out the bugs.
If you’re here, you found it. Have a look around. It don’t cost nothing. Leave a comment or ping something. Gotta check out the bugs.
Remember, I do this to entertain me, not you.
Uncle Pays the Bills
Find Local
|
June 16th, 2004 at 6:47 pm
Well, since you made it so easy to find. I sometimes contemplate switching to WordPress — just don’t want to do the work yet. But yeah, the advantages to having a completely database driven site are many.
Only glitch so far (which is at your old site too) is that it’s wider than my browser window. Probably a stylesheet definition specifying something using an absolute pixel width.
I’ll reference something … see if pingbacks work.
June 16th, 2004 at 6:49 pm
And, the “say it” button openned another browser window. Uneccessary, don’cha think? (But then I always hate it when somebody decides to open something in a new browser window.) Still.
June 16th, 2004 at 6:54 pm
Ah, the templates all have target = _blank. GOod catch
June 16th, 2004 at 6:54 pm
Testing for new pop up
June 16th, 2004 at 7:03 pm
So, do we officially update our bookmarks and blogrolls yet?
June 16th, 2004 at 7:50 pm
Nah. Gonna move this to the old url.
June 17th, 2004 at 2:19 am
No updating necessary.
June 17th, 2004 at 4:49 am
Nice. Transparent conversion, too. Just how it should work.
June 17th, 2004 at 4:49 am
Oh, comments work a lot faster, too.
June 17th, 2004 at 5:22 am
Another moved to Word Press
Says Uncle, with some help from yours truly, has moved from MT to WordPress. Seems he got a bit tired of 45 minute rebuilds. Can’t say I blame him!
June 17th, 2004 at 7:46 am
Just so you know, the difference between the MT and PHP solution is in their approaches to scale. MT generates static documents that take very little effort for the web server to deliver. This means that it spends all of the time building your site up-front, when a change is made. WordPress doesn’t spend any time up-front. Instead it builds the pages on demand. I’m not familiar with WordPress’ caching strategy, but what this amounts to is that the 45 minutes of assembly time you see now is spread out over the requests. The upside is that changes are immediate. The downside is that if you get significant traffic, the web server might not be able to keep up with requests while it reassembles pages for each page hit.
The good news is that most of your content is probably infrequently accessed, while only the top 10 or so draw all of the attention.