Jon is brilliant. The secret crush line starts behind me.

{blush}

DX, we can get a start on making smaller tables if you want to threadsuck and zip and post the closed Natters.

Then I'll mark them archived, and change the code to redirect links to them to the archive page, perhaps even to the right href anchor (if you name them "threadxx" where xx is the thread ID, that should make the system workable).

I can do that. I don't even need a reason.

You're a wild and crazy man.

This is a "maybe it's just me" thing, but when I do Threadsuck, it takes over my whole browser, in fact makes it very hard to do anything on my computer, until it downloads the whole thing.

And my issue is, if the thing I wanted was available via a link, rather than a form submission, then I could use the Alt-Click option -- to "download to disk" rather than the "load in browser window, then save" which is what my browser so obviously hates (reading 1.5 MB web pages!).

So, I'm all about the reverse engineering.

I can figure out from the form, that the link to download Bureau from 5007 onward would implicitly be something like [link] something ]&thread_id=25&beg_post=5007&stage=submitted&keep_unread=1

But, that doesn't work. It gives me that "Fatal Error" page.

Am I causing big problems by doing this?

This is a "maybe it's just me" thing, but when I do Threadsuck, it takes over my whole browser, in fact makes it very hard to do anything on my computer, until it downloads the whole thing.

Not just you, but also not just this board. The threadsuck is a 5+MB HTML page, and Mozilla does seem to choke on it a bit for me.

I got Natter 1 threadsucked this afternoon. It took about three hours. The threadsuck itself didn't take very long, but being a perfectionist, I went through the original thread fixing all the instances of superlong URLs and superextended-hyphenated-word-sequences, so that anybody who read the threadsuck wouldn't have to side-scroll each and every one of ten thousand posts. The URLs are easy enough to find, because you can search on "http", but those frelling hyphenations are driving this archivist bonkers.

Also, I'm out of town for a week starting Saturday, so I don't know how much I'll have done by then, if that's an issue.

those frelling hyphenations are driving this archivist bonkers

What app is it you're using to search, and can it use regexes?

Because I have a regex for multiple-hyphenated phrases right here, AIFG!

Or, of course, he said coming back from the coffee machine, a regex for "any phrase over 50 chars not containing whitespace gets a linebreak at char 51" would be easy.

I was hoping you'd say something like that.

Right now I'm just doing it in a browser window. I set my preferences to download, say, a thousand posts at a time, then if my horizontal scroll bar appears, I search through that batch of posts in smaller chunks until I find the offending hyphenations. What I need to know is not only what long hyphenations there are, but also what post they're in so I can edit them.