Building on Andy's great work, I've been putting together a collection
of utilities for accessing and working with data pulled from Twitter's
APIs. It's still in its infancy, but the goal is to simplify handling
Twitter's rate limits, pagination of results, etc., and to clean up and
convert returned json data for analytics purposes.

The "clucker" egg as I'm calling it will be available at:

https://github.com/n3mo/clucker

Thanks again Andy!

- Nick


Daniel Leslie <[email protected]> writes:

> Ooh, I rather like that talk. Thanks for the eggs!
>
> -Dan
> On 18 Dec 2014 09:24, "Andy Bennett" <[email protected]> wrote:
>
>> Hi everyone,
>>
>> I've released v0.2 of the OAuth Egg:
>>
>> http://wiki.call-cc.org/eggref/4/oauth
>>
>>
>> This release brings support for HMAC-SHA1 signing and a few bug fixes
>> when using the 1.0a and RFC 5849 modes.
>>
>> This egg has now been verified with at least the APIs of Dropbox and
>> Twitter.
>>
>>
>> Thanks to Nick Van Horn for reporting some bugs and spurring me into
>> action!
>>
>>
>>
>>
>> For those of you binding HTTP APIs, you might also be interested in the
>> rest-bind egg:
>>
>> http://wiki.call-cc.org/eggref/4/rest-bind
>>
>> ...and you can complement the documentation with my recent talk about
>> the rationale behind it:
>>
>> https://www.youtube.com/watch?v=nzS48beMxwo
>>
>>
>>
>>
>>
>> Regards,
>> @ndy
>>
>> --
>> [email protected]
>> http://www.ashurst.eu.org/
>> 0x7EBA75FF
>>
>>
>> _______________________________________________
>> Chicken-users mailing list
>> [email protected]
>> https://lists.nongnu.org/mailman/listinfo/chicken-users
>>

_______________________________________________
Chicken-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/chicken-users

Reply via email to