Discussing API v1.1

chrishennkens · 2013-06-18T23:37:00.000Z

Hi,
Two questions:
Why does the CURL string generated by the 1.1 oAuth tool still include this parameter value? oauth_version=“1.0”

Why does your oAuth Tool example from API 1.1 documentation return Code:215 messages when using GET via a browser window? It worked in API 1.0.

I setup my test app.
From the User Timeline API 1.1 Documentation page, I selected my app in the oAuth Tool select box and got the updated oAuth signature.

Then I pasted this link into another tab on the same browser instance and get code:215.
https://api.twitter.com/1.1/statuses/user_timeline.json?screen_name=twitterapi&count=2

I tried switching permissions to include Read/Write and DM’s, reauthorized the same link above and got the same Code:215.

I am unable to complete my work for my clients actual screen_name.

Thanks for reading.

PatriceRayon · 2013-06-19T18:00:42.000Z

I am creating a widget through my own account pointing to one of my lists
https://twitter.com/settings/widgets/new/list

Despite I requested on the profile of a member of my list to unactivate its retweets, I see the retweets of this user anyway if I create my widget…
Is it a bug or how can I get rid of those retweets that I don’t want to see anymore in my Widget ?
What should I do ?
Thank you

LosNationX · 2013-06-19T22:29:16.000Z

Can someone help me ? Well I log into my Twitter account on my phone app. Everything is fine. then when I switch to a different app for about a couple minutes it logs me off causing me to relogin again. its annoying. it keeps doing this. any help ?

LosNationX · 2013-06-19T22:34:51.000Z

Can someone help me ? Well I log into my Twitter account on my phone app. Everything is fine. then when I switch to a different app for about a couple minutes it logs me off causing me to relogin again. its annoying. it keeps doing this. any help ?

martinokello · 2013-06-21T09:28:06.000Z

As of this morning my application has started returning 401 unauthorized error getting user timelines and status timelines for both search and just normal queries.

I am using both my oauth consumer key to exchange for an oauthToken,

which I then use to tweets. It was working all yesterday using V1.1 and it temporary worked today, and now I am getting constant 401 unauthorized access errors when getting tweets from both search and status time lines.

Failliet2 · 2013-06-22T18:42:26.000Z

A couple of clients are using the Twitter plugin as provided before. Now it is not working anymore. Is this the way Twitter deals with users? I think this is showing first class arrogance. Unbelievable!

jaripennanen · 2013-06-24T09:11:09.000Z

I agree, however this is not about inexperience, this decision is plain harmful for Twitter visibility.

I have clients (websites) whom I’ve created simple Javascript that shows single tweet from their account in a bubble. No server-side is required to do that, it’s simple AJAX call in 1.0 API.

Now: I have to create the server-side thingie that loads a single tweet for given account? It doesn’t make sense! I don’t want to become tweet provider to my clients.

Twitter got a lot of visibility compared to other social media sites because it was so easy to show few / single tweet in own website. It was prominent ornament to many sites. Unlike Facebook & Others where incorporating stuff from their timelines have been darn difficult, or plain ugly.

I’m afraid if I have to create web service to serve single tweet I’d have to ask more money from my clients, and who is going to buy that?

Those who make their living from websites, usually uses the simplest systems. Such as this simple AJAX call if it’s possible, now Twitter is adamant to pull the rug from underneath.

guian09 · 2013-06-24T18:43:49.000Z

Hi. I am using GET https://api.twitter.com/1.1/statuses/home_timeline.json How can I limit the amount of information I receive.I only need “created_at”: “id” “text” “source”: “name” "screen_name"
Thanks in advance
GA

guian09 · 2013-06-24T18:49:22.000Z

Almost 3 weeks ago I posted(see bellow)nobody answered.Today I asked for help on how to limit the amount of information I receive from the timeline. Can somebody help me.@episod anybody? thanks
Hi. I am using https://api.twitter.com/1.1/statuses/home_timeline.json whenever I try to use any parameter like for example
https://api.twitter.com/1.1/statuses/home_timeline.json?count=10
give me this error without any parameter no problem
2 0 7316141533e2c2eb020dad48d3fb1d955b42c197
{“errors”:[{“message”:“Could not authenticate you”,“code”:32}]}
Thanks in advance for your help

AUdabe · 2013-06-25T11:28:55.000Z

hello.
with the new update twitter api as I can correct the error that I get in my plugin to allow me to enter the key twitter etc…

thanks.

c_r_w · 2013-06-25T17:25:00.000Z

I can easily make this request using twurl (https://github.com/marcel/twurl), so I would suspect there is a bug in the OAuth library you are using.

c_r_w · 2013-06-25T17:29:06.000Z

Actually, seeing the other issues in the thread, I am thinking there may have been a bug or temporary outage last week. See if this is working for you now.

c_r_w · 2013-06-25T17:30:05.000Z

I suspect there may have been a bug or temporary outage for retrieving followers lists last week. Today, I was able to successfully make this call. See if this is working for you now.

c_r_w · 2013-06-25T17:30:23.000Z

I suspect there may have been a bug or temporary outage for retrieving followers lists last week. Today, I was able to successfully make this call. See if this is working for you now.

c_r_w · 2013-06-25T17:30:31.000Z

I suspect there may have been a bug or temporary outage for retrieving followers lists last week. Today, I was able to successfully make this call. See if this is working for you now.

c_r_w · 2013-06-25T17:38:55.000Z

First question: Twitter’s REST API is at v1.1. However, it relies on OAuth v1.0a for authentication. So that is the correct information for oauth_version.

Second question: I suspect this was a temporary issue, as that particular call works for me when testing with twurl (https://github.com/marcel/twurl). Try it again and see if it is working now.

c_r_w · 2013-06-25T17:42:37.000Z

This is likely a problem with the OAuth library you are using. Test out your requests using the OAuth Tool and check out information on OAuth at [node:3726].

c_r_w · 2013-06-25T17:43:00.000Z

Unfortunately, there is no way to specify which data to return with the current API.

c_r_w · 2013-06-25T17:48:04.000Z

Hi, that is correct, due to OAuth authentication restrictions, it is not possible to use the v1.1 API solely client-side.

c_r_w · 2013-06-25T17:49:18.000Z

Due to the new OAuth requirements, you cannot use the v1.1 API solely client side. For client-side needs, please see https://dev.twitter.com/docs/twitter-for-websites.