After bringing the production database down to my local dev machine and restoring it in order to use the latest data to develop against, I could no longer load the Dashboard for my @VaxCalc account as it kept timing out. Autovist has posted more than 25,000 tweets for @VaxCalc tracking multiple broadcasts of each tweet, url clicks and RTs for each of the broadcasts. Was this large number of tweets killing performance somehow?
It took just a day to begin protecting our customers (and anybody who clicks on a link shared by our customers) with the SafeBrowsing API. I’m very pleased with our experience with it. Google provides good setup documentation, so I won’t go into the setup details. Instead, I’ll delve into an overview of how it works and what I’ve learned so far.
Suddenly – nothing with Autovist is working.
Customers are sending in scary warnings Google has placed in their emails from Autovist, like this one
An excellent tip from a friend on teaching math to a dyslexic child. (As a dyslexic myself, I found this method very appealing much easier to read.)
One of the most interesting systems I ever created was a Grassroots supporter database that:
- combined multiple lists of donors, supporters, email subscribers and action alert subscribers
- ran all addresses through Google Maps to show hot spots of support at state levels
- obtained GIS coordinates via Google Maps API and ran them through Sunlight Foundation’s API to discover which state legislators represented the largest number of supporters and donors (where do we have leverage?)
The Grassroots supporter database helped the organization know which legislators they could most powerfully lobby via a larger number of supporters in their districts.
Here is a view of support across Virginia: