While debugging Autovist today, I wanted to see what methods the Tweet object supported (from the Twitter gem, which wraps the Twitter API) in order to figure out why the message was null. As you can see below, it doesn’t have a nice way of dumping out all values for inspection. 🙁
Autovist was designed with the assumption of one customer paying with one credit card has one Twitter account. We’ve just been faced with a great problem to have: a customer loves the service so much that she wants a second Twitter account’s advocacy to be automated with Autovist. Yeah!
But how can I get this to work with the current design?
I thought my site had been hacked. Suddenly, all content was gone and my FTP credentials were being requested.
To perform the requested action, WordPress needs to access your web server. Please enter your FTP credentials to proceed.
While performance tuning the database to solve Dashboard timeouts, we made a surprise discovery about how tweets and their embedded URLs are actually being used.
Google Analytics is a powerful tool when your site has thousands of visitors a day or more. But it isn’t so good at showing you the most popular links on your site; nor does it allow you to work directly with the data your site generates and sends to it.
The reason we wanted to do this is because the Vaccine Ingredient Calculator’s Ingredient Report has a huge amount of links for more information and it would be really helpful to know the order in which our VIC users find them to be useful. Depending upon vaccine choices, there could be up to 90 links!
ReferenceError: Can’t find variable: Set
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