Re: [twitter-dev] Best C/C++ library for Twitter JSON?
hai,
in JSON.org u can find a JSON Library
//kamesh
On Thu, Jun 30, 2011 at 8:40 AM, CD chesterdorae...@gmail.com wrote:
Is there a defacto C/C++ library that can handle twitter's streaming
JSON? I tried real quick as a test to see if I can pipe my twitter
feed to boost's JSON parser. No dice. My JSON parser cannot handle the
following lines:
profile_background_image_url:http:\/\/a2.twimg.com\/
profile_background_images\/4531792\/wallpaper_stock.jpg,
url:http:\/\/on.fb.me\/bShBVQ,
exception error: invalid escape sequence
id:86162751646482432,
exception error: expected value
Removing the offending lines gets a populated property tree. Obviously
not sufficient for twitter. Here is the code in case I declared my
property tree wrong. Help?
int main (int argc, char * const argv[])
{
boost::property_tree::basic_ptreestd::string,std::string pt;
std::ifstream f;
f.open(testJSON2a.txt);
if(!f.is_open())
{
std::cout Error;
return 0;
}
try
{
boost::property_tree::json_parser::read_json(f,pt);
boost::property_tree::basic_ptreestd::string,std::string::const_iterator
iter = pt.begin(),iterEnd = pt.end();
for(;iter != iterEnd;++iter)
{
std::cout iter-first iter-
second.get_valuestd::string() std::endl;
}
}
catch(boost::property_tree::json_parser::json_parser_error je)
{
std::cout Error parsing: je.filename() on line:
je.line() std::endl;
std::cout je.message() std::endl;
}
return 0;
}
I can probably fix these two exceptions, but I have a feeling there
may be countably many other issues down the road with this approach.
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: 401: Could not authenticate with OAuth.
Hai, what is the signature base string u are using to generate the sigantureare u using any library(i think u are develoing this for iPhone) for get the data? //kamesh On Wed, Jun 29, 2011 at 10:38 PM, Howard Gutowitz howard.gutow...@gmail.com wrote: Specifically I have: 'account/verify_credentials.xml' finishes with HTTP 200 All other requests work fine. Only 'friendships/create.xml' and 'friendships/delete.xml request fails with the following error: ?xml version=1.0 encoding=UTF-8? hash errorCould not authenticate with OAuth./error request/1/friendships/create.xml?screen_name=rosariodawson/ request /hash Request's header Authorization = OAuth realm=\\, oauth_consumer_key=\X\, oauth_token=\179876397- xcJcDpijQ7Mde1QCGfTUHdLLbxWovkQhCiqXdDA\, oauth_signature_method= \HMAC- SHA1\, oauth_signature=\Gl7u0xZ3iGRKPS%2BFMNHBTB0Gwkg%3D\, oauth_timestamp=\1309173898\, oauth_nonce=\26DA6912-F3CC-40A6-B746- B4F18135C321\, oauth_version=\1.0\; X-Twitter-Client = TwTool; X-Twitter-Client-Url = http://www.eatoni.com/;; X-Twitter-Client-Version = 1; Response's header Cache-Control = no-cache, max-age=1800; Connection = Keep-Alive; Content-Encoding = gzip; Content-Type = application/xml; charset=utf-8; Date = Mon, 27 Jun 2011 11:27:20 GMT; Expires = Mon, 27 Jun 2011 11:57:20 GMT; Keep-Alive = timeout=15, max=100; Server = hi; Set-Cookie = k=213.108.72.42.1309174040693549; path=/; expires=Mon, 04-Jul-11 11:27:20 GMT; domain=.twitter.com, guest_id=130917404070357573; path=/; expires=Wed, 27 Jul 2011 11:27:20 GMT, _twitter_sess=BAh7CDoHaWQiJTcyZmM4ZTk0ODkzMThkZjZjY2FhNzIxMjMwNjQ2ZTVlIgpm %250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG %250AOgpAdXNlZHsAOg9jcmVhdGVkX2F0bCsIhoja0DAB --bc92ade75da0322e48b793fbee2dff7ad914b087; domain=.twitter.com; path=/; HttpOnly; Status = 401 Unauthorized; Transfer-Encoding = Identity; Vary = Accept-Encoding; Www-Authenticate = OAuth realm=\https://api.twitter.com\;; X-Runtime = 0.00949; On Jun 27, 6:09 pm, vishal vishal@gmail.com wrote: I am having trouble posting to twitter from my ruby on rails app. The consumer keys and secrets are correct, also the oauth token and secret seem to be fine. The code used to work fine but I have been getting these error since today morning. Is anyone facing the same issue or am I going wrong anywhere? client = Twitter::Client.new( :consumer_key = 'X', :consumer_secret = 'XX', :oauth_token = XX, :oauth_token_secret = , :endpoint = 'https://api.twitter.com') #Twitter::Client:0x104ae9e30 @user_agent=Twitter Ruby Gem 1.1.2, @proxy=nil, @endpoint=https://api.twitter.com;, @search_endpoint=https://search.twitter.com/;, @format=:json, @consumer_key=, @oauth_token_secret=, @adapter=:net_http, @oauth_token=, @consumer_secret=XXX client.update post message Twitter::Unauthorized: POSThttps://api.twitter.com/statuses/update.json: 401: Could not authenticate with OAuth. Thanks Vishal Kajjam -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] oAuth problem with AIR desktop app - Failed to validate oauth signature and token
Hi. I have the same issue, but may i ask why you are performing a GET request with a POST signature? HTTP POST should be: POST /oauth/request_token Headers\r\n \r\n callback=..nonce=... Not in the way you've shown us: HTTP POST: https://api.twitter.com/.../oauth_callback=..;... Secondly, have you checked your timestamps so it matches the twitter server? Say you live in Sweden like i do, you need to compensate for the time difference with -1 so it matches GMT. Thirdly, are you URL encoding anything at all in the POST header? I think the signature needs to be URL encoded. This is what my Header and POST data looks like: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/40b41730d2144ca9 On Thu, Jun 30, 2011 at 12:19 AM, miloshes blask...@gmail.com wrote: Hi guys, I am new here, working on yet another twitter client for desktops. It's Adobe AIR desktop app written in AS3. And I have a problem with acquiring a request token. Signature base: POSThttps%3A%2F%2Fapi.twitter.com http://2fapi.twitter.com/%2Foauth %2Frequest_tokenoauth_callback=http%3A%2F%2Fgoogle.com %2Foauth_consumer_key=b0..wwoauth_nonce=84950oauth_signature_method=HMAC- SHA1oauth_timestamp=1309385887oauth_version=1.0 HTTP POST: https://api.twitter.com/oauth/request_token?oauth_callback=http://twitter.comoauth_consumer_key=b0..wwoauth_nonce=82384oauth_signature_method=HMAC-SHA1oauth_timestamp=1309374642oauth_version=1.0oauth_signature=Cfx..og% Erro I am getting: Failed to validate oauth signature and token I am able to use pin code authorization but I don't want to use it for my app. So I hope there is a way how to pass oAuth authentication from desktop app using callback url. Could anyone help me please? It's killing me :( -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Digest for twitter-development-talk@googlegroups.com - 25 Messages in 11 Topics
On Wed, Jun 29, 2011 at 8:47 PM, twitter-development-talk+nore...@googlegroups.com wrote: I'm working on AND OR search on search API. I know I can do the query A OR B , but I'd like to use more search parameter, like, (A B) OR (C D). Is it possible to do that kind of parenthetic query? I am able to run search queries such as (bangalore OR mysore) AND (hotel) via the search api, without any problems. -- Targeted direct marketing on Social networks - http://www.wisdomtap.com/ -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Getting right to read DMs for exactly one user
Hi. My Twitter service needs to have exactly one user with the right to read DMs. All other users don't need that right, so I'm quite happy that they automatically lose it. Right now I'm trying to get an access token for the one user with DM right. I edit my application at dev.twitter.com, set it's right level to Read, Write and private Messages, revoke access to the app from the user in question and then re-authorize it. But on the re- authorization-page Twitter still shows me read DMs until June 30th. What do I have to do to get a token with extended rights to read DMs? Sincerely, Fabian Schlenz -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Application website
What do i do if i dont have an application website? i registered my app already but i dont have an actual application and i cant use it to tweet because i dont know how to open the web page because i have no addres...its just a folder on my desktop with my php and css files. What do i do now? lol -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Why our Twitter Share button is not counting?
Hi, We have added Twitter Share button at website: http://qrcode.good-survey.com (you can see it at the bottom) but it is not counting after sharing. I think we had done all by specification (the only question is if it is ok to have property counturl but removing it also does not help): a href=http://twitter.com/share; class=twitter-share-button data- text=QR Code Platform (branding, tracking, mobile apps, vector shapes, api, decoding) - http://goo.by/wf6r1T - #good_survey, #qrcode, #mobileapps data-count=horizontal data-via=good_survey counturl=http://qrcode.good-survey.com; data-url=http://qrcode.good- survey.comTweet/ascript type=text/javascript src=http:// platform.twitter.com/widgets.js/script Any hints? Best regards Alex -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Problems with Twitter Follow button
I am trying at add the follow button into the footer of our website however it would appear that ever time I put the button code into the left footer div, it is completely deleting the right div and its content. When I go back to template the right div is still there but when I view via Firebug the code has vanished. Why is this happening? Even when I put the botton code in the right div (which is not where I want to it appear but I tried out of interest) it is still deleting the content of that div. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] When is permission level enforcement going to happen?
I know the date for this is today (June 30), but is it something that will be rolling out slowly throughout the day starting sometime soon, or is it going live at the *end* of today or how is that working? I don't recall seeing the details mentioned previously. I'd like to get an idea of when I should start the pot of coffee that will be necessary to deal with the inevitable tech support flood... l8r Sean -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Application website
As far as the application record creation on dev.twitter.com is concerned, you can use a placeholder website URL until you have a more permanent home. Without more information about your development environment, I can't help you get up and running on your local machine, but ultimately you'll want to get your PHP and CSS files to be served from a HTTP server running on your machine, in most cases Apache. If you're using a Mac, you already have Apache running on your machine and it should be pretty easy for you to find some documentation on how to execute PHP files from your ~/Sites directory structure. @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Thu, Jun 30, 2011 at 5:15 AM, gshadowninja...@hotmail.com gshadowninja...@hotmail.com wrote: What do i do if i dont have an application website? i registered my app already but i dont have an actual application and i cant use it to tweet because i dont know how to open the web page because i have no addres...its just a folder on my desktop with my php and css files. What do i do now? lol -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] When is permission level enforcement going to happen?
Hi Sean, We're currently aiming for early to mid afternoon, Pacific Time, barring any unplanned circumstances. We'll also update @twitterapi and both the -announce and -talk mailing lists as we roll out. Thanks! @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Thu, Jun 30, 2011 at 6:57 AM, Sean Heber s...@spiffytech.com wrote: I know the date for this is today (June 30), but is it something that will be rolling out slowly throughout the day starting sometime soon, or is it going live at the *end* of today or how is that working? I don't recall seeing the details mentioned previously. I'd like to get an idea of when I should start the pot of coffee that will be necessary to deal with the inevitable tech support flood... l8r Sean -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Tweet button and iphone
Hi: I develop mobile websites and I want to use a tweet button in one of my pages,since using twitter with a mobile website is the first time for me I did a test page. This is my page: http://iphone.internet.com.jo/login.html When a user visit my website from a device like iphone and click tweet button,it will show the popup [Share box] as the current page [not as a popup],if the user doesn't want to login and clicked on cancel then twitter page should redirect the user back to my page but that wasn't the result,it redirects the user to twitter homepage. Is there a solution or any workarounds for this? I want the user to be able to tweet from iphone without any popups and also be able to return back to my site if (s)he didn't want to login. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: 401: Could not authenticate with OAuth.
We are using the following library: http://oauth.googlecode.com/svn/code/obj-c/OAuthConsumer Signature base string is created in file: 'http://oauth.googlecode.com/ svn/code/obj-c/OAuthConsumer/OAMutableURLRequest.m', method: '- (NSString *)_signatureBaseString;' Signature base string: POSThttps%3A%2F%2Fapi.twitter.com%2F1%2Ffriendships %2Fcreate.xmloauth_consumer_key%X%26oauth_nonce %3D28451170-543E-44CC-9554-118E69C0EDAB%26oauth_signature_method %3DHMAC-SHA1%26oauth_timestamp%3D1309432652%26oauth_token%3D179876397- xcJcDpijQ7Mde1QCGfTUHdLLbxWovkQhCiqXdDA%26oauth_version%3D1.0 On Jun 30, 9:27 am, kamesh SmartDude kamesh.smartd...@gmail.com wrote: Hai, what is the signature base string u are using to generate the sigantureare u using any library(i think u are develoing this for iPhone) for get the data? //kamesh On Wed, Jun 29, 2011 at 10:38 PM, Howard Gutowitz howard.gutow...@gmail.com wrote: Specifically I have: 'account/verify_credentials.xml' finishes with HTTP 200 All other requests work fine. Only 'friendships/create.xml' and 'friendships/delete.xml request fails with the following error: ?xml version=1.0 encoding=UTF-8? hash errorCould not authenticate with OAuth./error request/1/friendships/create.xml?screen_name=rosariodawson/ request /hash Request's header Authorization = OAuth realm=\\, oauth_consumer_key=\X\, oauth_token=\179876397- xcJcDpijQ7Mde1QCGfTUHdLLbxWovkQhCiqXdDA\, oauth_signature_method= \HMAC- SHA1\, oauth_signature=\Gl7u0xZ3iGRKPS%2BFMNHBTB0Gwkg%3D\, oauth_timestamp=\1309173898\, oauth_nonce=\26DA6912-F3CC-40A6-B746- B4F18135C321\, oauth_version=\1.0\; X-Twitter-Client = TwTool; X-Twitter-Client-Url = http://www.eatoni.com/;; X-Twitter-Client-Version = 1; Response's header Cache-Control = no-cache, max-age=1800; Connection = Keep-Alive; Content-Encoding = gzip; Content-Type = application/xml; charset=utf-8; Date = Mon, 27 Jun 2011 11:27:20 GMT; Expires = Mon, 27 Jun 2011 11:57:20 GMT; Keep-Alive = timeout=15, max=100; Server = hi; Set-Cookie = k=213.108.72.42.1309174040693549; path=/; expires=Mon, 04-Jul-11 11:27:20 GMT; domain=.twitter.com, guest_id=130917404070357573; path=/; expires=Wed, 27 Jul 2011 11:27:20 GMT, _twitter_sess=BAh7CDoHaWQiJTcyZmM4ZTk0ODkzMThkZjZjY2FhNzIxMjMwNjQ2ZTVlIgpm %250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG %250AOgpAdXNlZHsAOg9jcmVhdGVkX2F0bCsIhoja0DAB --bc92ade75da0322e48b793fbee2dff7ad914b087; domain=.twitter.com; path=/; HttpOnly; Status = 401 Unauthorized; Transfer-Encoding = Identity; Vary = Accept-Encoding; Www-Authenticate = OAuth realm=\https://api.twitter.com\;; X-Runtime = 0.00949; On Jun 27, 6:09 pm, vishal vishal@gmail.com wrote: I am having trouble posting to twitter from my ruby on rails app. The consumer keys and secrets are correct, also the oauth token and secret seem to be fine. The code used to work fine but I have been getting these error since today morning. Is anyone facing the same issue or am I going wrong anywhere? client = Twitter::Client.new( :consumer_key = 'X', :consumer_secret = 'XX', :oauth_token = XX, :oauth_token_secret = , :endpoint = 'https://api.twitter.com') #Twitter::Client:0x104ae9e30 @user_agent=Twitter Ruby Gem 1.1.2, @proxy=nil, @endpoint=https://api.twitter.com;, @search_endpoint=https://search.twitter.com/;, @format=:json, @consumer_key=, @oauth_token_secret=, @adapter=:net_http, @oauth_token=, @consumer_secret=XXX client.update post message Twitter::Unauthorized: POSThttps://api.twitter.com/statuses/update.json: 401: Could not authenticate with OAuth. Thanks Vishal Kajjam -- Twitter developer documentation and resources:https://dev.twitter.com/doc API updates via Twitter:https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] New twitter API in Clojure
Hi guys I have open sourced my connectivity api to twitter, so for all you Clojure twitter-heads, go and check out: https://github.com/adamwynne/twitter-api Some features: - its based on the async.http.client library for high performance, low overhead comms - it has a full test suite - it is up to date, and covers all the relevant API calls in the streaming, user and RESTful API's I welcome feedback and of course, all contributions are gratefully received. Enjoy Adam -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Tweet button and iphone
Hi Anajjar, I've been trying to click on your site to test your example, but the site is not responding. However, when a user clicks a Tweet Button on a site using mobile Safari on the iPhone, a new browser window will open with the Tweet intent. If a user is logged in, he can complete that intent. If not, he will be prompted to sign in. I just tested this with Twitter's main blog at http://blog.twitter.com from an iPhone using iOS 4.3.3. Users can return to your site by pressing the iOS UI that shows all open pages (up to 8) and swiping back to your site. Hope this helps. Seth anaj...@ibs.com.jo wrote: Hi: I develop mobile websites and I want to use a tweet button in one of my pages,since using twitter with a mobile website is the first time for me I did a test page. This is my page: http://iphone.internet.com.jo/login.html When a user visit my website from a device like iphone and click tweet button,it will show the popup [Share box] as the current page [not as a popup],if the user doesn't want to login and clicked on cancel then twitter page should redirect the user back to my page but that wasn't the result,it redirects the user to twitter homepage. Is there a solution or any workarounds for this? I want the user to be able to tweet from iphone without any popups and also be able to return back to my site if (s)he didn't want to login. -- Seth Bindernagel | @binder https://twitter.com/intent/follow?screen_name=binder -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] X-RateLimit-Remaining decrementing by 2 per call
Hi, I have just started using the twitter api in a blackberry application and in order to understand rate limiting further I have been experimenting by making calls using my browser and viewing the HTTP Headers. I have been making calls to api.twitter.com/1/friendships/show.xml? source_screen_name=XXXtarget_screen_name=YYY which I would expect to reduce X-RateLimit-Remaining by 1 for each call but it is reducing by 2. Is this correct? Internally are two calls being made? I would expect a single call to reduce the count by 1 regardless of the internal implementation. Any advice to help me understand this would be appreciated. Thanks in advance. Darren -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Tweet button doesn't work, stills in zero
I'm putting on my site a tweet button generated using:http://
twitter.com/goodies/tweetbutton
I've twitted from different public accounts and the counter stills in
zero.
Is there some restriction on the domains used for the pages that
includes twitter resources? Because my page is under the domain
.mychnl.com. I've tested my code inside a google blog and works
there, but in my page doesn't
my code is very simple:
script type=text/javascript src=http://platform.twitter.com/
widgets.js/script
a href=http://twitter.com/share?count=verticalamp;via=pmdiazz;
class=twitter-share-buttonTweet/a
Is there some conditions that should acomplish my page? Should include
meta-tags or headers??
I was testing using this url.api:
http://urls.api.twitter.com/1/urls/count.json?url={MY_URL}
is there another tool that can help me?
Thanks in advance!!!
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: The new permission model (R / RW / RWD) is now in effect
Additionally, newly generated tokens with the My Access Token feature on
dev.twitter.com will now return an access token at the same level of access
your application requests.
If you used My Access Token to generate your token in the past, you'll
want to first go to http://twitter.com/settings/applications to revoke your
access token's permissions and then go back to dev.twitter.com's My Access
Token feature to re-negotiate an upgraded token.
Any token that transitions from one state to another will have the string
representation of the access token and secret changed: If a token goes from
RO to RW, the strings will change. If a token goes from RW to RWD, the
strings will change. If a user revokes a token and you then renegotiate the
token, even if the permission level didn't change, the strings will change.
Thanks,
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
On Thu, Jun 30, 2011 at 12:11 PM, Arnaud Meunier arn...@twitter.com wrote:
Hey Chris,
The new permission model applies to all access tokens, including the
application owner's one. You have to reauthorize your existing access_token
through the OAuth Flow, just like any other user.
Arnaud / @rno http://twitter.com/rno
On Thu, Jun 30, 2011 at 11:56 AM, Chris Teso christ...@gmail.com wrote:
I assumed that the new permissions would not apply to an app reading
it's own DMs. ie: When authenticating with an apps own token and
secret /1/direct_messages.{format} should not enforce the R/W/DM
policy.
Appears this is not the case?
On Jun 30, 11:39 am, Arnaud Meunier arn...@twitter.com wrote:
Hey Developers,
As planned, the new three-tier permission model is now officially in
effect.
Please remember that you don't have to make any changes if your
application
or service doesn't need to read or delete Direct Messages.
Key points:
- Existing oauth_tokens have not (and will not) be invalidated, even if
you
update your application permission level.
- Read/Write and Read tokens are now unable to read and delete Direct
Messages. If you wish to read or delete a user's Direct Messages, you
need
to update your application and have your existing access tokens
reauthorized
through the OAuth authorize web flow.
- All authenticated API requests return an X-Access-Level header, so
you
can find out the current permission level of the access token you're
using
(read, read-write, or read-write-directmessages).
For more information, be sure to take a look on:
- The Application Permission Model documentation page:
http://t.co/elH0KY4
- The Application Permission Model FAQ:http://t.co/1Wliqg4
Thanks again for working with us on this new permission level,
Arnaud / @rno
--
Twitter developer documentation and resources:
https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: The new permission model (R / RW / RWD) is now in effect
Arnaud Taylor,
Thanks for the response. I must say that I'm confused as to why the
decision was made to block ones own app from reading their own DMs?
Can you elaborate on the logic behind this decision?
It seems logical that I would not have to re-authorize my own app
tokens to view my own DMs. Further, I do not want to change my apps
permission levels to do so. This effects ALL of our customers solely
so I can read my own apps DMs! If I follow Taylors suggested new token
request, can I then revert my apps permissions and still access my
apps own dms? ie: I DEFINITELY do not want to keep my app permissions
set to R/W/DM when I don't need to access any customer DM data.
Thanks,
Chris
On Jun 30, 12:17 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Additionally, newly generated tokens with the My Access Token feature on
dev.twitter.com will now return an access token at the same level of access
your application requests.
If you used My Access Token to generate your token in the past, you'll
want to first go tohttp://twitter.com/settings/applicationsto revoke your
access token's permissions and then go back to dev.twitter.com's My Access
Token feature to re-negotiate an upgraded token.
Any token that transitions from one state to another will have the string
representation of the access token and secret changed: If a token goes from
RO to RW, the strings will change. If a token goes from RW to RWD, the
strings will change. If a user revokes a token and you then renegotiate the
token, even if the permission level didn't change, the strings will change.
Thanks,
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
On Thu, Jun 30, 2011 at 12:11 PM, Arnaud Meunier arn...@twitter.com wrote:
Hey Chris,
The new permission model applies to all access tokens, including the
application owner's one. You have to reauthorize your existing access_token
through the OAuth Flow, just like any other user.
Arnaud / @rno http://twitter.com/rno
On Thu, Jun 30, 2011 at 11:56 AM, Chris Teso christ...@gmail.com wrote:
I assumed that the new permissions would not apply to an app reading
it's own DMs. ie: When authenticating with an apps own token and
secret /1/direct_messages.{format} should not enforce the R/W/DM
policy.
Appears this is not the case?
On Jun 30, 11:39 am, Arnaud Meunier arn...@twitter.com wrote:
Hey Developers,
As planned, the new three-tier permission model is now officially in
effect.
Please remember that you don't have to make any changes if your
application
or service doesn't need to read or delete Direct Messages.
Key points:
- Existing oauth_tokens have not (and will not) be invalidated, even if
you
update your application permission level.
- Read/Write and Read tokens are now unable to read and delete Direct
Messages. If you wish to read or delete a user's Direct Messages, you
need
to update your application and have your existing access tokens
reauthorized
through the OAuth authorize web flow.
- All authenticated API requests return an X-Access-Level header, so
you
can find out the current permission level of the access token you're
using
(read, read-write, or read-write-directmessages).
For more information, be sure to take a look on:
- The Application Permission Model documentation page:
http://t.co/elH0KY4
- The Application Permission Model FAQ:http://t.co/1Wliqg4
Thanks again for working with us on this new permission level,
Arnaud / @rno
--
Twitter developer documentation and resources:
https://dev.twitter.com/doc
API updates via Twitter:https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources:https://dev.twitter.com/doc
API updates via Twitter:https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: The new permission model (R / RW / RWD) is now in effect
I'm seeing a number of users, and it is a minority but still, getting
403 errors
Some if these users haven't even auth'd before I changed the app
permissions.
I know it's not a global app issue as the vast majority of my users
can still access dms, including me
On Jun 30, 8:27 pm, Chris Teso christ...@gmail.com wrote:
Arnaud Taylor,
Thanks for the response. I must say that I'm confused as to why the
decision was made to block ones own app from reading their own DMs?
Can you elaborate on the logic behind this decision?
It seems logical that I would not have to re-authorize my own app
tokens to view my own DMs. Further, I do not want to change my apps
permission levels to do so. This effects ALL of our customers solely
so I can read my own apps DMs! If I follow Taylors suggested new token
request, can I then revert my apps permissions and still access my
apps own dms? ie: I DEFINITELY do not want to keep my app permissions
set to R/W/DM when I don't need to access any customer DM data.
Thanks,
Chris
On Jun 30, 12:17 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Additionally, newly generated tokens with the My Access Token feature on
dev.twitter.com will now return an access token at the same level of access
your application requests.
If you used My Access Token to generate your token in the past, you'll
want to first go tohttp://twitter.com/settings/applicationstorevoke your
access token's permissions and then go back to dev.twitter.com's My Access
Token feature to re-negotiate an upgraded token.
Any token that transitions from one state to another will have the string
representation of the access token and secret changed: If a token goes from
RO to RW, the strings will change. If a token goes from RW to RWD, the
strings will change. If a user revokes a token and you then renegotiate the
token, even if the permission level didn't change, the strings will change.
Thanks,
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
On Thu, Jun 30, 2011 at 12:11 PM, Arnaud Meunier arn...@twitter.com wrote:
Hey Chris,
The new permission model applies to all access tokens, including the
application owner's one. You have to reauthorize your existing
access_token
through the OAuth Flow, just like any other user.
Arnaud / @rno http://twitter.com/rno
On Thu, Jun 30, 2011 at 11:56 AM, Chris Teso christ...@gmail.com wrote:
I assumed that the new permissions would not apply to an app reading
it's own DMs. ie: When authenticating with an apps own token and
secret /1/direct_messages.{format} should not enforce the R/W/DM
policy.
Appears this is not the case?
On Jun 30, 11:39 am, Arnaud Meunier arn...@twitter.com wrote:
Hey Developers,
As planned, the new three-tier permission model is now officially in
effect.
Please remember that you don't have to make any changes if your
application
or service doesn't need to read or delete Direct Messages.
Key points:
- Existing oauth_tokens have not (and will not) be invalidated, even if
you
update your application permission level.
- Read/Write and Read tokens are now unable to read and delete Direct
Messages. If you wish to read or delete a user's Direct Messages, you
need
to update your application and have your existing access tokens
reauthorized
through the OAuth authorize web flow.
- All authenticated API requests return an X-Access-Level header, so
you
can find out the current permission level of the access token you're
using
(read, read-write, or read-write-directmessages).
For more information, be sure to take a look on:
- The Application Permission Model documentation page:
http://t.co/elH0KY4
- The Application Permission Model FAQ:http://t.co/1Wliqg4
Thanks again for working with us on this new permission level,
Arnaud / @rno
--
Twitter developer documentation and resources:
https://dev.twitter.com/doc
API updates via Twitter:https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources:https://dev.twitter.com/doc
API updates via Twitter:https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: The new permission model (R / RW / RWD) is now in effect
Ok, I just went through the following exercise:
1. changed app permissions to R/W/DM
2. reset oauth tokens and updated my app
3. reverted app permissions to R/W
And BOOM. Can't access my own apps DMs even with new token perms. So,
I guess I need to have ALL of our customers approve our app to read
their DMs solely so I can read my own!! I also need to have them use
the Authorize flow rather than Sign in.
Can anything be done to help me out here? To me it's obvious that
customers should not have to authorize their accounts just to give my
app permission to read it's own DMs. This is a huge downer.
On Jun 30, 12:27 pm, Chris Teso christ...@gmail.com wrote:
Arnaud Taylor,
Thanks for the response. I must say that I'm confused as to why the
decision was made to block ones own app from reading their own DMs?
Can you elaborate on the logic behind this decision?
It seems logical that I would not have to re-authorize my own app
tokens to view my own DMs. Further, I do not want to change my apps
permission levels to do so. This effects ALL of our customers solely
so I can read my own apps DMs! If I follow Taylors suggested new token
request, can I then revert my apps permissions and still access my
apps own dms? ie: I DEFINITELY do not want to keep my app permissions
set to R/W/DM when I don't need to access any customer DM data.
Thanks,
Chris
On Jun 30, 12:17 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Additionally, newly generated tokens with the My Access Token feature on
dev.twitter.com will now return an access token at the same level of access
your application requests.
If you used My Access Token to generate your token in the past, you'll
want to first go tohttp://twitter.com/settings/applicationstorevoke your
access token's permissions and then go back to dev.twitter.com's My Access
Token feature to re-negotiate an upgraded token.
Any token that transitions from one state to another will have the string
representation of the access token and secret changed: If a token goes from
RO to RW, the strings will change. If a token goes from RW to RWD, the
strings will change. If a user revokes a token and you then renegotiate the
token, even if the permission level didn't change, the strings will change.
Thanks,
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
On Thu, Jun 30, 2011 at 12:11 PM, Arnaud Meunier arn...@twitter.com wrote:
Hey Chris,
The new permission model applies to all access tokens, including the
application owner's one. You have to reauthorize your existing
access_token
through the OAuth Flow, just like any other user.
Arnaud / @rno http://twitter.com/rno
On Thu, Jun 30, 2011 at 11:56 AM, Chris Teso christ...@gmail.com wrote:
I assumed that the new permissions would not apply to an app reading
it's own DMs. ie: When authenticating with an apps own token and
secret /1/direct_messages.{format} should not enforce the R/W/DM
policy.
Appears this is not the case?
On Jun 30, 11:39 am, Arnaud Meunier arn...@twitter.com wrote:
Hey Developers,
As planned, the new three-tier permission model is now officially in
effect.
Please remember that you don't have to make any changes if your
application
or service doesn't need to read or delete Direct Messages.
Key points:
- Existing oauth_tokens have not (and will not) be invalidated, even if
you
update your application permission level.
- Read/Write and Read tokens are now unable to read and delete Direct
Messages. If you wish to read or delete a user's Direct Messages, you
need
to update your application and have your existing access tokens
reauthorized
through the OAuth authorize web flow.
- All authenticated API requests return an X-Access-Level header, so
you
can find out the current permission level of the access token you're
using
(read, read-write, or read-write-directmessages).
For more information, be sure to take a look on:
- The Application Permission Model documentation page:
http://t.co/elH0KY4
- The Application Permission Model FAQ:http://t.co/1Wliqg4
Thanks again for working with us on this new permission level,
Arnaud / @rno
--
Twitter developer documentation and resources:
https://dev.twitter.com/doc
API updates via Twitter:https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources:https://dev.twitter.com/doc
API updates via Twitter:https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Re: [twitter-dev] Re: The new permission model (R / RW / RWD) is now in effect
Hi Chris,
With the one exception of Site Streams' authorization pattern, there is no
special relationship between the account owner of an application and the
application itself -- you are just a user of your application, same as any
other user. I'm sorry that wasn't clear.
You have a few options in this scenario and I'm sure one of them will be
right for you.
* Option 1: Create a side-car application record for the purpose of reading
and responding to DMs. Set your permission level on this app to RWD. Issue
your own access token. Use this consumer key and secret for the portion of
your application that needs to read/write DMs. You would code your
application to use the appropriate set of keys for the appropriate
situation. This separates concerns and would have other benefits. If your
app tweets on its own behalf, you'd want to use your primary API keys so
that you're attributed the way you like. When creating an app for this
purpose, be sure and clearly label its intent and purpose.
* Option 2: There's a feature we've added to the OAuth flow that allows you
to specify the level of permissions you are asking for at the time of the
request. In this scenario, you would set your application to RWD but
explicitly request your end-users to receive only RW tokens by passing the
parameter x_auth_access_type=write to
api.twitter.com/oauth/request_tokenon the first step of the OAuth song
and dance. When negotiating your own
token, you'll ask for a RWD but for all end-user tokens, only RW. You leave
your application at the RWD level. More details on this option are at
http://dev.twitter.com/doc/post/oauth/request_token
Either of these options seem suitable for your scenario, with the first
option likely being your quickest solution and also the most preferable.
Unless you have a requirement to share access tokens between arms of the
application, it's a great approach for separating concerns in an app.
Let me know if you have any questions on this.
Thanks,
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
On Thu, Jun 30, 2011 at 12:27 PM, Chris Teso christ...@gmail.com wrote:
Arnaud Taylor,
Thanks for the response. I must say that I'm confused as to why the
decision was made to block ones own app from reading their own DMs?
Can you elaborate on the logic behind this decision?
It seems logical that I would not have to re-authorize my own app
tokens to view my own DMs. Further, I do not want to change my apps
permission levels to do so. This effects ALL of our customers solely
so I can read my own apps DMs! If I follow Taylors suggested new token
request, can I then revert my apps permissions and still access my
apps own dms? ie: I DEFINITELY do not want to keep my app permissions
set to R/W/DM when I don't need to access any customer DM data.
Thanks,
Chris
On Jun 30, 12:17 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Additionally, newly generated tokens with the My Access Token feature
on
dev.twitter.com will now return an access token at the same level of
access
your application requests.
If you used My Access Token to generate your token in the past, you'll
want to first go tohttp://twitter.com/settings/applicationsto revoke
your
access token's permissions and then go back to dev.twitter.com's My
Access
Token feature to re-negotiate an upgraded token.
Any token that transitions from one state to another will have the string
representation of the access token and secret changed: If a token goes
from
RO to RW, the strings will change. If a token goes from RW to RWD, the
strings will change. If a user revokes a token and you then renegotiate
the
token, even if the permission level didn't change, the strings will
change.
Thanks,
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
On Thu, Jun 30, 2011 at 12:11 PM, Arnaud Meunier arn...@twitter.com
wrote:
Hey Chris,
The new permission model applies to all access tokens, including the
application owner's one. You have to reauthorize your existing
access_token
through the OAuth Flow, just like any other user.
Arnaud / @rno http://twitter.com/rno
On Thu, Jun 30, 2011 at 11:56 AM, Chris Teso christ...@gmail.com
wrote:
I assumed that the new permissions would not apply to an app reading
it's own DMs. ie: When authenticating with an apps own token and
secret /1/direct_messages.{format} should not enforce the R/W/DM
policy.
Appears this is not the case?
On Jun 30, 11:39 am, Arnaud Meunier arn...@twitter.com wrote:
Hey Developers,
As planned, the new three-tier permission model is now officially in
effect.
Please remember that you don't have to make any changes if your
application
or service doesn't need to read or delete Direct Messages.
Key points:
- Existing oauth_tokens have not (and will not) be invalidated, even
if
you
update
[twitter-dev] Re: The new permission model (R / RW / RWD) is now in effect
Option #1 sounds perfect and will work. Thank you for the idea.
A larger issue now seems that we lost our white listing when resetting
the tokens. I realize this should not be the case, however I have
confirmed this is not an un-OAuthed issue. All API calls are going
through fine. Our rate limit has been reset though to 150/hr.
On Jun 30, 1:02 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Chris,
With the one exception of Site Streams' authorization pattern, there is no
special relationship between the account owner of an application and the
application itself -- you are just a user of your application, same as any
other user. I'm sorry that wasn't clear.
You have a few options in this scenario and I'm sure one of them will be
right for you.
* Option 1: Create a side-car application record for the purpose of reading
and responding to DMs. Set your permission level on this app to RWD. Issue
your own access token. Use this consumer key and secret for the portion of
your application that needs to read/write DMs. You would code your
application to use the appropriate set of keys for the appropriate
situation. This separates concerns and would have other benefits. If your
app tweets on its own behalf, you'd want to use your primary API keys so
that you're attributed the way you like. When creating an app for this
purpose, be sure and clearly label its intent and purpose.
* Option 2: There's a feature we've added to the OAuth flow that allows you
to specify the level of permissions you are asking for at the time of the
request. In this scenario, you would set your application to RWD but
explicitly request your end-users to receive only RW tokens by passing the
parameter x_auth_access_type=write to
api.twitter.com/oauth/request_tokenon the first step of the OAuth song
and dance. When negotiating your own
token, you'll ask for a RWD but for all end-user tokens, only RW. You leave
your application at the RWD level. More details on this option are
athttp://dev.twitter.com/doc/post/oauth/request_token
Either of these options seem suitable for your scenario, with the first
option likely being your quickest solution and also the most preferable.
Unless you have a requirement to share access tokens between arms of the
application, it's a great approach for separating concerns in an app.
Let me know if you have any questions on this.
Thanks,
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
On Thu, Jun 30, 2011 at 12:27 PM, Chris Teso christ...@gmail.com wrote:
Arnaud Taylor,
Thanks for the response. I must say that I'm confused as to why the
decision was made to block ones own app from reading their own DMs?
Can you elaborate on the logic behind this decision?
It seems logical that I would not have to re-authorize my own app
tokens to view my own DMs. Further, I do not want to change my apps
permission levels to do so. This effects ALL of our customers solely
so I can read my own apps DMs! If I follow Taylors suggested new token
request, can I then revert my apps permissions and still access my
apps own dms? ie: I DEFINITELY do not want to keep my app permissions
set to R/W/DM when I don't need to access any customer DM data.
Thanks,
Chris
On Jun 30, 12:17 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Additionally, newly generated tokens with the My Access Token feature
on
dev.twitter.com will now return an access token at the same level of
access
your application requests.
If you used My Access Token to generate your token in the past, you'll
want to first go tohttp://twitter.com/settings/applicationstorevoke
your
access token's permissions and then go back to dev.twitter.com's My
Access
Token feature to re-negotiate an upgraded token.
Any token that transitions from one state to another will have the string
representation of the access token and secret changed: If a token goes
from
RO to RW, the strings will change. If a token goes from RW to RWD, the
strings will change. If a user revokes a token and you then renegotiate
the
token, even if the permission level didn't change, the strings will
change.
Thanks,
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
On Thu, Jun 30, 2011 at 12:11 PM, Arnaud Meunier arn...@twitter.com
wrote:
Hey Chris,
The new permission model applies to all access tokens, including the
application owner's one. You have to reauthorize your existing
access_token
through the OAuth Flow, just like any other user.
Arnaud / @rno http://twitter.com/rno
On Thu, Jun 30, 2011 at 11:56 AM, Chris Teso christ...@gmail.com
wrote:
I assumed that the new permissions would not apply to an app reading
it's own DMs. ie: When authenticating with an apps own token and
secret /1/direct_messages.{format} should not enforce the R/W/DM
[twitter-dev] Re: The new permission model (R / RW / RWD) is now in effect
It appears the token and secret have be re-reset and needed time to
take effect. Rate limit is back up.
On Jun 30, 1:02 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Chris,
With the one exception of Site Streams' authorization pattern, there is no
special relationship between the account owner of an application and the
application itself -- you are just a user of your application, same as any
other user. I'm sorry that wasn't clear.
You have a few options in this scenario and I'm sure one of them will be
right for you.
* Option 1: Create a side-car application record for the purpose of reading
and responding to DMs. Set your permission level on this app to RWD. Issue
your own access token. Use this consumer key and secret for the portion of
your application that needs to read/write DMs. You would code your
application to use the appropriate set of keys for the appropriate
situation. This separates concerns and would have other benefits. If your
app tweets on its own behalf, you'd want to use your primary API keys so
that you're attributed the way you like. When creating an app for this
purpose, be sure and clearly label its intent and purpose.
* Option 2: There's a feature we've added to the OAuth flow that allows you
to specify the level of permissions you are asking for at the time of the
request. In this scenario, you would set your application to RWD but
explicitly request your end-users to receive only RW tokens by passing the
parameter x_auth_access_type=write to
api.twitter.com/oauth/request_tokenon the first step of the OAuth song
and dance. When negotiating your own
token, you'll ask for a RWD but for all end-user tokens, only RW. You leave
your application at the RWD level. More details on this option are
athttp://dev.twitter.com/doc/post/oauth/request_token
Either of these options seem suitable for your scenario, with the first
option likely being your quickest solution and also the most preferable.
Unless you have a requirement to share access tokens between arms of the
application, it's a great approach for separating concerns in an app.
Let me know if you have any questions on this.
Thanks,
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
On Thu, Jun 30, 2011 at 12:27 PM, Chris Teso christ...@gmail.com wrote:
Arnaud Taylor,
Thanks for the response. I must say that I'm confused as to why the
decision was made to block ones own app from reading their own DMs?
Can you elaborate on the logic behind this decision?
It seems logical that I would not have to re-authorize my own app
tokens to view my own DMs. Further, I do not want to change my apps
permission levels to do so. This effects ALL of our customers solely
so I can read my own apps DMs! If I follow Taylors suggested new token
request, can I then revert my apps permissions and still access my
apps own dms? ie: I DEFINITELY do not want to keep my app permissions
set to R/W/DM when I don't need to access any customer DM data.
Thanks,
Chris
On Jun 30, 12:17 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Additionally, newly generated tokens with the My Access Token feature
on
dev.twitter.com will now return an access token at the same level of
access
your application requests.
If you used My Access Token to generate your token in the past, you'll
want to first go tohttp://twitter.com/settings/applicationstorevoke
your
access token's permissions and then go back to dev.twitter.com's My
Access
Token feature to re-negotiate an upgraded token.
Any token that transitions from one state to another will have the string
representation of the access token and secret changed: If a token goes
from
RO to RW, the strings will change. If a token goes from RW to RWD, the
strings will change. If a user revokes a token and you then renegotiate
the
token, even if the permission level didn't change, the strings will
change.
Thanks,
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
On Thu, Jun 30, 2011 at 12:11 PM, Arnaud Meunier arn...@twitter.com
wrote:
Hey Chris,
The new permission model applies to all access tokens, including the
application owner's one. You have to reauthorize your existing
access_token
through the OAuth Flow, just like any other user.
Arnaud / @rno http://twitter.com/rno
On Thu, Jun 30, 2011 at 11:56 AM, Chris Teso christ...@gmail.com
wrote:
I assumed that the new permissions would not apply to an app reading
it's own DMs. ie: When authenticating with an apps own token and
secret /1/direct_messages.{format} should not enforce the R/W/DM
policy.
Appears this is not the case?
On Jun 30, 11:39 am, Arnaud Meunier arn...@twitter.com wrote:
Hey Developers,
As planned, the new three-tier permission model is now officially in
effect.
Re: [twitter-dev] Re: The new permission model (R / RW / RWD) is now in effect
On Thu, Jun 30, 2011 at 01:02:45PM -0700, Taylor Singletary wrote: * Option 2: There's a feature we've added to the OAuth flow that allows you to specify the level of permissions you are asking for at the time of the request. In this scenario, you would set your application to RWD but explicitly request your end-users to receive only RW tokens by passing the parameter x_auth_access_type=write to api.twitter.com/oauth/request_tokenon the first step of the OAuth song and dance. When negotiating your own token, you'll ask for a RWD but for all end-user tokens, only RW. You leave your application at the RWD level. More details on this option are at http://dev.twitter.com/doc/post/oauth/request_token Is it possible to (leave) the app default access level set at RW, but use x_auth_access_type to request RWD access for a specific account? It seems like it should be, however the docs for request_token only mention two possible values --- 'read' and 'write' --- for 'x_auth_access_type'. Thanks for any help! Cheers, Jeff -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Bug with the new DM authorization and the /oauth/authenticate method
Hi all, My twitter app (a firefox/chrome extension in 'browser mode') uses the method /oauth/authenticate in the oauth process. I changed the access level of my app to read, write direct messages to conform to the new rules about DM access. I observe an error 93 when the application try to read DM and the authenticate page continue to display that my app has no access to DM... If I replace /oauth/authenticate by /oauth/ authorize this issue disappears. Is it normal? Laurent -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: Best C/C++ library for Twitter JSON?
Solution: Update boost to latest version. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
