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.
