Here's a tip if you make weblog software: if you intend normal people to use it, and you want it to bake the pages and fling them to a server across the net, and you want it to be efficient and repush every page (such as for a template change) as little as possible, you're in a tight spot and should reconsider one of the three. It's far and away the #1 conceptual misunderstanding with Radio UserLand. I don't know if it's because it's not explained well (where would they explain it if users don't read manuals?) but too many questions on the discussion group are asked that are answered with, "Radio only pushes changed pages when it thinks they've changed, and [the thing you did] doesn't count." POT.py would actually reupstream everything if I changed a template, but then, I don't leave it running--I use the -1 option exclusively.
Comments
comment
Which reminds of the time that I was playing with POT.py and (foolishly) added the published date and time, down to the second, to my main page. I saw it publish once and then switched to another window. When I came in the next morning I noticed that it had been publishing constantly all night. Ooops!
comment
Quite oops! I think I was going to make a variable so you could
ifanything like that out, but ended up using just the file ctime and mtime instead of having a publish time.