Does anyone who uses the twitter API know what the deal is with the created_at field for the user object? According to the data, 1574 of my last 5k followers— including people I've known on here for years—created their accounts today.
Conversation
Replying to
I see the same thing for my user name using rtweet::lookup_users(). created_at is today, but the additional field account_created_at is correct.
1
1
Replying to
Interesting, that might solve it. The API docs say created_at should be when the account was created, but I guess not? developer.twitter.com/en/docs/tweets
2
created_at under the user object was historically always when the account was created. If you're saying that has changed and it now reflects different data, that's going to screw up a lot of analysis code.
I don't think that has changed. Just pointing out that there's a second created_at under status, which may or may not be relevant to the issue.
1
Yeah, it turns out rtweet renames the created_at field so it doesn’t conflict with the tweet’s created_at field that is also returned in the user object
1
2
Show replies