twitter: responses tab should merge info from both replies.json and search

Bug #311899 reported by Dominic Evans
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gwibber
Fix Released
Low
Unassigned
1.0
Fix Released
Undecided
Unassigned

Bug Description

Since revision #153 (http://bazaar.launchpad.net/~segphault/gwibber/webkitui/revision/153) gwibber moved to using the replies.json feed to populate the responses tab with twitter replies, instead of the old method of searching for @username. This was needed as the twitter search API results don't currently contain the 'in reply to' information that the tweets themselves contain (I've raised a bug about this with the search API team)

However, as a result of this change, we now miss any tweets that don't start with @username (i.e. those that aren't marked as replies to you specifically). Therefore, to solve this issue, we should also perform a twitter search for '@username -to:username' to pick up those tweets that reference you but aren't specifically marked as replies to you. We should then merge the lists holding the results of these two sources (sorting by tweet id or time), trim the resulting list to the desired overall size, and then display.

This solution allows us to keep the in reply to links for responses specifically to us, but prevents us from missing out on tweets we wouldn't have seen otherwise.

For an even better solution we could add an 'in reply to ...' clickable link, that when clicked will request the info about that tweet id from the twitter api (which will have any reply_to information in it) and replace the ... with an appropriate link.

Dominic Evans (oldmanuk)
Changed in gwibber:
assignee: nobody → oldman
status: New → Confirmed
Dominic Evans (oldmanuk)
Changed in gwibber:
importance: Undecided → Low
Dominic Evans (oldmanuk)
Changed in gwibber:
milestone: none → 1.0
Revision history for this message
Dominic Evans (oldmanuk) wrote :
Changed in gwibber:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.