The comment module is included in core. That's fine BUT...
Normal users aren't savvy enough to know that by enabling forms, they're exposing their sites to spammers and the likes.
And, even if they are, they might not be aware of the different options to protect themselves. (Like me recently. I didn't know there were plugins in Wordpress that helped against this. Yes, the monkey is slow. Quit your giggling)
Soon, users will encounter the barrage of spam comments and, frankly, that's just not a nice experience to subject users to. They'll get frustrated they aren't getting any real comments and managing tons of spam will become a headache.
Knowing what comes along with comments, is this the UX we want to expose Backdrop users to by default? Shouldn't we provide minimal help given comments are on by default.
I think Backdrop should go the extra mile and enable the Honeypot module by default (users can deactivate them in the config if they so choose).
It'll show the world some thought went behind this instead of letting users fend for themselves, alone.
Backdrop shouldn't be a CMS with just modules slapped together.
Got the idea while thinking through this issue #1168
Recent comments
This is helpful. When I Googled for suggestions about the error message, I found an old entry in Stack Overflow that suggested increasing max_connections. I passed that along to the hosting...
"SQLSTATE[08004] [1040] Too many connections" error - any ideas?
Thanks for the suggestions. All caches have been enabled from the start. I'm not sure what qualifies as a "complex" view. There are 400-500 pages that include EVA fields. But the vast...
"SQLSTATE[08004] [1040] Too many connections" error - any ideas?
Also, when we had some problems with the Backdrop sites, this is what the server admin did: I have increased the max_connections for mariadb and increased the child_processes for...
"SQLSTATE[08004] [1040] Too many connections" error - any ideas?