Thanks Twitter. Not only have you removed open access to public Twitter timelines, you're expecting developers to contend with cryptic authentication documentation! Many of us simply want to display our own tweets on our own website, but it's obvious Twitter prefers us to use their widgets. Despite the convoluted Twitter instructions, implementing OAuth in your lovingly-crafted API 1.0 application is reasonably straight-forward if you use the libraries provided by talented group of (non-Twitter) developers.
They break it down into a few easy steps (largely made easy because the library does most of the heavy lifting for you):
- Create your Twitter Application
- Create an Access Token
- Download the OAuth Library
- Modify Your Timeline Fetching Code