Nope, they are different functions. And in that case, I'm afraid that this option isn't feasible, with MD5 being one-way and all that...
Let me check if there's any way to make .htaccess use MD5 passwords, though...
Edit: oh wait, there *is*. .htaccess uses by default crypt() passwords, but you can configure it to use MD5 too.
Anyway, these are all implementation details, and I'm sure something can be worked out in the end. The first decision to make, if I understand correctly, is still at a higher level...
How would the user table stay updated? Every time a new closed thread was ported, an update to the archives user table would be required.
Well, yeah. Basically. That would be how.
Update it when the archive is updated.
Edit: probably by using the most-up-to-date version at the time of archiving.
I'm in voting mode:
I say option 1. It is what I'm used to so it might just be a familiarity thing.
Update it when the archive is updated.
But the 100 users that joined between archives can't hit the site.
I still vote #1.
But the 100 users that joined between archives can't hit the site
Could also sync it twice a week, whatever makes it smoother.
Alternate solution:
#1 for natter, etc.
Modified threadsuck (with #names) stored offsite for showthreads, Nillylinks updated to point to them,
OR
Leave closed showthreads on the main board, archive everything else #1 style.
Hmm. Why don't we start with the modified #1? Zip and move Natters, leaving showthreads?
The problem with any synching, PMM, is that as far as I can tell, it has to be manual. As in not even with your average web app (since most hosts only allow programs running on their servers to access their DB).
Why is it more important for the Show Threads to be searchable?
t /genuinely curious
