I still don't know quite what a CVS repository does, but I do note that it's finished ahead of schedule. Yay Karl!

Not finished just yet. Testing. There will be bugs, permission issues, and other normal shake-out difficulties.

But it looks like we might make the schedule.

Michelle T.'s requests have been added, at a mid-priority. Yay for CVS having and testing!

I also like the idea of SNUF as the name for the filter, and I don't feel that 'threadsuck' is any worse or any more obscure than other internet words. If people feel it's a problem, let's add it to the FAQ, along with all the other obscure words. In fact, it should probably be mentioned in the FAQ anyway.

Not the FAQ, the How-To, methinks.

I too think "download thread" is clearer and better language for the link name. Nilly and Meijia are both used as names where there can be some explanation of what the name means, and meara-ing is clear from context. "Threadsuck" would not be.

People won't just be clicking "threadsuck" out of curiosity and getting stuck with a 2000-post download.

Errr... Actually, yes, that was the latest plan. I did design a fancy-pants interface, but ita felt it was too much, especially with the thread proliferation. A sample of my interface is here.

I too think "download thread" is clearer and better language for the link name.

Again, my thought was to have two links below the thread title - One that downloads the entire thread, and one that downloads just the unread messages.

Michele, oh Usability Queen (and I mean that in the nicest way), how do you feel about all this?

Actually, no, Jon. I wasn't thinking the page would just dump a file on the user. I was envisioning an intermediate page where one can pick the range of posts, the behaviour (mark read?), and perhaps even have the file zipped before it's handed off.

Usability Queen! Do I get a tiara?

I think the threadsuck control panel is a good idea, if a little confusing in the current iteration, if we think people will use it. And I'm impressed, if surprised, that there are no vampire jokes anywhere on it: that takes restraint.

With Jon's proposal, you'd have

Natter 4,345: The Cheese Continues
Subscribe | Download entire thread | Download unread posts.

My feeling is that unless we know a lot of people want to use the threadsuck option, it's a lot of choice to be surfacing at the top level. ita's intermediate page suggestion, especially if you can set default options and just click OK when you get to that page, might be a better idea if most of our users are reading online.

I was envisioning an intermediate page

OK, I get it. Let me work out a revised intermediate page design. Maybe something that allows an easy download of the referring thread at the top of the page, with more options for other threads below that?

that takes restraint.

It was tough, let me tell you!

I agree that we should have an intermediate page, because people will click on things just to see what happens (it's their right as users) and even the word "entire" won't be enough to put them off.

What might be useful is teaching people how to get the file to download directly to disk rather than appear in their browser first, then get saved.

If I option-click on a link in IE on Mac, that's "download rather than display this link".

What might be useful is teaching people how to get the file to download directly to disk rather than appear in their browser first, then get saved.

Is there a way we set up the server so that happens by default?

Also, would it be cool to run the result through gzip before downloading? It would save bandwidth.