#six apart

[jackyan]

Typepad Poof! Gone. No warning, nothing. I just headed there and this was what I saw.

[poploser]

VideoEgg + Six Apart = SAY Media. This blog was actually started on TypePad way back when.

[poploser]

Vox is shutting down. Not a huge surprise. For the six people still using it, they've added tools to export your content to TypePad and Flickr.

[jackyan]

Found another Voxer for whom the site is dead

We can, refreshingly, put paid to the ‘Vox is blocking orientals’ theory as my Vox and Facebook friend, Patricia Volonakis Davis, went through the same thing back in September. And if she’s oriental, then I’m Aristotle Onassis.

The parallels are concerning. Patricia publicly stated her issue on September 15, when she wrote, ‘I sort of live here still … when VOX gives me permission to post,’ but the problem had been there prior. She had written to Vox, to no avail. And, like me, the site began degenerating during the following week (as it is for me now): ‘I’m sorry I can’t answer comments here. They are not possible to answer due to a software glitch on my page, which has now even begun to affect the appearance of my blogs.’

So, three months on, the error had not been fixed, and Patricia has largely left Vox. She’s put up with being Voxless for longer. If I had a ready alternative, I probably would jump ship, too—though I want to take my content with me. It may mean that the Vox groups I started or run will fall into disrepair.

However, as I said on Facebook this morning, I already use Wordpress for work, and if I had to use it for personal blogging as well, I could wind up in the Priory.

[jackyan]

A history of being blocked on Vox since October 28

As of tonight, Vox has begun blocking its recent activity page from me. Just as the compose screen, which can take days to emerge for me, the recent activity page is beginning to take minutes to load now.

I have looked back at the history of this bug. In late August, Australians were locked out of Vox, but they restored their access.

October 28 was the first day I had to wait hours for the compose screen to emerge. It was all right for the rest of the day and on the 29th. The site was completely down on October 30 and 31 and returned November 1, though I did have one instance where the compose screen took hours to come up that day.

Vox died again on November 2 and 3. It returned momentarily on the 4th. Then, it was mostly dead until the 16th, where I had three days of trouble-free blogging till the 18th.

Since then, it has generally blocked me from composing.

Even until mid-month I was blaming the various ISPs, and as we headed toward the end of November, I still suspected that Vox was blocking some New Zealand cities. It was only till some Kiwi Voxers told me that they could still blog—including Sue Tyler who is on the same ISP as me in Wellington—that I began wondering if the block was specific to me.

On a friend’s suggestion, I started a fake account and found I could blog from there, confirming that Vox’s block was personal to me.

The thought that a splogger had more rights than I did when it came to Vox borders on the offensive.

I also asked Daisy, who works for Vox, to log in as me yesterday. She did, and discovered that she, too, could not compose a post. This was from the company’s HQ in California—which meant that the error is Vox’s and no one else’s.

I’m disappointed today that not only is Vox not fixed, but the error, virus, or server network problem that the company has is spreading.