about summary refs log tree commit diff stats
path: root/src/client.h
Commit message (Collapse)AuthorAgeFilesLines
* Added a convenience overload to client::replyToTweetKelly Rauchenberger2016-12-011-0/+1
|
* Made tweets, users, and notifications into copyable objectsKelly Rauchenberger2016-11-291-0/+10
| | | | Notifications are now also mutable. Users and tweets no longer have helper methods for interacting with the client. Fixed a bug (possibly introduced by a change to the Twitter API) that caused non-reply tweets to be marked as unknown notifications.
* Updated API to use exceptions and make tweet/user objects more helpfulKelly Rauchenberger2016-08-201-94/+35
|
* Wrapped JSON parsing in exception handlingKelly Rauchenberger2016-06-011-1/+1
|
* Added ability to get configurationKelly Rauchenberger2016-05-311-0/+6
|
* Added option to receive all replies in user streamKelly Rauchenberger2016-05-251-1/+4
|
* Added utility function to generate tweet reply prefillKelly Rauchenberger2016-05-221-0/+2
|
* Projects using libtwitter++ no longer have to include its dependenciesKelly Rauchenberger2016-05-211-7/+5
|
* Started implementing user streamsKelly Rauchenberger2016-05-201-5/+72
| | | | You can now start a user stream and end it yourself. If it disconnects abnormally, it will reconnect with a backoff as described by Twitter. Some data structures have some fields parsed now; tweets have IDs, text, and authors. Users have IDs, screen names, and names. Notifications from the stream are parsed completely. The ability to follow and unfollow users has also been added, as well as the ability to get a list of friends and followers, and to reply to a tweet.
* Added ability to upload media and tweet itKelly Rauchenberger2016-04-131-2/+13
| | | | Images (static and animated) and videos have been tested. Currently all media uploads occur in one large chunk; support to break down chunks will be added later.
* Added basic ability to tweetKelly Rauchenberger2016-04-121-0/+29
ass="p"></title> <meta name="viewport" content="width=device-width,initial-scale=1"> <style> .rails-default-error-page { background-color: #EFEFEF; color: #2E2F30; text-align: center; font-family: arial, sans-serif; margin: 0; } .rails-default-error-page div.dialog { width: 95%; max-width: 33em; margin: 4em auto 0; } .rails-default-error-page div.dialog > div { border: 1px solid #CCC; border-right-color: #999; border-left-color: #999; border-bottom-color: #BBB; border-top: #B00100 solid 4px; border-top-left-radius: 9px; border-top-right-radius: 9px; background-color: white; padding: 7px 12% 0; box-shadow: 0 3px 8px rgba(50, 50, 50, 0.17); } .rails-default-error-page h1 { font-size: 100%; color: #730E15; line-height: 1.5em; } .rails-default-error-page div.dialog > p { margin: 0 0 1em; padding: 1em; background-color: #F7F7F7; border: 1px solid #CCC; border-right-color: #999; border-left-color: #999; border-bottom-color: #999; border-bottom-left-radius: 4px; border-bottom-right-radius: 4px; border-top-color: #DADADA; color: #666; box-shadow: 0 3px 8px rgba(50, 50, 50, 0.17); } </style> </head> <body class="rails-default-error-page"> <!-- This file lives in public/500.html --> <div class="dialog"> <div> <h1>We're sorry, but something went wrong.</h1> </div> <p>If you are the application owner check the logs for more information.</p> </div> </body> </html>