At any rate, here is some feedback from the board staff. We're glad we insisted on referring to step one as an alpha test in spite of whatever terminology Hotwheels et. al. is using.
>i liked the blue better.
Agreed.
Dropped in the Hotwheels approved CSS legacy overlay. It's … blue. Could use some improvement but it is an improvement on the default.
>is that a security code? bummer!
Yeah. At the time of this writing every post requires filling out the security code, aka captcha. The developer stated this is changing to a less fascist method soon. BOs have no control or influence over captchas at the moment. This also is planned to change, "soon."
>no embed field?
Another missing feature. There's no option to enable it. We're not even sure what filetypes will ultimately be allowed – this might spell the death knell of formal file upload boards such as:
>>>/library/
Hopefully they'll keep PDFs which should be enough of a reason for /library/ to stick around. We'll just have to wait and see.
Speaking of captchas, at least one board management function requires a captcha. Let's call that feature implementation choice fiendishly ingenious. While restoring the board configuration is good for practice, it's going to get old real fast if they keep smashing it.
Also, about half the options we have access to don't seem to do anything no matter the setting. That's a good thing; a lowly BO shouldn't have access to most of them. Much less a BV, or registered user, or anonymous user, or proxy user. The user permissions system looks to be something epic in scope and finely detailed.
Currently though it's just bonkers.
>Thank you based anon.
And thank you for your efforts as well. We all miss TAR.