new javascript-only comment/quote forms

Anyone having issues with the new comment form the past day or two? Before, it was pure html, now it’s a javascript function (“antibot”, which I’m assuming helps prevent spamming, etc.).

I’ve always had issues with this site and javascript, that the preview/save buttons would be… “blank”(??). Even reloading the page wouldn’t fix that, but I’d have to back up one level entirely and they “reclick” on the page, and maybe it’d work. Quick example here from just a few minutes ago…

So, the net effect is that I quite often can’t post any comments, etc., and am wondering if anyone else has a similar issue.

Before, I could just go pure html (ie, no javascript) and everything’d work fine, but now that it’s javascript or nothing, I’m kinda cut off. :open_mouth:

Sorry for the hassle. I just removed the Javascript requirement for the post forms.

As for the disabled submit buttons, that’s simply because the post form is blank.

Ha! I just noticed that and was able to just post a comment, thanks! :slight_smile:

I thought maybe I jiggled something loose by playing with js on/off, that it magically “just worked”.

I’m not a js expert or anything, but if you’d want me to look into things to help prevent spamming or whatnot, let me know. Maybe php or something server-side could do the same job.

(Nobody seems to use perl anymore…)

Thanks a ton! I have a lot of prepackaged options available to try, and I’ve been experimenting with a bunch of different things during the past few weeks. I think I’m getting close to the right combination of deterrents without it being too intrusive or restrictive. Meanwhile, “please excuse our dust”.

Yep, some of the key ways to prevent things like the last Borgspam attacks can be pretty simple.

Eg, one might be to not allow new posts if more than X in a 1-day period, X being 3-4 if very few posts so far, or a recently-created account, then gradually increase X as the number of legit posts and time also increases. Violations would instantly freeze the account and hide the posts until checked out. Then you decide whether it’s legit and pass ’em, or spam and s’can the account altogether.

Just that one method can probably weed out the vast majority of dump’n’run spams. And if someone comes to BLF with a bevy of legit flashlight questions (what light to buy, how could I upgrade my XYZ light, what battery is “best”, etc.), a small delay won’t kill him.