It’s not hackers. Those kind of claims are just ducking the issue.
From what I have seen and what little information has been reported, it’s a database problem. There is either a table fragmentation problem or the size of the database has just outgrown the design/implementation of the software. It’s not likely to be a hardware limitation.
However, all offers of professional help have been spurned, at least publicly. Maybe after the election, it will be reconsidered.
In the meantime, I have been looking for info elsewhere, and dropping in only when things are hanging together long enough for me to pick up some links to articles elsewhere.
That might be worth investigating, although I don't have the professional expertise. If correct, perhaps FR could split the database at a key date such as Inauguration Day, 2013, so that we can access "freerepublic.com" with the delay if we make that selection for historical checks, but new posts are in the much smaller and faster newfreerepublic.com".
I think that’s the same conclusion we’re coming to. Very likely a database/software/hardware design vs actual usage issue. And there is no quick cure. A complete redesign and rewrite using all newer technologies in hardware and software ought to do the trick. Thankfully, I’ve been working on a new system using AJAX based techniques for a couple years (in my spare time) and even have a bare bones prototype working, but it’s months away from even being ready for beta testing. And John is beginning to think Cloud. Who knows? We may be rolling out something brand spanking new in the months ahead. But it’s going to be hell around here for the next week or so. Praying we make it.
I'm not saying hackers but there are several of us that can tell you for a fact, the instant ConEd blew up and all of Lower Manhatten went down last night, every function on FR started working perfectly. That lasted the rest of the night.