Hi Matt,
The id from the search system is different from the main Twitter system. We're still working on merging the search system into the main Twitter back-end and that's one of the big things to get fixed. Unfortunately, I don't think that fix is going to be very soon. We're nearing our first major milestone in the transition and after that I can hopefully get some information on exactly when we'll be done. If anyone is interested in the history of this, here goes. Search was built as summize.com using the public Twitter data. When Summize started with that data feed didn't include the user id, so Summize had to generate one. Once the user id was added to the data feed the system was taking quite a bit of traffic and it was decided to keep the old id's rather than spend the time to convert. At the time, that would have meant the whole company working for 3-4 days to convert it without downtime, you can see why we kept it. This id in the API has always bugged me so it's one of my top priorities when it comes to merging the systems. Once I know more I'll send something out to the list.
Thanks; Matt Sanford (@mzsanford) On Nov 21, 2008, at 02:38 PM, matt.lubner wrote:
When parsing results from the Search API, the "from_user_id" does not seem to be the correct numerical id of the user who posted the tweet. I'm fairly sure this is not the correct place to file a bug report, so if someone could point me in the correct direction, it would be much appreciated! Also, does anyone know what the turnaround time would be for a fix? This bug is currently preventing my app from being launched. :\ Thanks, Matt Lubner
