Does anyone know if there are plans to implement any methods to aid in
decreasing the number of api calls necessary for conversation
aggregation?

Even just statuses/:id/replies_to would be a nice start, though
there's room for more growth, here.

A conversation_tree method which returned all statuses downstream from
a given status (and if it is itself in reply to another status, we
suppose) would be really nice, though there are probably scale
problems with a method that could vary drastically in the complexity
and size of its returns.

Reply via email to