Talkorigins

If you have a notworking perfeshunal, you might have a talk with him about DNS "time-to-live" parameters.

Note that the issue with TOA had to do with a missed email (stupid holidays), which is why TTL wasn't used with it.

Now, PT uses a DNS provided by the domain name registrar. I doubt we have TTL for such a budget-friendly service.

Most of the budget DNS providers I've looked at (and definitely the ones I use) give the customer complete control over TTL and nearly every other aspect of your zone(s). If you'd like lots of free advice on that topic, I'll be only too happy to blather on at length.

Sorry, I was thinking about something else when I made the above post. Disregard the TTL stuff.

Did it work?

Did it work?

— Coin

I did some more clean up of our backend today. For a while now, we have been running Lighttpd as our primary webserver, and Apache has been running as well, serving some of our sites via a proxy to lighty. Tonight I finally moved the rest of the sites to lighttpd, and turned off Apache. Hopefully, things will be improve on the server without lighty and apache fighting for resources.

Since we no longer have limited bandwidth, we no longer need to compress our pages, which should also help us serve active threads more quickly.

I've also turned off some bandwidth logging that I was doing. This may improve latency. (It didn't work properly with multiple worker threads anyways.)

I just heard about the spelling issue today. I'm looking into it.

Spellcheck is now fixed. I needed to put the full path for aspell.

Hi, Reed. Any chance that Preview will go back to showing the thread, so we can see what we're responding to while drafting our posts?

Probably not. I think it is too much of a resource hog on the system to generate a huge comment preview page for posts with hundreds of comments. When I took if away, I didn't think that people used it that much.

I'll look into the possibility of opening the comment preview in a new window.

I should also add that I've updated my custom javascripts on DRN. They includes a "quote comment" button implemented in Ajax. Eventually I'm going to update PT's scripts.

With AJAX, I would think you could add the preview version of the comment (distinctly marked) to the current page, so there wouldn't be any need to compose a whole new page.

"quote comment" would be cool, especially if it were possible to quote more than one comment and have each one added to the comment box. Buttons to insert KwickXML templates, especially url, would also be nice.

Thanks for the work you've done, and any you might do in the future. :-)

When I took if away, I didn't think that people used it that much.

I tried out the Q button at DCN. It works just as I would have hoped -- except that, in firefox, it takes 2 seconds for the quote to show up. That may be a problem with my installation, which has too many weird extensions installed. However, in IE the text shows up right away, but I get an hourglass icon whenever my mouse is in the text entry box.

Er, DRN.

Hi, Reed. Any chance that Preview will go back to showing the thread, so we can see what we're responding to while drafting our posts?

Probably not. I think it is too much of a resource hog on the system to generate a huge comment preview page for posts with hundreds of comments. When I took if away, I didn't think that people used it that much.

The hourglass issue on IE has been fixed in my quote comment script.

Performance overall appears flawless, except possibly for

<degas.fdisk.net>

System error: Aspell program execution failed (`aspell -a --lang=en_US --encoding=utf-8 < /var/tmp/aspell_data_Az75O5 2>&1`)

Okay. I'll fix the speller on degas.