Skip to main content

Preventing Google Calendar spam, and intricacy of requirements analysis

In Google Calendar's (current) default configuration there's an opening for unlimited spamming, with an opportunity for dangerous phishing links. There's a Google Calendar setting that closes that opening, but in a way that also closes some information flow in legitimate collaboration with known colleagues. The details are a good example of the intricacy and difficulty in adequate requirements analysis.

The problem is in what happens when someone creates a calendar event that include you as a guest.

  • The person including you can elect to send out notifications to the event guests via email.
  • Your calendar has a setting which regulates when a calendar entry is automatically created for events of which you are a guest: "Automatically add invitations" (in General > Event settings)
    • Here are the options:
      1. Yes <- default="" li="" the="">
      2. Yes, but don't send event notifications unless I have responded "Yes" or "Maybe"
      3. No, only show invitations to which I have responded
    • You need to select 3 if you want to avoid automatically having spammer's events that include you as guest from showing on your calendar. (If you select 1 or 2 you can mark events that show on your calendar unwanted as spam, but then you have to intervene, and spam numbers could become unmanageable.)
For those of you who are reading just for the solution, that's it. It has a drawback, and a way that Google Calendar could rectify that drawback, tough such a solution is not yet available.

For those interested in how that solution could be better, and the intricacy of requirements assessment: the problem is that selecting 3 means that the system no longer does anything to automatically alert you about events that legitimately include you, but for which the colleague does not elect to issue an emailed notification. (This can easily happen in the context of work or other team endeavors.)

There's a solution for an analogous situation: to have an option to include events depending on whether the event creator is in your address book. This is similar to Gmail's Vacation responder configuration option, "Only send a response to people in my Contacts".

There might be some people in your contacts who overuse the privilege, but at least you have social recourse to let them know, which doesn't work with spammers. Further refinement of the configuration options, so you could identify a contacts group to exclude from the privilege, would provide a mechanical means for customizing to deal with this situation, as well.

Though this configuration issue is a fairly small detail, it illustrates the discretion necessary to enable people to manage communications which are accessible by the whole wide world. There's enormous potential inherent in that, and part of that potential is potential for abuse, which needs to be intricately tamed.

Comments

Popular posts from this blog

Finger Lakes 2019-06 Biking: Overview and preliminary travel, Sunday, Monday June 2, 3

A few weeks ago I went with friends to the Finger Lakes area in upstate New York to camp and bike. It was an important opportunity and exploration for me, and wanting to write about the experience tipped me into starting a blog for these posts and others.

I'm including a table of contents of the trip postings towards the top of each one:
Finger Lakes 2019-06 Biking: Overview + preliminary travel, June 2, 3  ⇐ You are hereFinger Lakes 2019-06 Biking: Tuesday, June 4Finger Lakes 2019-06 Biking: Wednesday, June 5 - small incident, no bikingFinger Lakes 2019-06 Biking: Thursday, June 6Finger Lakes 2019-06 Biking: Friday, June 7 - campsite transition, no bikingFinger Lakes 2019-06 Biking: Saturday, June 8Finger Lakes 2019-06 Biking: Sunday, June 9Finger Lakes 2019-06 Biking: Trip Wrap-Up I love to travel by bike and to camp, and did some substantial outings summers during high school and college. During and after college I also redeveloped digestive problems that I had as an infant, an…

Finger Lakes 2019-06 Biking: Tuesday, June 4

This is posting #2 of a camping and bicycling trip I took with some friends through the Finger Lakes region of upper-state New York. Here's the complete set of postings: Finger Lakes 2019-06 Biking: Overview and preliminary travel, Sunday, Monday June 2, 3Finger Lakes 2019-06 Biking: Tuesday, June 4   ⇐ You are hereFinger Lakes 2019-06 Biking: Wednesday, June 5 - small incident, no bikingFinger Lakes 2019-06 Biking: Thursday, June 6Finger Lakes 2019-06 Biking: Friday, June 7 - campsite transition, no bikingFinger Lakes 2019-06 Biking: Saturday, June 8Finger Lakes 2019-06 Biking: Sunday, June 9Finger Lakes 2019-06 Biking: Trip Wrap-Up This was my first day of substantial bike riding. It also turned out to be a significant test of my endurance.
Around 50 miles total: Shared Tuesday biking map. The map is embedded at the bottom of the page. The destination was Clark Gully, "Birthplace to the World". Steve informed us that the Seneca know it as the place where the The People …

Finger Lakes 2019-06 Biking: Thursday, June 6

This is posting #4 of a camping and bicycling trip I took with some friends through the Finger Lakes region of upper-state New York. Here's the complete set of postings: Finger Lakes 2019-06 Biking: Overview and preliminary travel, Sunday, Monday June 2, 3Finger Lakes 2019-06 Biking: Tuesday, June 4Finger Lakes 2019-06 Biking: Wednesday, June 5 - small incident, no bikingFinger Lakes 2019-06 Biking: Thursday, June 6    <- are="" here="" i="" you="">⇐ You are hereFinger Lakes 2019-06 Biking: Friday, June 7 - campsite transition, no bikingFinger Lakes 2019-06 Biking: Saturday, June 8Finger Lakes 2019-06 Biking: Sunday, June 9Finger Lakes 2019-06 Biking: Trip Wrap-Up This was my favorite biking day.
Again around 50 miles total: Shared Thursday biking map. Again, you can see the map inline at the bottom of this post. The night before was Ash, Ingrid, and my first night actually camping at Watkins Glen. The campsites are nice! Even the secti…