You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I updated rtweet and RStudio after my Twitter API was being picky (meaning, taking forever to load). Tweetbotornot worked for one round, but then I started receiving 404 Errors.
I checked a sample of the usernames and I got the 404 error — which is weird because when I manually looked up those usernames, they all existed. At first, I thought it was an API error. But when I tried it with a different API, it still didn't work. And that API token also worked with typical rtweet functions.
So now I can't help but wonder if it's some sort of package error. I am a bit new to scraping Twitter so perhaps this makes zero sense, but I'm slightly desperate for answers. Given the rtweet update, I thought there was a chance this could make sense.
The text was updated successfully, but these errors were encountered:
The package hans't been updated in 2 years.
After rtweet update, this package needs some serious update not only connect to rtweet, but to the new format of Twitter API data.
I forked the project to try and do this update to get it working with the new API format.
I updated rtweet and RStudio after my Twitter API was being picky (meaning, taking forever to load). Tweetbotornot worked for one round, but then I started receiving 404 Errors.
I checked a sample of the usernames and I got the 404 error — which is weird because when I manually looked up those usernames, they all existed. At first, I thought it was an API error. But when I tried it with a different API, it still didn't work. And that API token also worked with typical rtweet functions.
So now I can't help but wonder if it's some sort of package error. I am a bit new to scraping Twitter so perhaps this makes zero sense, but I'm slightly desperate for answers. Given the rtweet update, I thought there was a chance this could make sense.
The text was updated successfully, but these errors were encountered: