Seems like part of this could've been prevented by just tweeting with (1/) or (2/) in the beginning of multi-tweet posts.