This slowness problem seems to be a lot more extended and is taking a lot longer to "resolve" than similar problems in the past. I don't think that "traffic" is to blame - - as I recall, new threads and posts during the summer of '98 (impeachment summer) had to blow away whatever is coming along now.
On the other hand, when I tried to post to yesterday's FReeper USO Canteen thread (the one about the soldier who was killed during a covert operation in Poland), it took forever for the thread to come up because of all the pictures and graphics. I finally gave up on it.
But would that kind of stuff have anything to do with me clicking on 'Post Reply' in order to bring up this box I am typing into and having to wait forever for it to come up? (That is, if I don't get the "Site Not Responding" pop-up first.)
I think the problem is some kind of virus, security breach, or scumbag Democrat sabotage. That's what I think.
I forgot to say that my reasoning behind my theory is that we are slow during EAST COAST WORKING HOURS, such as the times Terry McAuliffe is in his office. You will notice the speed has picked up now.
... it took forever for the thread to come up because of all the pictures and graphics.
Each picture and graphics comes from some particular server, as specified in the html for that picture. If someone links to a picture on a slow or easily overloaded server or to an excessivly large picture, then the page with that link will load slowly, while other pages could be fine.
But would that kind of stuff have anything to do with me clicking on 'Post Reply' in order to bring up this box I am typing into and having to wait forever for it to come up? (That is, if I don't get the "Site Not Responding" pop-up first.)
Not likely anything related. Slow replies on posting or on pretty much every FR page, even those without slow loading pictures, are likely due to something on or near the FR server or its internet link. Unless the entire net seems slow to you, in which case the problem is more likely near your end or a massive overload or failure in the main web backbone.