UPDATE May 18 2009: fixed some bugs, removed Twitter API rate limit issues, and simplified usage to one simple HTML file
I put together a little hack that shows the tweets you’re no longer getting.
Basically, it produces output like the following, showing the @reply tweets you didn’t see in your Twitter stream becaue you don’t follow the person the message is directed to. In my case, it showed me 63 interesting tweets tonight. The output is something like this:
Each entry is shown with a link to the original Tweet on Twitter so you can click to get the full details of the tweet.
How to use it
It is all in one HTML file: whatumissed.html.
You can copy and paste the above into a local file on your computer and open in your browser, or simply execute the version at mrblog.org directly (and “View Source” to see how it works):
- It should be pretty easy to turn off the diagnostic data if you like by using
visibility: hiddenfor the “statusmsg” div in the html/script.
- There is no little CSS or other styling here – if you hack the code with cool CSS styling, please post back to me so others can benefit too.
- If you make other hacks to this code, or have other suggestions for me, please let me know.
I don’t understand. If they are @replies, they show up. But your image isn’t showing @replies – not sure what this program is supposed to be finding.
I tried it, but I think it failed. i never got the Twitter icons you show. I got something like this:
myFriends = 11965332 screen_name: ChrisSpagnuolo
found @ reply: ‘ChrisSpagnuolo: @BertDecker Thanks Bert.’
adding ‘ChrisSpagnuolo: @BertDecker Thanks Bert.’ to results
found @ reply: ‘ChrisSpagnuolo: @TheStickMonkey @dcardella @mediaman64 @karmakimmie Thanks for iPhone app recco’s.’
In the past, when people you follow posted a tweet, those tweets would appear in your updates at http://twitter.com/home (or API /statuses/friends_timeline).
Last week, twitter changed things so that you no longer see tweets posted by the people you follow that are deemed to be “replies” to someone you do not follow. See this post for a more in-depth explanation: http://mrblog.org/2009/05/14/twitter-fixreplies-fiasco-is-telling/
The “whatumissed” hack shows the tweets that Twitter isn’t showing you anymore. As to why it’s not working for you, let us know the browser you’re using.
You might also try the version on the site here directly and ee if that works: http://mrblog.org/whatumissed.html
This is a great piece of software! Just 2 suggestions (I’ve not checked the code, so I have no idea if it is possible) 1) Grab “in reply to” link. 2) Recognize URLs and make them a link.
Thanks. (2) is now done, thanks to some code from Simon Whatley
It turns out the search API doesn’t provide “in reply to” so in order to show an “in reply to” link, it would require an additional API call per tweet, which would probably run a pretty big risk of hitting API limits – so I will leave an “in reply to” link hack as an exercise for the reader.
Thanks for the reply MrBlog.
The “in reply to” would be difficult since it would rapidly hit the API count limit. It’s on twitters API roadmap but until then, no luck. http://apiwiki.twitter.com/V2-Roadmap
I know that is not intended to replace Twitter but I’m finding myself to use it a lot!
One enhancement I would like to try to implement: Auto-refresh with since_id parameter! 🙂
Auto-refresh with since_id should be doable.
In terms of it becoming a real client, what would be really cool is as a greasemonkey script for the normal twitter.com site, but that would be a pretty large task.
Perhaps a version that shows the full stream does make sense though, even in this somewhat crude form, jumping to twitter for other actions, etc. – in other words, not replacing all of Twitter.com but just an alternative “home” screen.
One trick with an “Auto-refresh” by the way is you probably need to reload the script with a since_id parameter passed int he url or something due to the way the code works by adding new “
[…] see the whatumissed hack for a way to see these missed replies again: http://mrblog.org/whatumissed.html Subscribe to the […]
I hacked up “since_id” support – no auto-refresh, but that would not be too hard to add.
I’ve been using this since I discovered it a few weeks ago, but as of about a week ago it seems to be asking for Twitter API credentials and doesn’t seem to work without them.
Thanks for your work on this.
Thanks for your reply (which I missed until just now :).
I’ve discovered the issue is a change to the API functionality as listed on September 10, 2009 on http://apiwiki.twitter.com/REST-API-Changelog which says “Fixed (REST): statuses/friends, statuses/followers, friends/ids, and followers/ids for protected users require proper authentication.”.
I’m a user with non-public/protected updates so the page will no longer work for me unfortunately, without logging into the API page. If I do that it works. But ideally I don’t want to do that for an HTTP link, but I’m not sure if changing the URL in your code to HTTPS will work or not.
Yeah @follower, all bets are off if for accounts with non-public/protected updates. I forget that some people even have protected accounts on Twitter.