I would guess something like: your client has downloaded part of the feed containing two fragments of the same conversation.
-
-
-
You mute one & scroll to the other, where you try to mute it again. It queries the server & finds the convo is already muted, shows "unmute"
-
"Mute" seems full of annoying bugs like this. Not a well thought through feature.
End of conversation
New conversation -
-
-
I have no idea how any of this works. The only thing that consistently applies seems to be blocks. Thank jeebus.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.