Something is going wrong with the code that parses links. See
Ouise "Natter: 2 Good 2 B 4 Gotten!" Oct 8, 2002 7:51:59 pm EDT
for an example. I think this only happens when the poster enters the <a href=""> manually.
[Testing: Does this mess up? Nope. Maybe this?]
I think the problem was that I forgot to close the quotation marks around the URL the first two or three times I tried to get that post right. I didn't notice until I tried the type-everything-out-again method of fixing it.
On the archives, I've threadsucked everything that's in the attic, and I'll try to get most of it up to the archives page this weekend. I'm still bugged by the fact that the threadsucks are missing posts. It's a random thing, probably caused by that banner ad that WX puts at the bottom of random pages, but the upshot is that there are posts missing. I have an idea about how to improve the threadsuck program, but I didn't get a chance to mention it to John before he left on holiday.
As an alternative, I tried accessing the WX forums using the newsreader in Mozilla, and was able to download the Contingency Plan and Projects that way, but each forum is a single file containing all the posts in all the threads. I ran into a snag with that method, too, because it refuses to download NAFDA for me. I freely admit that I am a newbie when it comes to NNTP, so if anyone has any suggestions, I'd be happy to hear them.
Why did the "0 new" go away? Did people not like it?
I know that I didn't like "0 new". I think that having "x new" appear only when there are new posts will be especially helpful to make the Beep Me and Press threads stand out when there are new items.
I didn't know WX did NNTP, cool.
I could write a Perl script to do the threadsuck using NNTP.