well I almost fixed @digital_henge finally except twitter apparently nixed timeliness for duplicate tweet so it's rejecting a tweet identical to one from may 2017
it's entirely possible the account/app has gotten into a bad state somehow, as evidenced by its tweet history it previously worked fine
-
-
incidentally a few years ago twitter would consider a "reply" to be a new tweet even with the same content
-
this was definitely before new reply system/handle-stripping, pooossibly before threading, not sure how this would work now but
-
I would dodge duplicate tweet restrictions by throwing an arbitrary tweet id I was "replying" to in the payload and it'd let me duplicate and be completely invisible to non-api viewers
- End of conversation
New conversation -
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.
ˢⁿᵉᵉᵏʸ