Blue's WordPress Blog

…something that’s been troubling me about ezboard, Inc.’s CEO, Robert Labatt’s Yuku profile is that he seems confused about dates.

He appears to be confused as to when his company’s data was compromised by what they claimed was a hack attack and they lost all that data: 70,000 posts on our ezboard alone. That’s one out of the 500,000 claimed ezboards.

He writes:

“I came to ezboard in 2004 as the CEO with a mandate to improve the service and create a great company. In the time I have been at the company, we have really improved the reliability of our systems (and after the May ’03 attack, our security).”

You know, I could have sworn that was May 2005… You know, after he was put in charge and not, as his self-penned profile might erroneously suggest, before.

I’m sure that’s just another typo and not deliberate though…

So come on then, are you migrating ezboards to Yuku yet or not?

There’s another announcement over on the Lobby:

“The board migration tool has been completed, and is ready to go. We’re going to take it slow to start with, so that if there are any problems, we don’t have a flood of boards with the same problem.”

This was posted on Friday afternoon. Maybe there’s been no response, because alison saw fit to “bump” that topic this morning.

Of course, given that this “announcement” was made in one of the chat forums on Yuku, that might explain things. After all, isn’t that preaching to the converted (if misguided)?

Surely the place to make an announcement about migrating ezboards would be … ezboard? Well there’s no official system-wide announcement and nothing in the help forums apart from another staffer saying:

“Boards being migrated to Yuku is still down the road a bit, maybe by the end of the year.”

That was posted two days earlier, so the board migrations must have come as a bit of a surprise or something to them…

It certainly is just more confusion and lack of communication between ezstaff. After all, no-one seemed to know they were ready to go until I reminded people of their own situation. No-one involved on the tech. side seemed to have told any support or other staff.