You can clone with
HTTPS or Subversion.
This is a smaller story broken out from #562.
This issue is just to make/statuses/followers.json work like the twitter API. This route doesn't currently exist at all, but there is a nice update json decorator for you to use.
Ignore the issue of client authentication for the moment; just make this work as a normally authenticated user in the browser for now (see #564 about authentication)
Description: Returns the authenticating user's followers, each with current status inline. They are ordered by the order in which they followed the user, 100 at a time.
Definitely interpret anything in the twitter docs so that it makes sense for rstat.us, and definitely ask if you have any questions!
Leave a comment if you're working on this.
Note:: Specifies the ID of the user to befriend. Helpful for disambiguating when a valid user ID is also a valid screen name.
screen_name: optional The screen name of the potentially blocked user. Helpful for disambiguating when a valid screen name is also a user ID. Example Values: noradio
Breaks the results into pages. This is recommended for users who are following many users. Provide a value of -1 to begin paging. Provide values as returned in the response body's next_cursor and previous_cursor attributes to page back and forth in the list. Example Values: 12893764510938
The above is what made sense to me based off of the current way rstat.us is built. I didn't include entities for that because well, rstat.us doesn't have entities.
The Twitter API has moved on from v1 to v1.1, and the link above is now broken. Here's the v1.1 API documentation:
It looks to me like this resource has been removed in the new version. Instead we've got these:
The first one returns only user ids, in groups of 5,000. The second returns complete user objects, in groups of 20.
Unlike the /statuses/followers resource, neither of these resources includes the most recent status of each user.