1. Infrastructure Issues
Our server-side architecture had to change significantly to enable the uber-cool functionality that our twitter client relies on. As is always the case with software development, this threw up some unexpected difficulties. We simply hadn't envisaged the complexity required to adjust to, and fix, these.
2. SSL Certificate
We've been trying to order an SSL certificate from 123-Reg. Their level of service has been very poor with no communication when problems occurs. They have until lunchtime to deliver otherwise we're off to Go Daddy.
3. Breaking changes to Twitter API
Within the past few days Twitter made some changes to their API that has broken the 3rd-party library we're using. The fault developed because a, previously assumed, numeric field in their response now sometimes has the value "100+". This causes exceptions when you expect it to actually be a number! We know the library authors are working hard to fix this but we just have to wait for them.
So, where are we?
Issue 1 has been fixed, but issues 2 and 3 are still outstanding. As soon as they're resolved, we're ready to roll.
Apologies to everyone that's waiting for this trial. We really appreciate your patience and we'll let you know the instant it becomes available.