userscripts icon indicating copy to clipboard operation
userscripts copied to clipboard

Twitter Reply Count - no longer works

Open darkred opened this issue 4 years ago • 3 comments

Greetings

I've noticed that the 'Twitter Reply Count' script no longer works, i.e. there's no reply count e.g. for the test URL of the description screenshot: https://twitter.com/TwitterSupport/status/1150813610370748416 (open the URL in new tab and click the timestamp link if you have login)

Tweet screenshot

2021-01-10_003226

There's no error in Console. Tested in fresh profiles of Chrome 87/Firefox 84 with latest TM beta/VM beta, having login to Twitter or not.

Thank you


PS. I can't help but mention that there's a "report" of this issue in the Greasyfork page : lazy, one-sentence (plus Hi and Please!!), and with a Bad rating on top, instead of No rating - just a question/comment. The same friggin annoying thing with most of "issue reports" in GF... Combined with hit-and-run clueless "Bad" reviews all over... (I've posted my suggestions about that in Greasyfork Github repo..)

darkred avatar Jan 09 '21 22:01 darkred

I'd like to note that if you open the above tweet URL while having login to Twitter, then by default(=without the script) the reply count appears ok (825) but it's just numbers, there's no accompanying text:

Screenshot

2021-01-11_200140

If you click its timestamp link then you get the screenshot of the OP.

darkred avatar Jan 11 '21 18:01 darkred

The text/label is needed and is no longer attached to the tweet.

I have a workaround which is working locally, but it requires a new dependency which isn't ready for release (and which has several other dependencies which I should also release). So you'll have to enjoy the non-drama of not knowing for a while...

Note: I de-listed the script on Greasy Fork months ago when Twitter stopped exposing the stats:

twitter-reply-count

chocolateboy avatar Jan 11 '21 18:01 chocolateboy

Thanks for replying.

I'm glad you have a workaround. I wrote this issue guessing that Twitter has probably made it impossible for the script to work again.

And that "Bad" rating... You see, I've also written various userscripts, and such "ratings" on GreasyFork never cease to annoy me.

darkred avatar Jan 11 '21 18:01 darkred