aboutsummaryrefslogtreecommitdiffstats
path: root/protocols/twitter/twitter_lib.c
Commit message (Collapse)AuthorAgeLines
...
* Merging "storage" branch which I wrote long ago. It separates generation ofWilmer van der Gaast2013-04-20-8/+0
|\ | | | | | | | | | | 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).
| * Remove two hacks for some glib<2.14 versions that are no longer supported.Wilmer van der Gaast2012-06-04-8/+0
| |
* | I'm still bored on a long flight. Wrote a script to automatically updateWilmer van der Gaast2013-02-21-1/+1
| | | | | | | | | | | | | | 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.
* | Fixed Twitter favourite command. Its syntax was silently changed in the 1.1Wilmer van der Gaast2013-01-14-6/+8
| | | | | | | | | | API. A full list of diffs would be helpful, guys...
* | I suck. This will teach me not to combine logging and actual work in sillyWilmer van der Gaast2012-12-25-1/+1
| | | | | | | | | | ways.
* | Whoops, remove those debugging printfs as I intended to do before merging.Wilmer van der Gaast2012-12-24-9/+1
| |
* | For finding since_id, don't use RT original IDs of course. :-/ This fixesWilmer van der Gaast2012-12-21-4/+3
| | | | | | | | | | duplicate-tweet issues in non-streaming mode.
* | Don't hide own tweets in streaming mode with fetch_mentions off, and moveWilmer van der Gaast2012-12-03-4/+5
| | | | | | | | | | txs_free() to the right place - fixes a memory leak.
* | Have root confirm some commands that so far gave no feedback at all, sinceWilmer van der Gaast2012-11-25-5/+11
| | | | | | | | | | "no news is good news" can be a little confusing.
* | Only a few commands use twitter_message_id_from_command_arg(), others wereWilmer van der Gaast2012-11-25-2/+11
| | | | | | | | | | still using a decimal scanf format string. Messy code duplication. :-(
* | Use hex for show_ids, but stick to the 2-char maximum. a 256-message backlogWilmer van der Gaast2012-11-25-2/+2
| | | | | | | | | | really should be enough.
* | Fixed one potential memory leak, and re-remembered that for GLib + valgrindWilmer van der Gaast2012-11-25-1/+0
| | | | | | | | | | you REALLY need to set G_SLICE=always-malloc. Argh!
* | Finally cleaned up the show-tweet functions.Wilmer van der Gaast2012-11-25-77/+68
| |
* | Fixing two oopses from my last commit.Wilmer van der Gaast2012-11-25-1/+2
| |
* | Changed mode/room management a little bit.Wilmer van der Gaast2012-11-25-46/+10
| |
* | s/twitter_msg/twitter_log/ and use it in a few more places.Wilmer van der Gaast2012-11-25-2/+2
| |
* | Show DMs the right way. With mode=many and show_ids=off they'll look justWilmer van der Gaast2012-11-25-6/+12
| | | | | | | | | | | | like tweets but that's what you get with bad settings.. Also, don't show DMs from ourselves.
* | Minor rework: Always fill td->log now and use it not just for show_ids, butWilmer van der Gaast2012-11-25-47/+84
| | | | | | | | | | | | | | | | | | | | 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.
* | Fixing one obvious memory leak.Wilmer van der Gaast2012-11-24-0/+2
| |
* | Some code for handling disconnect/event messages.Wilmer van der Gaast2012-11-20-0/+41
| |
* | Decode incoming DMs.Wilmer van der Gaast2012-11-12-25/+76
| |
* | Extend keepalive code to time out connections when pings don't getWilmer van der Gaast2012-11-11-0/+1
| | | | | | | | | | acknowledged, using this for Twitter streams and MSN so far.
* | Detect and handle streaming connection loss.Wilmer van der Gaast2012-11-11-0/+10
| |
* | Tiny cleanup. Fixing some memory leaks (why did I not notice so far thatWilmer van der Gaast2012-11-11-5/+3
| | | | | | | | | | those free()s were commented out?).
* | Realised I don't need delimited=length at all, objects are guaranteed to beWilmer van der Gaast2012-11-11-32/+22
| | | | | | | | | | CRLF-terminated.
* | Showing tweets now, and leaking less memory. Still lots of cleanup leftWilmer van der Gaast2012-11-11-26/+54
| | | | | | | | | | to do.
* | Very immature code for reading from the streaming API. It reads from aWilmer van der Gaast2012-11-10-4/+64
| | | | | | | | | | | | fixed URL and tried to parse individual JSON objects. Not doing anything useful with it.
* | Removed xmltree dependency entirely.Wilmer van der Gaast2012-11-10-22/+17
| |
* | Fixed the last parser (generic handler which just remembers status IDs).Wilmer van der Gaast2012-11-09-4/+3
| | | | | | | | | | | | xmltree.h include can almost be removed, it's just used for return values now.
* | Updated error response parsing. Also, use this for 401 responses so for exampleWilmer van der Gaast2012-11-09-13/+12
| | | | | | | | | | | | | | | | the auth errors caused by NTP desync are clearer: <root> twitter - Login error: Authentication failure (401 Unauthorized (Timestamp out of bounds))
* | Getting better. Corruption fixed, fetching of mentions fixed, error handlingWilmer van der Gaast2012-11-09-6/+14
| | | | | | | | | | "fixed".
* | It logs in and fetches statuses! \o/ But, some corruption..Wilmer van der Gaast2012-11-08-59/+76
| |
* | Type safety check.Wilmer van der Gaast2012-11-05-0/+4
| |
* | Can log in now. Fails to fetch timelines though, which is going to be theWilmer van der Gaast2012-11-05-72/+42
| | | | | | | | | | more annoying part anyway. Plus, I want streaming API stuff instead.
* | s/.xml/.json/. Good luck getting that working again.Wilmer van der Gaast2012-11-04-3/+3
| |
* | Move Twitter XML parsing/error checking into a separate function and use itWilmer van der Gaast2012-09-25-83/+64
| | | | | | | | | | everywhere. This should be a more thorough fix for #953.
* | Since I can't figure out where the stalls are coming from at this point, atWilmer van der Gaast2012-09-22-1/+4
| | | | | | | | | | | | | | | | 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.
* | Little cleanup. Use xt_from_string() where possible.Wilmer van der Gaast2012-09-22-32/+24
| |
* | Merge Twitter favourite command from Flexo/#983. Leaving out the unfavouriteWilmer van der Gaast2012-09-15-0/+12
|/ | | | | | | | command for reasons given there. At this point there are loads of command and stuff is getting a little messy maybe.. :-/
* Scan media entities as well, not just url entities. This should expand moreWilmer van der Gaast2012-06-04-15/+22
| | | | | t.co URLs.
* Merging report-spam patch for Twitter from Flexo. #923Wilmer van der Gaast2012-03-12-0/+14
|
* Applied patch from #895, making show_old_mentions an integer setting insteadWilmer van der Gaast2012-02-10-4/+7
| | | | | of boolean so you can change the number of mentions being fetched.
* Merging strip_newlines Twitter setting.Wilmer van der Gaast2012-01-30-0/+3
|\
| * add 'strip_newlines' setting to TwitterDaniel Albers2012-01-13-0/+3
|/
* Don't handle HTTP 401 responses from Twitter API differently anymore afterWilmer van der Gaast2012-01-10-8/+0
| | | | | | initial login. This fixes issues with Twitter's intermittent authentication failures. (Bug #893)
* Return, don't try to flush the timeline on a broken connection. This likelyWilmer van der Gaast2012-01-10-2/+2
| | | | | fixes #888/#891.
* Fixing memory leak in Twitter module.Wilmer van der Gaast2011-12-26-8/+7
|
* Hopefully this fixed #838. Patch from Artem Savkov, thanks! The problem wasWilmer van der Gaast2011-11-24-17/+18
| | | | | | HTTP failures caused by (most likely) DNS resolution problems. Yes, ignoring return values is still bad, kids!
* changeset:devel,814 was silly and incomplete. This should fix that. FullWilmer van der Gaast2011-10-19-0/+4
| | | | | workaround for Twitter "hang" problem.
* Stupid work-around for bug #838. The troublesome condition is known, I justWilmer van der Gaast2011-10-17-0/+7
| | | | | | don't know exactly how BitlBee gets into it. Any more info from people who see this problem often would be useful.