#83

Dear Twitter Team: any simple solution to retrieve a public tweet using javascript only?

#84

I just posted an answer on Stackoverflow that might help you:

#85

no there is no way to do it simply.

#86

Frustrating, annoying and stupid…
Like @spritz_creative and others here said, not a single logical reason why auth should be required for public info.

#87

Hahaha retards… always making things “secure”

#88

The solution @Jason_Mayes created works wonderfully! If you use Tumblr as a CMS, you do need to adjust the way you execute the Javascript slightly to get it to work. I wrote up some tips here: http://bitshare.cm/post/53690908419/did-your-tweets-recently-break-on-your-website-heres

Best wishes.

@DavidShares

#89

@WW_webdev - more likely, in my view, it’s just the first step in a long process towards charging for api access. By authenticating everyone they can track per user who is using the API. There are already call volume and concurrency limits on the API on a per account (and per IP address) basis with the option to pay to increase those limits. There are quite a few big data mining companies out there who pay Twitter a lot of money for all this information that they want to monetise in turn. Having free access to the API undermines that entire business model for both twitter and their partners.

In time expect those rate and concurrency limits to be reduced and cheaper access plans or official partnerships to be announced if you need entry level access to that data. It sucks but Twitter do need to monetise their service if they are to stay in business and this is one of the ways they’ll use. I just wish they were more open about their long term plans for the API and app ecosystem. Fortunately in time a more open competitor will come along, but until then we’re stuck with OAuth for all.

#90

I put this solution together based on @kiers comment above. It is php only, requires no javascript, and is only one file. I am certain it can be improved, but should provide a great starting point… https://github.com/JonMasterson/Flip-the-Bird

#91

get data into twitter timeline but response below error…

{“errors”: [{“message”: "The Twitter REST API v1 is no longer active. Please migrate to API v1.1. https://dev.twitter.com/docs/api/1.1/overview.", “code”: 68}]}

#92

Great simple PHP example. I added this line in index.php, right below the tag, so the items get a proper pubDate:

<?php echo htmlspecialchars(htmlspecialchars_decode(strip_tags($line->created_at))); ?>

#93

twitterizer is no longer supported and uses API 1.0

#94

@jeremykemper123 There’s only one way to use Twitter API 1.1 without oAuth – and that’s by having a small extra bit of code to act as a proxy between your JavaScript and the API.

E.g. How to use Twitter API 1.1 in JavaScript code, bypassing oAuth authentication on the client-side: http://www.timacheson.com/Blog/2013/jul/twitter_api_proxy

#95

Booo… Its doesnt make any sense for me to request and authenticate through OAuth for the public feeds. The feeds which can be viewed through Google search page without even logging in!!!

#96

This is completely ridiculous for public data and no legacy support at all after version 1.0 retirement. I had to dig about 90% of v1.1 documentation for last ~3 hours and ending up getting information from these discussions and by directly tweeting to the platform team. This is silly!

#97

Twitter might need to update some things themselves https://search.twitter.com/search?q=bollocks

#98

@neilakapete And others, there seems to be a way to include the timeline WITHOUT the twitter app token: http://bit.ly/13yJjkk note: About to test this method

#99

that is if they implemented the oAuth api correctly. it does not work like everyone else does

#100

You are welcome!

#101

This is fixed in latest version please ensure you are using latest version from http://jasonmayes.com/projects/twitterApi/

#102

This is crazy I can understand the desire to reduce load but surely this must be causing a massive reduction in traffic to twitter from embedded feeds…