North Central US | dko_scOH - 5/24/2026 08:44
That would indeed work. It's what we did the last time we upgraded servers. The problem is, you now have a fresh copy of stale software. This code base is at least twenty five years old -- ancient in development terms.
In the interest of security -- and site options -- we really should migrate to more modern code, where development is ongoing. AgTalk is approaching 26 years old, and I'm 65. This next version may well be my last. It needs to run with minimal problems or security holes for years to come.
On the plus side, we can archive all past posts and read them into the new setup. On the minus side, threading will be stripped from the messages, so there's no going back.
Is there really anything wrong with this aside from it being old and not able to handle a few million posts? |
Any update on the random slowness and errors?
