I’m creating a bot posting a tweet thread using the V2 API. This is done by using the id in the following tweet using the in_reply_to_tweet_id property.
This thread works fine on desktop, but when viewing it on the mobile app the replies show as “This Tweet is unavailable” in what seems quite random.
You can see the thread here at post: bbctelescope/status/1484715256257683460
then try to load it on mobile or in a private browser, and some of the tweets don’t work.
If I try to create the tweets using the UI, it works without any problems, so I’m thinking it is something API related.
Any obvious i am missing?
1 Like
I think this is more of a new account and anti spam thing - I don’t think it’s anything you’re doing wrong because the thread looks like it worked
1 Like
fair enough - weird that it is a different behaviour if I use the API vs the UI though? I’ll leave it running for a few days and see if over time it gets better. thanks!
1 Like
This is still happening 
Why would this be, some screenshots are attached to show what I’m experiencing…
1 Like
I am also facing this issue, can someone from Twitter confirm if this is indeed spam prevention? If so, how old an account should be so that this doesn’t happen?
Thread posted via API: /notHackerNews/status/1520432807738494976
Thread posted manually: /notHackerNews/status/1520447099967803393
1 Like
