Note: I’ve disabled comments and the contact form on this website until after I recover from my next surgery.
If there’s a dark side to writing books and having a website that gets millions of views, it’s that people who seem to have a lot of angst think it’s okay to leave mean-spirited comments on the website. I moderate all the comments, so outside people never see them, but I’m amazed at some of the angry posts people write. Part of me would like to reply, “Sorry, I didn’t write Unix, Java, Scala, Gimp, etc., I just try to explain how they work,” but instead I just delete their comments (because they never leave a name or email address).
My guess is that the people who write these things are angry at something else and for whatever reason that leads them to think that they can post a mean comment here anonymously, but yeesh, every once in a while the haterade gets to me and I just turn off the ability to comment completely for days or weeks. To the people that post mean-spirited comments like that, you need to take responsibility for your own life and/or get some help.
Back in 2013 I read the book Clean Code by Robert C. Martin, and in an effort to keep that book alive with me a little while longer, I decided to make my own “Cliffs Notes” version of the book on this page. One of my favorite notes from below is that a language named LOGO used the keyword
to in the same way that Scala uses
def, so a method named
double would be defined as
to double... instead of
def double..., which seems like it would help developers name methods better.
After trying a lot of different anti-spam modules with Drupal 8, the best thing I’ve ever done to reduce comment spam is to go to the Drupal admin /admin/structure/types/manage/blog/fields URI, click Edit on the Comments field, and then select the “Anonymous posters may not enter their contact information.” Since I chose that option two days ago I’ve only had one spammy comment show up in my approval list. That field gave spammers a simple way to enter a URL, and without it, the spam seems to have dried up.
As I noted five days ago, Mollom went out of business so I had to switch this Drupal 8 website to use a different module to control comment spam. I ended up adding two modules that work together, but the side effect of using their best features is that they end up disabling Drupal 8 page caching. This image clearly shows the result that disabling page caching has on CPU use.
I’m not sure why, but on April 3, 2018, the people behind the Mollom anti-spam module for Drupal basically went out of business. This meant that I either had to disable comments on this site (which I did for a while), or look at other anti-spam modules, which I did over the weekend.
As a brief note today, if you want to know if your Drupal 8 web pages are being cached, take a look at the headers that are returned by your Drupal 8 URLs. Here’s an example using the
On April 3, 2018 this website suddenly got a ton of spam comments. Fortunately I caught the probably very quickly, and turned off the ability for people to post comments here. When I checked into the problem I found that Mollom — created by the same person who created Drupal — basically went out of business on April 2nd. (I’m sure there was some warning about this decision, but I sure didn’t get it.)
I’m often surprised when people who offer a free service shut down that service without asking a simple question: “Would you be willing to pay for this service, and if so, how much?”
(I’ll re-enable the ability to post comments here when I find a good replacement for Mollom.)
Note (March 14, 2018): I’ve disabled comments on this website until I get through this current illness.
Due to a potential security issue I’ve disabled new comments on this website. Hopefully they’ll be re-enabled next week.