| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
| |
These only reflect on what arch/cpu bitlbee was built, not on which
it is running. This makes the Debian package unreproducible.
See e.g.
https://tests.reproducible-builds.org/rb-pkg/testing/i386/bitlbee.html
|
|
|
|
|
|
| |
Mostly minor rare leaks that happen in error conditions, and one
dereference before null check in twitter_logout (the null check is
probably the wrong one there, but it doesn't hurt to keep it)
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
used protocol version when internally handling redirects.
|
|
|
|
|
| |
"no news is good news" can be a little confusing.
|
|
|
|
|
|
| |
fixed URL and tried to parse individual JSON objects. Not doing anything
useful with it.
|
|
|
|
|
|
| |
-i8 -kr -ts8 -ut -l100 Because K&R isn't so bad after all but spaces are
definitely evil. (Not that GNU indent understands how to use tabs, oh well.)
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|