<< List of all previous releases
As most of you know, new anti-spam legislation was recently introduced that changed the way that services that generate email have to behave. While the email service I used already supported unsubscribes, the legislation introduced a fundamental change in that recipients of emails now have to explicitly opt-in. Previously, it was assumed that anyone with whom you had a legitimate relationship (e.g., based on the fact that you were using your ScoutsTracker account) had implicitly opted-in.
So now under “Account” | “Signed in as” you can see your “Opt-In Email Permissions”. When you next sign in, you'll be told that you must decide whether you want to opt-in or opt-out of a couple of email types.
Furthermore, if you opt out of receiving notifications (e.g., pushed events, migrated youth, event signups, etc.) this has an impact on other functionality that I now need to accommodate (e.g., if you try to add yourself to the list of people who get notified when youths signup for an event, but you've previously opted out of receiving notifications)
Note: direct scouter-to-youth/parent emails is not affected, nor covered by CASL, as those are non-commercial messages written by you, to a set of recipients chosen by you, and triggered by you. In this regard, ScoutsTracker operates no differently than gmail or yahoo or hotmail… i.e., ScoutsTracker simply acts as the delivery mechanism.
I'll skip all the boring technical descriptions, and just say that the upshot is that with a database managed remotely, it allows for faster recovery after a server crash.