Ok, I got the info from jamie in chat and for a message that Jamie generated on 2014-04-24T11:44:56.000 New Zealand time, so 2014-04-23T23:44:56.000Z (UTC) this code generated:

```
messagetext: "test one for cheddar"
parentmessage: null
timestamp: "2014-04-23T11:44:56.000Z"
```

The old code correctly generated the timestamp of the event in UTC.  This new code appears to be trying to fudge the timestamp to look like the timezone'd time with an erroneous UTC timezone identifier on it.  Our messages should be storing the exact time of the event (i.e. the way the code was before), so I do not believe that there is any problem with clamshell.