Talkorigins

| 19 Comments

Some of you may have noticed that the Talk.Origins Archive was not accessible today. Its hosting company changed the IP address for the server that the Archive is on. The new IP address is currently propagating through the DNS network and you will be able to access the site again as soon as your ISP updates its records.

Also we’ve ordered a new server for PT and will have access to more bandwidth soon.

Update:

Current plans have us switching to the new connection tonight. This means that PT may go offline for you until your ISP picks up the new IP.

19 Comments

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?

Coin Wrote:

Did it work?

As far as PT is concerned, the results appear to be mixed. Bandwidth seems to be good (FIOS is awesome!) but there are still serious backend problems. Bringing up the top page is generally pretty snappy, but it still may take as long as 15 minutes to view any particular thread or perform some action such as “Preview”.

Sometimes instant, sometimes like plowing feldspar.

And “Check Spelling” is unconditionally busticated, as far as I can tell.

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.

Quite a few people were using it to see the posts that weren’t showing up on the page, and to check whether they were double posting. Since you took it away at the height of those problems, it led to quite a bit a of frustration (not just mine; several people posted to that effect).

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.

How about just showing the 10 or so most recent comments, like over at AtBC? That would usually be good enough.

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

Syntax Error: not well-formed (invalid token) at line 5, column 89, byte 230 at /usr/local/lib/perl5/site_perl/5.12.3/mach/XML/Parser.pm line 187

Okay. I’ll fix the speller on degas.

About this Entry

This page contains a single entry by Reed A. Cartwright published on December 19, 2006 1:40 PM.

News Flash: Cobb County Case Settled was the previous entry in this blog.

The Year in ID is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.

Categories

Archives

Author Archives

Powered by Movable Type 4.361

Site Meter