IncludeEntities deprecated but still necessary?

Jun 10, 2012 at 3:03 PM
Edited Jun 10, 2012 at 3:04 PM

Am I doing something wrong?

The following code returns 4 tweets (as it should) that contain hashtags

 

            var statusTweets =
                from tweet in twitterCtx.Status
                where tweet.Type == StatusType.User
                      && tweet.ScreenName == "ChrisSlee"
                      && tweet.IncludeEntities == true
                      && tweet.Entities.HashTagMentions.Count > 0
                select tweet;
This code returns no tweets..
            var statusTweets =
                from tweet in twitterCtx.Status
                where tweet.Type == StatusType.User
                      && tweet.ScreenName == "ChrisSlee"
                      //&& tweet.IncludeEntities == true
                      && tweet.Entities.HashTagMentions.Count > 0
                select tweet;

 

Coordinator
Jun 10, 2012 at 11:24 PM

Hi,

Twitter had planned to deprecate include_entities (IncludeEntities in LINQ to Twitter), but postponed the deprecation.  Here's the original post:

https://dev.twitter.com/blog/api-housekeeping

At the bottom of the post, they indicate the postponement.

So, you still need to add IncludeEntities to get this to work.  I'm aware that LINQ to Twitter still gives you a compiler warning and that's uncomfortable.  My dilemma is in the uncertainty of the Twitter deprecation schedule, whether to change LINQ to Twitter not knowing whether Twitter will change tomorrow or months from now.

Right now, if you have a work-aroung, I'd ask to please use that for right now.  If you run into something that can't be worked-around, let me know and I'll think about the best way to handle it.

Joe

 

Jun 11, 2012 at 1:37 PM

Great! Thanks Joe.  

I appreciate all the work you have put into Linq to Twitter.  It has saved me countless hours of time and I wanted to say thinks.


Chris