Recently there’s been simply too much downtime for the site, our previous hosting provider simply couldn’t live up to what it promised.
It took a little while, so apologies for those who tried to access the site while we were moving.
Early signs though are awesome, the site is already much more stable, and much faster than it was previously.
As always, if you have any issues or come across any bugs, please do let us know by emailing [email protected]
Something that’s been requested a few times in the past is to show the actual search results in the email that is sent out when new matches are found.
I’m glad to announce that this feature request has now been completed, and all match notification emails that are sent out from now contain the details of the matches found.
As usual, keep submitting feature requests and letting us know what you like / dislike.
Submit feature requests in the knowledge-base here
There’s often been confusion on just how often tweets are sent from your queued matches, so it’s been updated to something that makes a lot more sense.
Previously, your queued matches were sent out at the same rate at which your search was running. Meaning, if you were running your search every 2 hours, then one of your queued matches would be sent out every 2 hours.
Obviously this isn’t enough for most people, as the queued matches list can’t keep up and send out at a rate fast enough, as you’ll be adding more and more items to your queue over time faster than they can be sent out.
So, the new rate of sending out from the queued matches list, is a flat rate of one every 10 minutes for your each campaign you have running. So for each search that you’ve setup, up to 6 tweets per hour will be sent out from your queue.
Over time, a few accounts have been abandoned, and the updates to the search script made that much more obvious as in the past 24 hours a lot of old users have received emails saying they have new matches ready for them to check out. Some of whom were excited that their seemingly stagnant account was bringing in fresh results, others a bit bemused that they were getting new results after a long quiet period.
A decision has been made to clean up the campaigns on the site, and accounts that appear to be stale have been deactivated.
Any campaigns that have not sent out a reply in the past 3 months, have been deactivated. This cleanup will happen on a daily basis to keep things running smoothly.
This doesn’t mean your whole account will be deactivated, just old stale campaigns, you can simply re-activate the campaign if you’d like to keep it running by editing it.
With more users brings more load, and as a result there’s been a few server outages recently (which we apologise for), so a few hours today was spent investigating the causes and resolutions.
Happy to say that the server is running much leaner now, and operating much more stable.
The finder script has been heavily revamped, so if you notice any bogus results, please let us know via the support site and we’ll get on to it ASAP.
We’ve been long time users of Zendesk for the support portal, but have decided to integrate more with it now.
Logged in users will now see a support tab to the right of the dashboard that will allow them to search the support forum as soon as they run into a problem, and find the solution they need to power on through.
What we’d like to also see, is people using this new tab to let us know what changes and feature requests you want see developed into the system.
Go check it out!
A bug was discovered yesterday that seemed to affect a handful of users, whereby their confirmed matches would disappear from the system soon after being confirmed.
A fix has been found and put into place to ensure that no confirmed matches are removed from the accounts prematurely.
Matches will remain in your queue for 24 hours unless they are confirmed before that time, confirmed matches will stay in your queue for 30 days before being removed.
Apologies to anybody that was affected by this issue, and please do log any bugs found at twithawk.zendesk.com so they can be sorted out quickly.
Tagged: bug, queue
It’s a big day for TwitHawk, a huge milestone has been hit, a quarter of a million tweets have been sent via the platform, and things are only picking up at a fast rate. That’s 250’000 introductions / leads generated / new friends made. In truth, this milestone could have been reached a long long time ago if it weren’t for being active in fighting SPAM and in making sure that Twitter isn’t flooded with mindless tweets, instead ensuring that both senders and recipients get benefit from the relationships formed.
For a limited time, to help celebrate this milestone all new users that sign up and use the coupon code of QUARTER will get $10 worth of credits (200 credits) free to kick start their campaigns.
In side news, this past week has seen a lot of improvements including:
A final note for non OAuth users (older accounts).
Twitter will very soon be turning off their API access to accounts that do not use OAuth (see here for more info). If you don’t know if you are using OAuth with TwitHawk or not, don’t worry, all you need to do is login to your TwitHawk account and go to each of your accounts, if you are not using OAuth the system will let you know and guide you through converting your account to use OAuth. If you don’t get any popups, then you are already using the right authentication and don’t need to do anything further.
As the site gets more and more users, the server is having to work harder and harder to keep up, and a few of the cracks that were minor before were spreading and showing themselves more often than is acceptable.
A thankyou to all those that sent through the details of the errors they were getting, and if anybody has errors in future please do send them through to help with the sites debugging.
Various improvements have been made to both the site itself, and the Twitter search and sending scripts that should improve the sites stability, but as above, if you notice any issues, please do send them through to info -at- twithawk dot com
Recently a few people have reported that they are getting duplicate emails from the system when new matches are being found.
This has now been resolved, it was only occurring for accounts that had multiple Twitter accounts assigned to their TwitHawk account.
RSS