convore.json/groups/json/dates-and-times/messages.json

[{"user_id": 1, "stars": [], "topic_id": 11227, "date_created": 1299473427.9024701, "message": "I go back and forth between representing it as a string, and just using epoch time", "group_id": 5999, "id": 285660}, {"user_id": 1, "stars": [], "topic_id": 11227, "date_created": 1299473415.846981, "message": "How do you handle this?", "group_id": 5999, "id": 285659}, {"user_id": 4935, "stars": [], "topic_id": 11227, "date_created": 1299473532.0970869, "message": "I use strings, but I would consider using epoch time.", "group_id": 5999, "id": 285664}, {"user_id": 22997, "stars": [], "topic_id": 11227, "date_created": 1300639070.4958949, "message": "I also use strings to represent date/time. I find the added benefit of (human) readable documents to be worth the extra parsing step.", "group_id": 5999, "id": 392544}, {"user_id": 4935, "stars": [], "topic_id": 11227, "date_created": 1300674033.522893, "message": "yeah, it's nice", "group_id": 5999, "id": 394830}, {"user_id": 4935, "stars": [], "topic_id": 11227, "date_created": 1300674117.194649, "message": "it uses the fact that \"\\/hi\\/\" and \"/hi/\" are equivalent to achieve bulletproof serialization...misses the point imo", "group_id": 5999, "id": 394835}, {"user_id": 4935, "stars": [], "topic_id": 11227, "date_created": 1300674049.9959891, "message": "not a fan of Microsoft's JSON date/time representation", "group_id": 5999, "id": 394831}]