Link Details

Link 1018403 thumbnail
User 1083557 avatar

By narramissic
Submitted: Aug 21 2013 / 09:57

It’s been several months now since Twitter switched over to version 1.1 of the Twitter API. Headaches were expected, and headaches are being had. A primary cause of these headaches is the move to enforce OAuth for every API request, but a second culprit - rate limiting - is responsible for drastic restructuring of existing code. Here's how to avoid rate limits and re-enable JavaScript for the Twitter API v1.1.
  • 2
  • 0
  • 105
  • 15

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (2)

Voters Against This Link (0)

    Java EE7
    Written by: Andrew Lee Rubinger
    Featured Refcardz: Top Refcardz:
    1. Design Patterns
    2. OO JS
    3. Cont. Delivery
    4. CI Patterns
    5. CI Tools
    1. Spring Integration
    2. Git
    3. Regex
    4. Java
    5. REST