| Commit message (Collapse) | Author | Age | Lines |
... | |
|
|
|
| |
It has been broken for a very long time and nobody cared about it.
|
|
|
|
|
|
|
| |
These appear in glib 2.40, and, well, are pretty much useless. But
people complain about them anyway.
Probably fixes trac ticket 1151, at least partially.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
srv_lookup works on cygwin and openbsd now.
Provide ns_initparse, friends, and types where they aren't provided by
platform.
Use dn_expandname instead of custom parser so compressed DNS responses
are handled correctly.
|
|
|
|
| |
Only took me a few months to write. I even added a test case.
|
| |
|
|
|
|
|
|
|
| |
(used to encode >16-bit chars). Added code to parse those *and* the ability
to encode >16-bit Unicode in UTF-8. Also sending this upstream. This should
fix #1121.
|
|
|
|
|
|
| |
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...
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
Little benefit as I'm not burning my fingers on keepalive connecitons for
now, but eventually the Twitter streaming API is going to drop 1.0 support:
https://dev.twitter.com/blog/deprecating-http-1.0-streaming-api
|
| |
| |
| |
| |
| | |
used protocol version when internally handling redirects.
|
|/
|
|
|
|
| |
let me close #641, and more importantly, prepares the Twitter module for
an upcoming API change. https://dev.twitter.com/blog/deprecating-http-1.0-streaming-api
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| | |
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).
|
| |
| |
| |
| |
| |
| | |
Also, use it in xt_print() instead of replicating most of xt_to_string()
in it. This changed four-space indents into tabs but oh well, we'll live.
|
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| | |
json.c: In function ‘json_parse_ex’:
json.c:260:30: warning: ‘string_length’ may be used uninitialized in this function [-Wmaybe-uninitialized]
json.c:358:16: warning: ‘string’ may be used uninitialized in this function [-Wmaybe-uninitialized]
|
| | |
|
| |
| |
| |
| |
| | |
Twitter webservers seem to do successful session resumes only sporadically.
|
| |
| |
| |
| |
| | |
one for every connection.
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
strto(d|l) fix because I can just use GLib instead of reinventing the wheel.
This should fix corruption issues with tweets in Cyrillic. I've double-
checked this code against http://en.wikipedia.org/wiki/UTF-8 now and it looks
correct to me.
|
| | |
| | |
| | |
| | |
| | |
| | | |
type to long long, the parser was still using strtol to convert numbers,
truncating large numbers to LONG_MAX. Bug found by Artem Savkov, thanks!
|
| | |
| | |
| | |
| | |
| | | |
"no news is good news" can be a little confusing.
|
| | |
| | |
| | |
| | |
| | | |
Forgot to do this so far because my libevent code let me get away with it.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
MTU in mind it's not a very useful change, but I seem to be getting data in
bigger chunks most of the time. Likely because with SSL you have record (?)
boundaries and compression.
This should reduce I/O overhead just a little bit.
|
| |\ \ |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
those free()s were commented out?).
|
| | | |
| | | |
| | | |
| | | |
| | | | |
http_close().
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
fixed URL and tried to parse individual JSON objects. Not doing anything
useful with it.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
a complete response before giving it back to the caller.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
types, or it might be too small to contain Twitter message IDs on for
example GCC+i386.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
the auth errors caused by NTP desync are clearer:
<root> twitter - Login error: Authentication failure (401 Unauthorized
(Timestamp out of bounds))
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
avoid making *any* changes to the third-party json.c.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Starting to see the use of convenience functions to dig through many layers
of structs..
|
| | | | |
|
| | | | |
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
stream is spread over two packets (or SSL records in this case), xt_handle()
would report a fatal error (which normally means the connection has failed
and should be abandoned immediately).
Returning 1 is likely more correct; just the fact that there's no data to
process yet is not a fatal failure.
This fixes potential issues with Google Talk when using OpenSSL (which
seems to be feeding data on record boundaries, even if additional records
have already been received).
|
| | |
| | |
| | |
| | |
| | | |
next-to-useless binary.
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| | |
Adding an extra layer of defense against truncated responses from Twitter.
But as long as the response from xt_from_string() isn't NULL-checked this
won't help much. So that's my next step. :-)
|
| |
| |
| |
| |
| |
| |
| |
| | |
least have a work-around for it.
After hitting the Twitter timer a few times while a previous fetch still
seems to be running, close the connection. Auto-reconnect will do the rest.
|
| | |
|