Conversation

Can't tell if it's deliberate or not, but it looks like implicit threads (replying to yourself, 1 tweet at a time) have a broken display now, especially if others reply too. Not sure if using the thread-composition interface preserves it.
6
17
If I'm right, new display logic is chronological or something and does not privilege author's own replies, but composing a thread all at once before tweeting should do better...
2
4
Yep, threading does not break if you use the threading interface, ensuring that your own replies are the first. Could someone try replying to THIS tweet? I'll only reply after a couple of other replies come in, to test my breakage theory.
5
4
Okay that worked. Could be that thread logic, once established, prevails. Or some random mix of thread logic, account size of replies, bluecheck status etc. etc. I would not bet on threading UX being preserved given the longform-attachment type plans.
2
3
Replying to
Don’t quote me on this, but I think if indexing is running slower than usual you’ll get weird threading issues until the skiplists are updated. May be indicative of some issues downstack.