Opened at 2010-04-19T12:23:05Z
Closed at 2015-05-05T14:57:00Z
#597 closed enhancement (fixed)
Search channel support for Twitter
| Reported by: | Owned by: | geert | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Version: | 1.2.6 | |
| Keywords: | patch | Cc: | |
| IRC client+version: | Client-independent | Operating System: | Public server |
| OS version/distro: |
Description
tircd has this nice feature of displaying updated search results in a seperate channel, by /j #tag and /topic #tag #tag:
If you want to have updated search results for a specific term delivered, you can /join <any channel> then set the /topic for the channnel to your search query. Results that match that query will be sent to that channel. The /topic can be almost anything supported by the twitter search (see http://search.twitter.com/operators for exmaples). Using the 'near' option is not currently supported.
This would be cool in BitlBee, too.
Attachments (4)
Change History (31)
comment:1 Changed at 2010-06-09T22:06:47Z by
comment:4 Changed at 2011-08-10T06:46:10Z by
maybe through a /query <search> inside the #twitter_channel?
comment:6 Changed at 2011-08-27T10:30:04Z by
Sorry guys, this really isn't going to happen any time soon. The search API call is JSON-only and BitlBee uses XML. I'm not going to add a JSON dependency any time soon so for now this is impossible.
Actually https://dev.twitter.com/docs/api/1/get/search shows that it supports JSON and ... ATOM. That's not very useful either though.
comment:7 Changed at 2011-10-14T11:09:51Z by
According to https://dev.twitter.com/discussions/1765 ATOM is XML based and should be parse-able as XML
comment:8 follow-up: 14 Changed at 2011-10-14T15:38:56Z by
Yes, I know. Not going to happen. That's a nice hack for getting that stuff into an RSS reader. The last thing this code needs is a completely separate parser for a lossy compatibility format, just for searches.
comment:9 Changed at 2011-10-15T17:29:31Z by
awww, this would be cool. and json is really trivial to parse, we can probably roll our own (or someone else's) to avoid any outside dependency.
remember what randall said! ;)
comment:10 Changed at 2011-12-04T12:12:12Z by
Could saved searches be added? These both use XML.
https://dev.twitter.com/docs/api/1/get/saved_searches
https://dev.twitter.com/docs/api/1/get/saved_searches/show/%3Aid
comment:11 Changed at 2012-02-12T14:29:55Z by
wilmer: Any opinion on the saved searches as posted in comment 10?
comment:12 Changed at 2012-06-30T11:41:01Z by
Sitting at Akademy 2012 and would really like to /join #akademy on bitlbee right now. Yes I know, PatchWelcome. :>
Changed at 2012-12-23T15:46:35Z by
| Attachment: | bitlbee-tracking-channels.patch added |
|---|
twitter search channels patch
comment:13 Changed at 2012-12-23T15:52:18Z by
Here's the patch I'm currently using for twitter "search" channels. works only with hashtags, not normal searches.
Usage:
> chat add twitter #hashtag > /j #hashtag
It probably needs some tweaking and there are quirks that I'm not sure how to work around (e.g. having to rejoin every channel after acc off/acc on). But if someone wants to test it here you go. You have to have JSON, i.e. bzr revision 951 or later to apply this.
Changed at 2013-01-16T11:35:34Z by
| Attachment: | bitlbee_tracking_channels_r965.patch added |
|---|
version with a couple of fixes that applies cleanly to bzr965
comment:14 follow-up: 15 Changed at 2013-08-01T21:14:16Z by
Replying to wilmer:
Yes, I know. Not going to happen. That's a nice hack for getting that stuff into an RSS reader. The last thing this code needs is a completely separate parser for a lossy compatibility format, just for searches.
Why not add an optionnal dependency?
comment:15 follow-up: 16 Changed at 2013-08-01T21:34:45Z by
The point you're responding to is no longer relevant, since BitlBee now uses JSON for Twitter - any other flavours of the Twitter API are no longer supported.
comment:16 Changed at 2013-08-06T12:18:05Z by
Replying to wilmer:
The point you're responding to is no longer relevant, since BitlBee now uses JSON for Twitter - any other flavours of the Twitter API are no longer supported.
Does this mean that since your original argument for not implementing it is now gone, we will get this feature? :)
comment:17 Changed at 2013-08-08T07:36:20Z by
Indeed. There's a patch in this bug already, even. I just haven't had a chance to look at it yet, and am thinking of whether the UI for it works the way I want it to..
comment:19 Changed at 2013-12-07T10:03:34Z by
I'd (still) love this, too. Also, lists should probably also be possible like this, no?
comment:20 Changed at 2014-02-04T06:51:34Z by
| Keywords: | patch added |
|---|
comment:21 follow-up: 22 Changed at 2014-02-26T01:59:43Z by
Is there an updated patch available for those who would like to try this on the most recent builds?
Changed at 2014-02-26T07:53:13Z by
| Attachment: | bitlbee_tracking_channels_r1010.patch added |
|---|
comment:22 follow-up: 25 Changed at 2014-02-26T07:53:45Z by
comment:25 Changed at 2014-12-21T05:30:24Z by
Replying to Artem Savkov <artem.savkov@…>:
Replying to FiXato@…:
Is there an updated patch available for those who would like to try this on the most recent builds?
Heres a r1010 rebased patch.
Sorry for the belated thanks. Thanks! :P Since we're now on 1070, and this still hasn't seem to have made it into the repo (afaik at least), is there any chance for an updated patch?
Changed at 2014-12-24T18:33:00Z by
| Attachment: | jgeboski_tracking_channels_r1060.patch added |
|---|
Whole new patch to do tracking channels by jgeboski, fixing many of the issues of the old one and adding more features
comment:26 Changed at 2014-12-24T18:48:53Z by
jgeboski's description of the patch:
[PATCH] twitter: implemented filter based group chats
Filter group chats allow for the ability to read the tweets of select users without actually following the users, and/or track keywords or hashtags. A filter group chat can have multiple users, keywords, or hashtags. These users, keywords, or hashtags can span multiple group chats. This allows for rather robust filter organization.
The underlying structure for the filters is based on linked list, as using the glib hash tables requires >= glib-2.16 for sanity. Since the glib requirement of bitlbee is only 2.14, linked list are used in order to prevent an overly complex implementation.
The idea for this patch was inspired by Artem Savkov's "Twitter search channels" patch.
Usage:
In order to use the filter group chats, a group chat must be added to the twitter account. The channel room name is either follow:username, track:keyword, and/or track:#hashtag. Multiple elements can be used by separating each element by a semicolon.
Main difference with the older patch is that this one allows both follow and track channels, where track channels aren't restricted to hashtags only, and tracking channel users aren't added to the blist permanently (they were leaking), or joined to the channel (no more join spam)
Applies cleanly to bzr revisions 1011-1060, including the 3.2.2 release.
comment:27 Changed at 2015-05-05T14:57:00Z by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
This is now applied and is part of the 3.4 release, see the "filter channels" section of https://wiki.bitlbee.org/HowtoTwitter for usage instructions
http://code.google.com/p/tircd/
http://github.com/abramhindle/tircd-plus-search/blob/master/tircd.pod
Check how they implement search. Topic based or channel name based.