convore.json/groups/convore-api-developers/tracking-in-topics-and-groups-payload/messages.json

[{"user_id": 1, "stars": [], "topic_id": 21683, "date_created": 1303930009.3929479, "message": "Ohhhh", "group_id": 2780, "id": 830075}, {"user_id": 1, "stars": [], "topic_id": 21683, "date_created": 1303929951.0581031, "message": "haha", "group_id": 2780, "id": 830062}, {"user_id": 1706, "stars": [], "topic_id": 21683, "date_created": 1303929925.5788331, "message": "I swear, convore must be the only app who's basic resty API lags behind the live stream :-)", "group_id": 2780, "id": 830058}, {"user_id": 1706, "stars": [], "topic_id": 21683, "date_created": 1303930361.548008, "message": "and flips appear in live - you get a read followed by a flip of the tracked state", "group_id": 2780, "id": 830190}, {"user_id": 1706, "stars": [], "topic_id": 21683, "date_created": 1303930424.74404, "message": "imho", "group_id": 2780, "id": 830221}, {"user_id": 1, "stars": [], "topic_id": 21683, "date_created": 1303929969.7302611, "message": "Is this what you're looking for? https://convore.com/api/#track", "group_id": 2780, "id": 830067}, {"user_id": 17897, "stars": [], "topic_id": 21683, "date_created": 1303930306.3510261, "message": "does the track api flip the tracked state?", "group_id": 2780, "id": 830153}, {"user_id": 1706, "stars": [], "topic_id": 21683, "date_created": 1303930329.30351, "message": "@adsworth yes", "group_id": 2780, "id": 830168}, {"user_id": 1706, "stars": [], "topic_id": 21683, "date_created": 1303930000.115098, "message": "nope - tracking: true/false when fetching the list of groups or topics", "group_id": 2780, "id": 830073}, {"user_id": 1706, "stars": [{"date_created": 1303930205.189106, "user_id": 1}], "topic_id": 21683, "date_created": 1303930022.7403269, "message": "hence my quip", "group_id": 2780, "id": 830078}, {"user_id": 1, "stars": [], "topic_id": 21683, "date_created": 1303930550.2897761, "message": "@protocool OK tracked status should appear in the API now.", "group_id": 2780, "id": 830275}, {"user_id": 17897, "stars": [], "topic_id": 21683, "date_created": 1303930403.160418, "message": "the read doesn't really make sense, or does it?", "group_id": 2780, "id": 830204}, {"user_id": 1706, "stars": [], "topic_id": 21683, "date_created": 1303930423.4191401, "message": "if you have 5 unread and flip from tracked to not-tracked, clearing read makes sense", "group_id": 2780, "id": 830220}, {"user_id": 1706, "stars": [{"date_created": 1303930679.833921, "user_id": 1}], "topic_id": 21683, "date_created": 1303930671.0632329, "message": "thanks @ericflo - but you need to become more responsive. Entire minutes between a request and implementation is simply unacceptable.", "group_id": 2780, "id": 830350}, {"user_id": 17897, "stars": [], "topic_id": 21683, "date_created": 1303931572.7292211, "message": "@protocool clearing the read makes sense. but publishing that in the live api doesn't imho.", "group_id": 2780, "id": 830815}, {"user_id": 17897, "stars": [], "topic_id": 21683, "date_created": 1303931593.7618041, "message": "I didn't read the topic, so it shouldn't send a read message", "group_id": 2780, "id": 830824}, {"user_id": 1706, "stars": [], "topic_id": 21683, "date_created": 1303933753.7132051, "message": "@adsworth I guess it boils down to whether you think it's reasonable behavior that in the HTML UI when you hit the pause button, any existing unread count (for whatever you're pausing) disappears. The 'read' in live preserves that state across all clients.", "group_id": 2780, "id": 831517}, {"user_id": 17897, "stars": [{"date_created": 1303937749.140532, "user_id": 1}], "topic_id": 21683, "date_created": 1303933968.9860809, "message": "@protocool OK, I'm sold. It does make sense. :)", "group_id": 2780, "id": 831555}]