After fighting with the various (outdated) oAuth libraries that were linked to on the developer site, I have finally thrown in the towel and am now asking for assistance here. Do forgive me if I sound somewhat frustrated/agitated because I really am.
I’m currently handling a project for a client where they would like to place a twitter timeline on their front page.
If they weren’t so particular about the look and feel of the feed, I would just grabbed the new embedded timeline JS code and dumped it in there.
The next logical solution would be to grab the timeline/feed out via the API and then manipulate the text strings as required.
Of course, now that Twitter has moved on to ver 1.1 of oAuth, I can’t use this any more:
It’s just a read-only operation. I seriously don’t understand why there is a need for oAuth. I said the same thing last year when Facebook did the same thing, but things haven’t changed then. At least their implementation was so much easier.
Long story short, is there anyone who can help me? Please?