Re: What ICANN Does With Public Comments on the Budget...
by
George Kirikos
The message failure was at 18:17 GMT (i.e. -0000), note the time zone. Since I was the one that sent/discovered the bouncing email, I know for a fact it wasn't working.
Convert the failure time to Pacific time by subtracting 7 hours, i.e. 18:17 minus 7 hours = 11:17 Pacific time. Bret's post was at 12:27 Pacific time. The first email that made it through, after ICANN fixed it, was at 15:20 -0700 (i.e. Pacific time zone).
Thus we have the message failure at 11:17 Pacific time, Bret's post at 12:27 Pacific time, and the first successful comment at 15:20 Pacifc time. The question "how come that George Kirikos has left two comments before the time you've put in your blog" obviously has a fatal flaw in it.
When ICANN Board Members can't do simple timezone math, the staff doesn't have to worry very much about scrutiny of the Budget math...
The message failure was at 18:17 GMT (i.e. -0000), note the time zone. Since I was the one that sent/discovered the bouncing email, I know for a fact it wasn't working.
Convert the failure time to Pacific time by subtracting 7 hours, i.e. 18:17 minus 7 hours = 11:17 Pacific time. Bret's post was at 12:27 Pacific time. The first email that made it through, after ICANN fixed it, was at 15:20 -0700 (i.e. Pacific time zone).
Thus we have the message failure at 11:17 Pacific time, Bret's post at 12:27 Pacific time, and the first successful comment at 15:20 Pacifc time. The question "how come that George Kirikos has left two comments before the time you've put in your blog" obviously has a fatal flaw in it.
When ICANN Board Members can't do simple timezone math, the staff doesn't have to worry very much about scrutiny of the Budget math...