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
Thanks argiepiano, still seeing the flicker on your site. It happens when clicking between the level 1 links, page in top level and about, can see the height increases momentarily. I've looked at...
CSS menu flicker bug
richa78, I've submitted a PR that (in my testing), removes this issue. Can you give that a try? It's linked in that issue mentioned above.
CSS menu flicker bug
I think it might be a good time to review the status of the field group functionality in core issue. https://github.com/backdrop/backdrop-issues/issues/647
Dec 14th - Weekly Meeting Agenda Items