Read-until is naturally stored with, or in relation-to, the User object. Due to temporary infrastructure limitations, that is database issues, it's not really feasible to add additional high-velocity columns on Users for a little while. Once this limitation is sorted out, the Platform team can do all sorts of interesting things. There's a whole team of folks dedicated to working on this infrastructure.
-John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Fri, May 14, 2010 at 5:48 AM, Raffi Krikorian <ra...@twitter.com> wrote: > annotations are immutable along with the tweet. you create annotations when > you create a tweet, and they are stored with that tweet. > > On Fri, May 14, 2010 at 12:37 PM, janole <s...@mobileways.de> wrote: >> >> Wouldn't that be something for the upcoming Annotations? >> >> Ole >> >> -- >> Jan Ole Suhr >> s...@mobileways.de >> On Twitter: http://twitter.com/janole >> >> >> On 14 Mai, 12:45, Raffi Krikorian <ra...@twitter.com> wrote: >> > Love the idea - pretty hard to do. Want to doit. Not sure when :p >> > >> > On Friday, May 14, 2010, Adam <v0id....@gmail.com> wrote: >> > > I'm not sure if this has been asked before, but I was wondering about >> > > the inclusion of a "read/unread" field included with a status. So many >> > > applications conduct their own methods of knowing whether a tweet has >> > > been read, but it would be really good if this could be unified on >> > > Twitter. I'm not completely sure how it would work, maybe have a new >> > > API function to set the "read/unread" status, and tweets seen on >> > > Twitter.com itself would never set this status, only applications >> > > would use this function. >> > >> > > This is just an idea though, what do you think? >> > >> > -- >> > Raffi Krikorian >> > Twitter Platform Teamhttp://twitter.com/raffi > > > > -- > Raffi Krikorian > Twitter Platform Team > http://twitter.com/raffi >