-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not collecting likers at all #169
Comments
I have the exact same problem. It's across all my twitter accounts & started yesterday (29th June 2023) |
having the same exact issue too |
Having the issue as well. |
Also having the issue. |
Also having this issue. It also stopped blocking accounts I already had in cue as well. |
same here. looking into the network-tab of my debugger i saw that the twitter api did not want to answer the calls requesting details about the tweet. seems like they are expecting a little more auth since a few hours/days. |
Same issue under Firefox 114.0.2/Windows 11. Weirdly in the background the data is properly fetched. |
same here in edge |
Same issue, Microsoft Edge - Version 114.0.1823.58 (Official build) (64-bit) running on openSuse |
Is this to do with the latest round of Elon fuckery on twitter? The rate restriction for example? |
I think so. Calls to https://api.twitter.com/1.1/statuses/show.json?id=$tweetid <-- replace by a tweetid |
Same for me. It doesn't collect handler names, although I can see it's scrolling down. |
@dmstern are you still working on this extension? |
same issue here, been waiting for it to get fixed for weeks now, any news? |
This userscript works for me to mass block a tweet's likers: https://github.com/E011011101001/Twitter-Block-With-Love/ |
Noticed that blocker stoped collecting likers when clicked on block all. What to do?
![image](https://private-user-images.githubusercontent.com/72319020/250085272-b780efee-1256-4ffe-a0c0-4e9415d99067.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA0NzQ5NjksIm5iZiI6MTcyMDQ3NDY2OSwicGF0aCI6Ii83MjMxOTAyMC8yNTAwODUyNzItYjc4MGVmZWUtMTI1Ni00ZmZlLWEwYzAtNGU5NDE1ZDk5MDY3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzA4VDIxMzc0OVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTBjZWJiZjk2MGI4OWZhNGE1YzY4OTQ0ZTBlMDE2MjQ5Nzk1NjVlODE3ZjE0Y2Q0MTBiNDkyMjEwYzhjMjNhMzEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.gWIybUuUlFUZFLkC1P3pB7CILdZ0qN7LT56VrUL6HI0)
Tried on numerous tweets and it is the same.
The text was updated successfully, but these errors were encountered: