There seems to be a very significant system glitch effecting us right now, where many new threads are losing both their content when being posted, as well as not even having a "Reply 1" that anyone can respond to.
We are not sure what is going on, but if you try to post things and get a thread that is empty, just hit abuse and tell us to remove it. You may want to hold off on posting new threads if you have that happen until John Robinson can figure out what is going on.
When I posted a thread a few minutes ago it said that there was an error and it had been logged, for whatever that's worth.
For some reason, FR keeps tripping my firewall into thinking it is under attack. (The IP address it records is FR's.) Also, I get blank or mostly blank pages at random, both on the latest posts page and in the threads.
Artificial intelligence taken to a new level. Kudus to the server!
"if you try to post things and get a thread that is empty, just hit abuse and tell us to remove it."
Okey dokie. Something weired going on. Vast left wing conspiracy, me thinks.
I haven't noticed this specific problem...
but for the last 3~4 articles I posted, when I searched on a title word (to avoid posting a duplicate) I received a notification that I didn't have authorized access to the FR server for the search function. (I forget the exact wording). Anyway, I just hit the backpage on my browser, hit the searh button again, then it would work!
I don't know if the problems are related, but figure I'd let ya know FWIW.
Yes, the content on some resent threads has been low.
I've had problems posting for the last couple weeks or so. I just about quit posting articles because of this...I just thought it was my 'ol computer acting up.
Then they'd go on a conspiracy theory for about 1,000 more posts about the Bush dictatorship infiltrating opposing views and damaging the servers, etc. etc.
An improvement I can live with.
In the last two weeks, I've noticed several items on the http://www.freerepublic.com/focus/f-news/browse page where the listing was "#2 of 1" - it seems to be fixed now.