| Commit message (Collapse) | Author | Age | Lines |
|---|
| | |
|
| |
|
|
|
| |
Difficult because there's no bee_user struct pointing at the user themselves
so instead just fake one for very limited use.
|
| |
|
|
|
|
|
| |
Used uncrustify, with the configuration file in ./doc/uncrustify.cfg
Commit author set to "Indent <please@skip.me>" so that it's easier to
skip while doing git blame.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
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.
|
| |
|
|
|
| |
really should be enough.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
fixed URL and tried to parse individual JSON objects. Not doing anything
useful with it.
|
| |
|
|
|
|
| |
HTTP failures caused by (most likely) DNS resolution problems. Yes, ignoring
return values is still bad, kids!
|
| |
|
|
|
|
| |
don't know exactly how BitlBee gets into it. Any more info from people who
see this problem often would be useful.
|
| | |
|
| |
|
|
|
|
| |
list of contacts at login time. Still depends on adding an API version number
to base_url though.
|
| |
|
|
|
|
| |
since Twitter can't seem to make up their mind on the formatting of their
error responses, sometimes using XML and sometimes plain text.
|
| | |
|
| |
|
|
|
| |
to do: Document the feature and allow using the numbers in rt/replies.
|
| |
|
|
|
|
| |
This fixes a weird bug where Twitter updates often stop after a while
when running in daemon mode with multiple users connected.
|
| |
|
|
|
|
| |
this in the Twitter module to remember the id and timestamp of a contact's
last tweet, which can later be used for simple replies/retweets.
|
| |
|
|
|
| |
either your most recent tweet, or a specific id (pass it as an argument)).
|
| |
|
|
|
|
|
|
|
|
| |
name with that service name, not always Twitter. This is especially useful
when having multiple accounts on different sites with the same username.
Also adding an "identica" protocol entry for convenience.
Based on a patch from kensanata, bug #648.
|
| |
|
|
|
|
| |
instead of adding contacts as they post tweets. Also in mode=chat, populate
the channel *before* adding the user to it, avoiding a flood of joins.
|
| |
|
|
|
| |
Twitter API can be used. Only with Basic authentication though.
|
| |
|
|
|
|
| |
Keep it in the Twitter module, and use the oauth_info struct through the
whole session to keep all this together.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Twitter's tricky. It returns vars (user_id, screen_name) in the access token
that, the way I read the spec, should be included in all subsequent queries.
However, stuff only started to work when I dropped those vars.
This code's definitely not pretty ATM. Need to clean up now that it actually
works.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
