I wonder when I could start charging for my tweets? Find out which celebs are selling out here: http://ow.ly/Trh3
Giant People: 15 Amusing Photoshopped Pictures | Pixzii http://ow.ly/RYVl
20 Illusional Droste Effect Images that will Twist Your Mind | Pixzii http://ow.ly/RYUz
http://ping.fm/YVsT3 Resolution to eat healthier, lose weight, + more time w/family? Consider my friend's meal service! Yumm!
You google. You text. You chat. Do you Poken yet? http://ping.fm/OlmnP #RVA does...
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.’
Not sure how many hours it has been since Vox was capable of loading a compose window for me. I lost count. I no longer believe that deleting tags has helped, especially as it is now 2.20 a.m. and I had no access to Vox all evening. Please write me with your next theory, Vox.
As a result of the return to terrible load times, Kimmie’s theory about a dodgy neighbour might still be true. I haven’t deleted everyone from my neighbourhood and started from scratch, which is arguably the next step, if I have sufficient time to waste.
I have downloaded Firebug (thanks to my friend Andrew Carr-Smith) to see what data Vox loads on to my browser in the times I get a blank compose screen. Answer: none. Nothing even begins to load.
I still think the Vox server knows when it’s me, Patricia or Ninja, or any of the others who might have left here without telling us why, and fails to serve any compose screen to us. I still reckon that there is something peculiar about our accounts that the programming does not like.
I’m getting paranoid importing from YouTube because of the tags they introduce, and tags might be one of the reasons it takes me hours to get a compose screen on Vox. However, this one came up on demand, which is a relief.
I showed this to my neighbourhood yesterday, but as the YouTube one is public, I have no problems sharing it more widely. It was my TV appearance last month on CTV, with Angela and Megan on Good Living. This was not networked, but it was very fun to do. The set reminded me a bit of the Good Morning one at Avalon, except I got one thing that I was promised but never got: a subtitle with both my and Lucire’s names.