Skip to content
This repository has been archived by the owner on May 19, 2020. It is now read-only.

Twitter API implementation #20

Closed
tunix opened this issue Jul 21, 2012 · 3 comments
Closed

Twitter API implementation #20

tunix opened this issue Jul 21, 2012 · 3 comments
Labels

Comments

@tunix
Copy link

tunix commented Jul 21, 2012

Going to implement twitter API for my learning process. Then I plan to implement #19 if time permits.

@BYK
Copy link
Owner

BYK commented Jul 22, 2012

I would like to see this happen too and we actually considered Twitter API to be our second guest of honor for implementations. But although Twitter claims it has a "REST" api, all they have is a piece of garbage that uses HTTP, poorly, for the transport. It does not conform to any REST conventions/rules so I don't think it is possible to implement a client for Twitter using pyresto.

Until Twitter fixes their API...

@BYK
Copy link
Owner

BYK commented Jul 22, 2012

You may try fixing #3 btw. Foursquare API v2 is not perfect in terms of REST compatibility but it is a heaven after the Twitter API nightmare.

@tunix
Copy link
Author

tunix commented Jul 24, 2012

Nonetheless I'll keep on implementing Twitter API. Despite what it's, I believe it's valuable to have it in pyresto. Afterall, that's what the fork is for. :p

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants