>You could try making the line that separates the threads the same red as the names of posters, or make it thicker.

Let's try the first suggestion.

>I can't help but notice that there's no permalink for each reply anymore.

OK, I'll bring it back for now. The idea is to simplify things and keep a single link: when clicked, it cites the reply, and if you right-click on it and select "Copy link address" from the popup menu, you get the post's perma-link. I still plan to make it so on one of the subsequent updates when I finish and fully debug a quick reply feature.

>I don't know if the old board software did this, but it seems that the new software will re-save an uploaded image for the thumbnail even if the uploaded image is already small enough to fit the thumbnail.

It thumbnailed unconditionally before, since I haven't made any major changes to the thumbnailing code. However, expect new restrictions on images to come: images smaller than thumbnail size (which will be fixed at 200×200 pixels) or with aspect ratio beyond 1:10 / 10:1 will be rejected. So, re-saving thumbnails is fine. All images will be re-thumbnailed eventually anyway.

>It would probably be wise to make sure the password limit for when you create a reply is the same for when you delete a reply.

This discrepancy stemmed from the fact that I basically ported the UI from my new IB software first, overlooking a few things in the process. I rewrote the password handling code and fixed the issue: now passwords are stored as cryptographically strong digests (using Blowfish-based bcrypt) and can be at most 72 bytes long. However, as outlined in the updated FAQ, passwords now expire: you have just 3 days to change your mind and delete a post before it becomes public domain.

E-mails are no longer restricted to 30 characters as was idiotically enforced by vichan. The new limit is 255 bytes as dictated by applicable RFCs. Post message length limit is henceforth 65,535 bytes on all boards. Note that I mean bytes, not characters: due to technical shortcomings (namely, the use of MariaDB for storage), text field length limits are imposed in bytes, not actual characters; our site uses the UTF-8 encoding, meaning that a single character can occupy from 1 to 4 bytes (e.g. Russian characters take up two bytes, Chinese/Japanese/Korean even more.)

Thanks for feedback. As a footnote, a few more sleepless nights on coffee and Adrenaline Rush, and the site's operation should stabilize by the end of August.