Another thought. Are you feeding your DB with normal API endpoints
and the search API endpoint? The search API returns different
user_ids. http://dev.twitter.com/doc/get/search
http://code.google.com/p/twitter-api/issues/detail?id=214
--
Twitter developer documentation and resources:
That is the problem. User ID's are not suppose to change, though in
our DB we see the same screen name with a different User ID. Of the
5,000 users in the DB, some have 6 ID's, a few have 5, 4 and 3 ID's
but many have 2 User ID's. We are talking 5,000 users being affected
of 5 million users in our
Right. But here's the scenario:
User ID 1 has screen name foo
You load user ID 1's data.
User ID 1 decides that foo is a silly screen name and changes it to bar.
A new user, ID 10 signs up and decides that foo is an awesome screen name.
You load user 10's data.
So the important question: if
