I've had a number of interactions with the SCORE organization (nee S.C.O.R.E., the Service Corp of Retired Executives). In his post I'll outline those and provide a file of slides prepared for my presentation at St. Paul SCORE's Lunch and Learn Roundtable on May 2, 2017.
Curt Trout's blog
We have just learned that Acquia, the parent company of Mollom, has announced that they will no longer support or maintain the Mollom service as of April 2, 2018.
We are sorry to see this Spam fighting service go. We particularly liked the way the service worked, frequently invisibly, to block Spam submissions.
Traditionally, websites have used HTTP (HyperText Transfer Protocol) by default and only used HTTPS (HTTP Secure, or HTTP over TLS, or HTTP over SSL) when they were processing particularly sensitive data like credit card information. I’ll look at why this was the case and why we should start using HTTPS for all website traffic.
While this post is particularly pertinent to those people and organizations that operate their own websites, e.g., Troutreach Technologies' clients and potential clients, the information should be useful to all Internet users.
Please join me in remembering:
America is the Home of the Free
Because of the Brave
Thank you, Veterans
Please click the Read More link to see a very touching tribute.
A recent newsletter from one of our hosting providers reminded us of the importance of responsive website design. It also pointed the way to a useful Google Mobile-Friendly Test.
Most of us like to receive messages; nobody likes to receive spam messages. Once one of our email addresses becomes known to spammers we are going to be targeted. Let's see how we can shutdown one common way that spammers harvest email addresses.
Everyone knows what a honeypot is; right? Wrong!
We recently realized that we had never addressed the Honeypot module specifically in a blog post. Let's take a look at it now.
Most, if not all, of the sites we develop have a copyright notice in the footer. In the past this usually meant an annual update, on January 1st or 2nd, to update each site. There's a better way and here it is:
As much as we try to make the operation and maintenance of our websites intuitive, there is a need to document how a site has been constructed and why certain decisions have been made. We used the Drupal contributed module Site Notes to meet this need on Drupal Version 5 and 6 websites. Let's look at an easy to use, and perhaps more flexible way to meet these needs in Drupal 7 and the future.
I was doing some surfing and stumbled across this presentation from Drupal Camp Indianapolis in July, 2012. While the intended audience is people looking to develop websites themselves using Drupal, it does contain useful information for others not familiar with a content management system (CMS), like Drupal, and distinguishes between the most popular Open Source Content Management Systems, namely Wordpress, Joomla and Drupal.