| 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.
|
|
|
|
| |
Also, fix bug in parsing of entities in DMs.
|
| |
|
|
|
|
|
|
| |
Commit eb4ad8d (a merge commit, yes) changed it to _last_tweet and
missed one of the three. Not entirely sure if wilmer's fault, could be
mine when I did the merge of his merge on my side. Whatever.
|
|
|
|
|
|
|
|
|
|
|
| |
- Show version as part of the initial message of &bitlbee
- Use g_strerror() to show actual errors when saving xml configs
- Only show "The nick is (probably) not registered" for ENOENT, use
g_strerror() for the rest of OS errors when loading xml configs
- Show "Protocol not found: <name>" when find_protocol() returns null,
useful when the user uninstalls a plugin accidentally.
- Suggest the user to check the system clock when getting error 401 from
the twitter stream (other REST endpoints show a better error message)
|
|
|
|
|
|
| |
Also fix the endptr condition which was backwards and resulted in every
tweet id getting rejected, but you didn't see that one, this commit
really is about the tweet id 00 which is the most important tweet id.
|
|
|
|
|
| |
Fixes issues such as parsing "reply eo" as replying to "0e",
as reported by torrancew
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
This reverts commit ce402b20d82ec323e6bd5e306de934773590742d.
See discussion in PR #10 for more details.
|
|
|
|
|
|
|
|
|
|
|
| |
Allow users to specify how tweets should be displayed
3 new settings are available to set how tweets are displayed:
- twitter_format_string for normal tweets
- retweet_format_string for retweets
- reply_format_string for replies
For full documentation see the help files
|
|
|
|
|
|
|
| |
By default, "reply" prepends the username of the tweet being replied to. This
adds support for a "rawreply" command which does not prepend this username.
This is useful for "replying" to your own tweet to maintain a chain of tweets
on a singular topic.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|\ |
|
| | |
|
|/
|
|
|
| |
This works by setting the last_tweet hidden account setting to the ID of
the last shown tweet.
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes warnings about passing signed chars to them (apparently they
are implemented as macros that do array lookups without checks in some
platforms, yay)
Specifically:
functions=isalnum|isalpha|isdigit|isspace|isxdigit|tolower|toupper
sed -ir "s/$functions/g_ascii_&/g" **/*.c
|
|
|
|
|
|
| |
Fixes a few minor bugs with users who have uppercase characters in nicks
(see trac ticket 1138). Most notably, the "follow" command showing no
feedback that a user was followed
|
|
|
|
| |
Land of the Free, Home of the Brave
|
| |
|
|
|
|
| |
Only took me a few months to write. I even added a test case.
|
|
|
|
|
|
| |
Few BitlBee-specific diffs now. Annoyingly need to link to libm now for the
use of the function pow() since the lib now does its own number parsing...
|
|
|
|
|
|
|
|
|
| |
service. https://dev.twitter.com/blog/upcoming-tco-changes #1077
Seriously guys, stop being so obnoxious. This t.co garbage lengthens pretty
much everything (that looks like a) URL at this point. Stop counting it towards
the 140-char limit.
|
| |
|
|
|
|
|
| |
used protocol version when internally handling redirects.
|
|
|
|
|
| |
longer working. (Not compatible with Twitter API 1.1 from what I can see?)
|
|
|
|
|
| |
service, and string handling fix when pretending to do this anyway.
|
| |
|
|\
| |
| |
| |
| |
| | |
XML-formatted user configs from disk I/O so we can try to start using other
mechanisms to store them (a REST API or something, for example).
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
my copyright mentions since some were getting pretty stale. Left files not
touched since before 2012 alone so that this change doesn't touch almost
EVERY source file.
|
| | |
|
| |
| |
| |
| |
| | |
API. A full list of diffs would be helpful, guys...
|
| |
| |
| |
| |
| |
| |
| | |
Twitter sends us our real username on OAuth completion, which is then used
instead of the username supplied by the user. Identi.ca doesn't supply
this info so BitlBee would instead replace td->user with a NULL pointer.
|
| |
| |
| |
| |
| | |
ways.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
duplicate-tweet issues in non-streaming mode.
|
| |
| |
| |
| |
| | |
txs_free() to the right place - fixes a memory leak.
|
| |
| |
| |
| |
| | |
commands. Also fixed reply command in strict commands mode.
|
| |
| |
| |
| |
| | |
"no news is good news" can be a little confusing.
|
| |
| |
| |
| |
| | |
still using a decimal scanf format string. Messy code duplication. :-(
|
| |
| |
| |
| |
| | |
really should be enough.
|
| |
| |
| |
| |
| | |
to post tweets.
|
| |
| |
| |
| |
| | |
you REALLY need to set G_SLICE=always-malloc. Argh!
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
like tweets but that's what you get with bad settings.. Also, don't show
DMs from ourselves.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
also for stream deduplication. Also, drop tweets from unknown people unless
fetch_mentions is set. The stream will feed us that spam either way but not
everyone wants to see it.
Last, fixing a bug where in streaming mode, per-user last tweet times were
no longer getting tracked.
|