Key to the calendar. Yellow: days when Vox worked normally. Pink: days when the compose screen took minutes or hours to load. Red: days when Vox would not allow me to compose at all.
I’m sure most of you will agree that putting up with a compose screen that will not load for hours or days since October 28 is being pretty patient.
In that time, Daisy and Six Apart have been great at trying to help me troubleshoot why this is happening. They have confirmed that there is something wrong and that, even at Six Apart HQ in California, they cannot get the compose screen to come up when logged on as me.
A number of solutions have been proposed, but despite carrying them out, the loading delay remains intolerably long.
It’s as though the Six Apart servers (after becoming self-aware!) know it’s me and fail to serve the compose page. No code is downloaded.
I remain convinced that whatever is happening to me is connected to what happened to Patricia (who has only made 50-odd posts on Vox, but has exactly the same symptoms) and Ninja (who can no longer compose with this site without switching to Internet Explorer—Vox is the only site which he has to make a browser switch for). I also believe the bug is connected to the one that locked out all the Australians I knew on this service in August 2009.
We also have the mysterious period between November 16 and 18 when the site operated normally, and the compose screen came up on demand. What happened on those three days? I had more tags in my account than when the site first blocked me from composing, and possibly more neighbours. Yet for those days, everything was normal here.
I have never suggested seriously that the block was malicious (though it was fun to entertain some outlandish theories), but it does seem to be rather coincidental that I come across bugs on Vox, Blogger, Facebook and other services continually. Many have been documented on this blog. I just never thought that among the last regular blog posts, the bugs I write about would be Vox’s.
One day I am sure they will find the error, or there will be a new version of Vox which remedies it. The underlying code is updated a lot more frequently with incremental improvements than Team Vox will have us know. Until then, I will check in here periodically—to read your posts, delete spammers, and administer the many groups that I run—but we will have to say farewell to my regular updates. I will also click on ‘Create’ from time to time to see if the bug has been fixed, and, if the site ever lets me, post the odd private neighbourhood or friends-only entry.
Finally, you could say, my disappointment outweighed my patience. As some of you read in a private post yesterday, this is a good time to move on.
Vox is, after all, still in beta, if its terms and conditions (revised a few months ago) are to be believed, so there’s no point my getting mad about this. It is what I signed up for in 2006 when I began as a Vox beta tester. Three years on, it appears I was still in the same boat, but with a less reliable site.
Thank you for all your friendships over the last three years. I have enjoyed it and everything this blog has offered. You can still find me on Facebook (a site with far worse issues than Vox ever had), Tumblr and at my main blog, where I am already ramping up the posting I do. I have a campaign site for the 2010 mayoral election here in Wellington, and will offer occasional commentary at Lucire’s web edition. If the Vox cravings get too much, I might enter the odd thing at lucire.vox.com, but even that account began to fail a few days ago.
This is not a total farewell. In the words of Gen Douglas MacArthur, ‘I shall return.’
Recent Comments