Comments on: #fixreplies hack – shows what Tweets you’re missing

By: MrBlog

MrBlog — Thu, 01 Oct 2009 20:28:31 +0000

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.

By: follower

follower — Fri, 25 Sep 2009 09:57:47 +0000

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.

–Philip.

By: MrBlog

MrBlog — Thu, 17 Sep 2009 17:26:02 +0000

@follower I don’t see how this is possible. It’s just a static HTML file and Javascript. It’s got to be something else triggering the “credentials” request. Can you send a screenshot? Are you loading the HTML file from mrblog.org or a copy on your own host?

By: follower

follower — Mon, 14 Sep 2009 07:20:30 +0000

Hi,

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.

–Philip.

By: MrBlog

MrBlog — Sun, 24 May 2009 16:19:27 +0000

I hacked up “since_id” support – no auto-refresh, but that would not be too hard to add.

By: Mr Blog » Blog Archive » Twitter #fixreplies fiasco is telling

Mr Blog » Blog Archive » Twitter #fixreplies fiasco is telling — Wed, 20 May 2009 16:23:49 +0000

[...] see the whatumissed hack for a way to see these missed replies again: http://mrblog.org/whatumissed.html Subscribe to the [...]

By: MrBlog

MrBlog — Tue, 19 May 2009 22:33:11 +0000

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 “

By: MrBlog

MrBlog — Tue, 19 May 2009 21:58:51 +0000

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.

By: ups

ups — Tue, 19 May 2009 20:20:26 +0000

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!

By: MrBlog

MrBlog — Tue, 19 May 2009 19:21:13 +0000

Ups,

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.