If you have a Zoom account, either free or paid, then you can set your displayed name in your Zoom profile on the Zoom website. However, most Zoom participants in meetings sponsored by non-profit groups don’t have, and don’t need, Zoom accounts. The name displayed for these people, by default, probably isn’t very user friendly. Let’s see how Zoom gets the default displayed name and, more importantly, how we can change it to better suit all meeting participants.
I've been involved lately helping people get Zoom installed on their computers and verifying that it works. I can categorize new Zoom users into three categories:
- People who are able to get Zoom installed and running on their device(s) by simply following a meeting invitation hyperlink and letting the automated process work. The overwhelming majority of new Zoom users fall into this class.
- People who need a little help understanding the process and need prompting to follow the normal path. I'm guessing that maybe 10% of new Zoom users fall into this category.
- People who get Zoom installed correctly but find that normal Zoom meeting hyperlinks don't work. This doesn't happen often, but it does happen enough to require a circumvention.
That third category is what this blog post is all about.
The COVID-19 pandemic and associated Stay At Home orders have disrupted the way we get together in person, both formally and informally. While there are many platforms that facilitate person-to-person connections "in the cloud," Zoom is definitely one of the most, if not the most, popular. In this blog post, and a few more to follow, I'm going to look at this platform, address an unusual problem that will stump some potential users, and encourage more people to use Zoom to host their own "meetings in the cloud."
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.
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.