Beta board is now at version 0.2.

On migration: To sum up what I think is the major issue, there are a whole bunch of inactive users in the user table and all those passwords are stored in unsalted, insecure hashes. If we migrate users, then we have to keep around all those insecure password hashes. Active users could be forced to create a new password that will be securely stored, but the inactive users will just have those insecure hashes sitting around.

The new site makes it a lot harder to hack into the database, but it's best to assume that database security could be breached.

As always, the beta board is at https://beta.buffistas.me.

Not a lot of work slated for beta 0.3, but not much free time to work on it either :(

[link]

Also, the data schema of the beta board is pretty similar to the current board. However, tables are not created for new threads there is just a posts table and a threads table (called subjects because of a keyword conflict with threads)

That's how the board here used to work, but ita had to split it out into individual thread tables because the posts table just got too big and unwieldly.

Hmmm.... that shouldn't be an issue with the Postgres database.

In case you didn't know the beta site is now at version 0.3. Support was added to close threads and there are a few bug fixes. Version 0.4 will be about filling out a lot of the static content. I'm thinking I might take a little different approach and make the static content at least semi-editable from admin so it's easier to update things.

That's the update so if you didn't know, now you know.

Made another update.

From a user perspective it just adds a static etiquette page. From the admin perspective there is a lot more as pages can be added and edited in the admin portal. Such pages can then be edited by admins without having to write HTML or dealing with having to check files in and out.

I need to add a preview option in the admin section still as the WYSIWYG editor isn't always.

or dealing with having to check files in and out.

Is there a check to make sure more than one admin isn't editing the same page at the same time?

Nope. I'm sort of assuming that pages won't be edited all that often.

It could be added. When the edit form is loaded there could be a timeout period and disallow loading the edit form until either the edits are posted or the timeout expires. But that has its own drawbacks if someone starts editing and then comes back in an hour or so then their editing session will have timed out.