[twitter-dev] Re: Unwanted Link Shortening with t.co
There is no way to turn it off but if you are in control of displaying the tweet as well, you can decode it with entities. On May 22, 4:50 pm, Scott Wilcox sc...@dor.ky wrote: There is currently no options for turning url-wrapping off. On 22 May 2011, at 16:47, Mo wrote: I understand what's happening. The issue is that now my domain doesn't appear in my tweets. It's a marketing issue. I'd like to know what the workaround is, since one seems to exist for other link shorteners. On May 18, 5:21 pm, Jonathan Strauss jonat...@awe.sm wrote: Twitter is just wrapping your link int.co. When it gets displayed in Twitter, it will show the link on your domain as you passed it in. On May 18, 12:35 pm, Mo maur...@moluv.com wrote: Since switching to the new Intents linking, by URLs are being shortened. I have a registered Twitter application, and a relatively short URL already (http://TagsBy.me). I'd like to continue using my own URLs, even if it means I have to build a shortener with an even shorter domain. However, I'd like to know what the rules/guidelines are that Twitter uses for overriding links, since there are many exceptions that I see in my Twitter stream. -- Scott Wilcox @dordotky | sc...@dor.ky |http://dor.ky +44 (0) 7538 842418 | +1 (646) 827-0580 -- 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
OAuth flow cannot be used from the Japanese mobile of Japan. Re: [twitter-dev] Re: A new permission level
Hello. Because the OAuth flow of twitter.com cannot be used from the Web based client for the Japanese mobile phone that we are providing, XAuth is used. (I get permission in your support.) The following problems occur if it accesses the OAuth flow from the cellular phone of a major career of Japan now. - NTT DoCoMo , Softbank 1.The over memory error happens frequently because the size of HTML and the image is large. 2.The alarm display concerning SSL goes out whenever the page is switched. - KDDI 403 errors occur on the way, and OAuth flow fails. Moreover, because JavaScript cannot be used with a lot of models, the user is confused. Because we cannot provide the DM function from the cellular phone to the user who uses it, an existing user is inconvenient the state as it is it. (The user of the Japanese mobile phone has a lot of people who do not have PC. ) Because it is thought that there is a development expert of the Japanese mobile phone of Japan in your company, Could you add the OAuth flow that can be used from web browser of the cellular phone of Japan by 6/14? -- Shinichi Fujikawa President CTO Mindscope,Inc. http://www.mindscope.co.jp http://www.mindscope.co.jp movatwi http://www.movatwi.jp (Japanese mobile based Twitter app, Winner of OPEN WEB AWARDS 2009 “Best Mobile Based Twitter App”) -- 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 www.twitter.com/sharetext=, How to remove the automatic shortened url?
Hi everybody, I discover the new page to share things on twitter: www.twitter.com/share?text= . This new page automatically add in the tweet a shortened url of the page where you're coming from, the page where you pushed the share button. The problem is that the url shortener doesn't work as well as the bit.ly one, as all the windows location hash won't be shortened too. I now search one of these two solutions: 1: make the twitter shortener work well (with #windowsHash shortened too) 2: remove the automatic url shortener of twitter from the tweets, to keep only bit.ly's one. Can somebody help me to achieve that? Thank you a lot in advance for your help! David -- 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] please give us a way to test error 93
we're ready to test. -- 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] Twitter Error codes ( not HTML errors )
Is there a list of the Twitter errors we get back ?
That is, not the HTTP errors like 401 etc, but errors like this ( in
JSON ) :
{
errors:
[
{
code:39,
message:Creation token is missing or invalid -- call
similar_places to get a valid creation token
}
]
}
--
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] Twitter Mentions since_id
Im trying to get mentions using the since_id parameter. If I leave out
the since_id parameter I get all my mentions, which is correct, but as
soon as I add the since_id, I get 401, unauthorised. Since Im VERY new
to the twitter and oAuth API, it might be the way my string is made
up, but I need some help please.
http://api.twitter.com/1/statuses/mentions.json?since_id=1oauth_consumer_key={key}oauth_nonce={key}oauth_signature_method=HMAC-SHA1oauth_signature={key}oauth_timestamp=1306132513oauth_token={key}oauth_version=1.0
Where {key} are the correct values. I've tried adding the since_id at
the back but without any luck. From the source code it seems that the
signature is created on the base code of :
http://api.twitter.com/1/statuses/mentions.json?since_id=1 and
afterwards the rest is added to that string.
Any ideas?
Thank you
--
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] crossdomain.xml status quo?
Over 1,5 years ago the question was raised about why the crossdomain.xml doesn't allow public access. https://groups.google.com/group/twitter-development-talk/browse_thread/thread/e35a708400b529b3/2a8e40506a039072 https://groups.google.com/group/twitter-development-talk/browse_thread/thread/28232e3965222037/4a9763e9a77f959c Since nothing has changed: Whats the status-quo? Will we see a change? -- 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] Additional attribute in share link
I'm looking through the FAQ for the tweet button and am not seeing one of the attributes listed. On the page, the different examples have an underscore and equal and a 13 digit number (e.g. http://twitter.com/share?_=1306165040196 ). It looks like the first 10 digits could be a unix timestamp, but I'm not 100% sure about that. It also means the three digits at the end (196) are something else. I couldn't find anything in FAQ, so I'm hoping someone can help. What is this number? Thanks. Tony -- 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] New www.twitter.com/sharetext=, How to remove the automatic shortened url?
Hey David, You can totally use your bit.ly shortened URL with the url parameter. Just remember to also specify your full URL (without the hash) using the counturl parameter in order to make your count box work properly. Exemple here: https://dev.twitter.com/pages/tweet_button#using-shorturl Hope that helps! Arnaud / @rno http://twitter.com/rno On Mon, May 23, 2011 at 7:13 AM, daviddarx david.horsf...@gmail.com wrote: Hi everybody, I discover the new page to share things on twitter: www.twitter.com/share?text= . This new page automatically add in the tweet a shortened url of the page where you're coming from, the page where you pushed the share button. The problem is that the url shortener doesn't work as well as the bit.ly one, as all the windows location hash won't be shortened too. I now search one of these two solutions: 1: make the twitter shortener work well (with #windowsHash shortened too) 2: remove the automatic url shortener of twitter from the tweets, to keep only bit.ly's one. Can somebody help me to achieve that? Thank you a lot in advance for your help! David -- 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] Additional attribute in share link
Hey Tony, This ID is automatically generated by the JavaScript Tweet Button, for internal technical reasons. It's not a property that customizes its behavior :) Arnaud / @rno http://twitter.com/rno On Mon, May 23, 2011 at 9:09 AM, Tony House tonyho...@gmail.com wrote: I'm looking through the FAQ for the tweet button and am not seeing one of the attributes listed. On the page, the different examples have an underscore and equal and a 13 digit number (e.g. http://twitter.com/share?_=1306165040196 ). It looks like the first 10 digits could be a unix timestamp, but I'm not 100% sure about that. It also means the three digits at the end (196) are something else. I couldn't find anything in FAQ, so I'm hoping someone can help. What is this number? Thanks. Tony -- 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] Twitter Mentions since_id
Hey Paul,
If you can, I recommend you use header-based OAuth (passing OAuth related
parameters in an Authorization header, instead of the query string).
Which signature base string are you using? Are you using a library? If yes,
could you share the code you're using? :)
Arnaud / @rno http://twitter.com/rno
On Sun, May 22, 2011 at 11:58 PM, Paul jpb@gmail.com wrote:
Im trying to get mentions using the since_id parameter. If I leave out
the since_id parameter I get all my mentions, which is correct, but as
soon as I add the since_id, I get 401, unauthorised. Since Im VERY new
to the twitter and oAuth API, it might be the way my string is made
up, but I need some help please.
http://api.twitter.com/1/statuses/mentions.json?since_id=1oauth_consumer_key={key}oauth_nonce={key}oauth_signature_method=HMAC-SHA1oauth_signature={key}oauth_timestamp=1306132513oauth_token={key}oauth_version=1.0
Where {key} are the correct values. I've tried adding the since_id at
the back but without any luck. From the source code it seems that the
signature is created on the base code of :
http://api.twitter.com/1/statuses/mentions.json?since_id=1 and
afterwards the rest is added to that string.
Any ideas?
Thank you
--
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: Which API to use / getting started question
Thanks for the feedback, but that's not quite what I was looking for. I'm not looking simply for a display of the user's tweets client side, but to get them server side and do stuff based on the contents of the tweet. For example (making this up), I might track the number of times a given word is used in the user's tweets or something else. On May 23, 12:59 am, Mohan Arun mar...@gmail.com wrote: Users of my app will be able to indicate that they want any of their tweets with hashtags to appear on my site as messages posted from that user. So, if I were a user who had selected this option and tweeted I like #foo, this site would see that tweet and add the same message to their site. This is essentially so that people don't have to actually directly use my app to use it. Instead, they just tweet stuff and my app picks it up (so long as it has a hash tag). I remember seeing something like this already available as an embedddable twitter widget. Can you check the available twitter widgets if this is what you need. http://twitter.com/about/resources/widgets/widget_search - Mohanhttp://www.mohanarun.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] Selling Content vs. Selling a Service
A number of chat groups have grown up around Twitter. One of the big requirements for these groups is to produce a transcript for each chat session. While the content is free, there is a cost associated with the collection of tweets and generation of the transcripts for each group. Many chat groups collect the tweets into a transcript, generate a PDF (or similar document), and post the transcripts to a common member website. 1) The Twitter TOS appears to allow the creation of chat transcripts using the API. 2) What does the TOS say about charging money for the transcripts? Would that be forbidden under Twitter's API terms (resale of tweets)? Or is it possible to sell a transcript based on the labor/technology costs involved in generating the transcript? -- 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] Streaming API credentials
I'd like to use the streaming API to track certain terms that I'll ultimately present to all of my web application's users. For instance, I want my app to display all tweets for some event, identified by some hashed term. I see that the streaming API (unlike the search API) requires authentication, either Basic or OAuth. For tinkering purposes, I've just used my own OAuth token/secret to hit the streaming API. But which credentials should my app use? Since the stream will be presented to all of my app's users, it doesn't make sense for it to use a single user's credentials. It also doesn't make much sense to open up individual, but identical streams for each user. Is there a way to consume the streaming API with some app-level credentials? -- 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] Authorize vs. Authenticate
I can't seem to find the difference, does anyone know? Previous to the new permission system I sent my users to http://twitter.com/oauth/authenticate/ But for some reason no matter what I do, it says at the bottom This application will not be able to: Access your private messages. So I changed to http://twitter.com/oauth/authorize. That solved the problem about accessing private messages. But I'd like to force the user to re-log into twitter. I can't figure out a way to do that with authorize. I just need to solve one of these 2 problems. Any ideas? Thanks, Tyson -- 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] Streaming API credentials
You would create a twitter app at https://dev.twitter.com/apps After you create it, there is a My Access Token button on the details page for your application. I /believe/ that will get you what you want. James On Mon, May 23, 2011 at 3:04 PM, Craig Walls hab...@gmail.com wrote: I'd like to use the streaming API to track certain terms that I'll ultimately present to all of my web application's users. For instance, I want my app to display all tweets for some event, identified by some hashed term. I see that the streaming API (unlike the search API) requires authentication, either Basic or OAuth. For tinkering purposes, I've just used my own OAuth token/secret to hit the streaming API. But which credentials should my app use? Since the stream will be presented to all of my app's users, it doesn't make sense for it to use a single user's credentials. It also doesn't make much sense to open up individual, but identical streams for each user. Is there a way to consume the streaming API with some app-level credentials? -- 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] Authorize vs. Authenticate
I believe the only difference is that the authenticate route could be used by only web based applications (ie they need to have a callback url) and allows for the force_login param. The authenticate can be used by either desktop or web apps, but do not support the force_login...but this may be changing soon. From themattharris earlier in the recent thread about the oauth permission change: We support multiple accounts in our application, how do we force a login on the authorize flow? Currently the only flow that supports the force_login parameter is / oauth/authenticate but adding it to /oauth/authorize flow is a good idea. We’ll begin working on this now and will let you know when it is released. On Mon, May 23, 2011 at 3:54 PM, Tyson Lowery tysonlow...@gmail.com wrote: I can't seem to find the difference, does anyone know? Previous to the new permission system I sent my users to http://twitter.com/oauth/authenticate/ But for some reason no matter what I do, it says at the bottom This application will not be able to: Access your private messages. So I changed to http://twitter.com/oauth/authorize. That solved the problem about accessing private messages. But I'd like to force the user to re-log into twitter. I can't figure out a way to do that with authorize. I just need to solve one of these 2 problems. Any ideas? Thanks, Tyson -- 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: Authorize vs. Authenticate
Ahhh, thanks that answers half my question. I did not see that from Matt - they should split that thread into technical questions and complaints, it got too hard to follow. From my testing, I am pretty sure authorize supports callback urls. Any idea about authenticate and private messages? Is this permission not available in the authenticate flow by design, or is this a bug? . On May 23, 3:01 pm, James Estes james.es...@gmail.com wrote: I believe the only difference is that the authenticate route could be used by only web based applications (ie they need to have a callback url) and allows for the force_login param. The authenticate can be used by either desktop or web apps, but do not support the force_login...but this may be changing soon. From themattharris earlier in the recent thread about the oauth permission change: We support multiple accounts in our application, how do we force a login on the authorize flow? Currently the only flow that supports the force_login parameter is / oauth/authenticate but adding it to /oauth/authorize flow is a good idea. We’ll begin working on this now and will let you know when it is released. On Mon, May 23, 2011 at 3:54 PM, Tyson Lowery tysonlow...@gmail.com wrote: I can't seem to find the difference, does anyone know? Previous to the new permission system I sent my users to http://twitter.com/oauth/authenticate/ But for some reason no matter what I do, it says at the bottom This application will not be able to: Access your private messages. So I changed tohttp://twitter.com/oauth/authorize. That solved the problem about accessing private messages. But I'd like to force the user to re-log into twitter. I can't figure out a way to do that with authorize. I just need to solve one of these 2 problems. Any ideas? Thanks, Tyson -- 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: Streaming API credentials
Correct me if I'm mistaken, but I believe that access token/secret pair are still *my* access token and secret for that application. That is, they can be used to access my personal Twitter data. I'm uncomfortable using my personal credentials (or those of any individual user) for this purpose. What I'm looking for is a token/secret that belongs to the app and can only be used to do things that required authentication, but not access an individual's data (accessing the streaming API, for instance). Perhaps I create a bogus user that represents the application and use their credentials? -- 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: Authorize vs. Authenticate
From my testing, I am pretty sure authorize supports callback urls. It does, sorry if I wasn't clear on that. So for your other question, yes, the new permission (for Read Write and Private Messages) will only be settable from the /authorize endpoint. Further up in the same thread: You said you were restricting this permission to the OAuth /authorize web flow only. Will /oauth/authenticate (Sign in with Twitter) support the new permission? The R/W/DM permission can only be granted through the /oauth/authorize route. Sign in with Twitter cannot be used to grant R/W/DM. We understand applications may use other methods of authentication like Sign in with Twitter as well. For this reason, if a user has authorised your application for R/W/DM and you direct them through Sign in with Twitter, we will respect the existing access token permission. This means you can use Sign in with Twitter after a user has authorized your application for R/W/DM. James On Mon, May 23, 2011 at 4:08 PM, Tyson Lowery tysonlow...@gmail.com wrote: Ahhh, thanks that answers half my question. I did not see that from Matt - they should split that thread into technical questions and complaints, it got too hard to follow. From my testing, I am pretty sure authorize supports callback urls. Any idea about authenticate and private messages? Is this permission not available in the authenticate flow by design, or is this a bug? . On May 23, 3:01 pm, James Estes james.es...@gmail.com wrote: I believe the only difference is that the authenticate route could be used by only web based applications (ie they need to have a callback url) and allows for the force_login param. The authenticate can be used by either desktop or web apps, but do not support the force_login...but this may be changing soon. From themattharris earlier in the recent thread about the oauth permission change: We support multiple accounts in our application, how do we force a login on the authorize flow? Currently the only flow that supports the force_login parameter is / oauth/authenticate but adding it to /oauth/authorize flow is a good idea. We’ll begin working on this now and will let you know when it is released. On Mon, May 23, 2011 at 3:54 PM, Tyson Lowery tysonlow...@gmail.com wrote: I can't seem to find the difference, does anyone know? Previous to the new permission system I sent my users to http://twitter.com/oauth/authenticate/ But for some reason no matter what I do, it says at the bottom This application will not be able to: Access your private messages. So I changed tohttp://twitter.com/oauth/authorize. That solved the problem about accessing private messages. But I'd like to force the user to re-log into twitter. I can't figure out a way to do that with authorize. I just need to solve one of these 2 problems. Any ideas? Thanks, Tyson -- 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] Checking whether a user has given permission to Private Messages
Is there a way to check whether a user has explicitly granted permission to their Private Messages? -- 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] Checking whether a user has given permission to Private Messages
I don't think so, but looks like its coming soon. From themattharris: How do we know what the access level of a user token is? This is a great idea and one the team has discussed. What we are going to do is add a new header to authentication requests that will tell you the access level of the token you authenticated with. We’re working on this now and hope to have it released in the next few days James On Mon, May 23, 2011 at 4:20 PM, Tyson Lowery tysonlow...@gmail.com wrote: Is there a way to check whether a user has explicitly granted permission to their Private Messages? -- 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: Checking whether a user has given permission to Private Messages
I think I found the answer from themattharris: How do we know what the access level of a user token is? This is a great idea and one the team has discussed. What we are going to do is add a new header to authentication requests that will tell you the access level of the token you authenticated with. We’re working on this now and hope to have it released in the next few days. -- 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: Streaming API credentials
You're right. The simplest (only?) way would be to create an account specifically for managing your app. I believe there was a recent post on this list talking about that being the norm, but I couldn't find it. I'd love for the app to have it's own credentials, and allow for assigning multiple twitter users to administer/manage the app. James On Mon, May 23, 2011 at 4:14 PM, Craig Walls hab...@gmail.com wrote: Correct me if I'm mistaken, but I believe that access token/secret pair are still *my* access token and secret for that application. That is, they can be used to access my personal Twitter data. I'm uncomfortable using my personal credentials (or those of any individual user) for this purpose. What I'm looking for is a token/secret that belongs to the app and can only be used to do things that required authentication, but not access an individual's data (accessing the streaming API, for instance). Perhaps I create a bogus user that represents the application and use their credentials? -- 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: Checking whether a user has given permission to Private Messages
We just started to return the X-Access-Level header for authenticated API requests, that tells you what access level the user token has: - read (Read-only) - read-write (Read Write) - read-write-privatemessages (Read, Write, Private Message) The FAQ on http://dev.twitter.com/pages/application-permission-model-faqwill be udpated in a minute :) Hope that helps, Arnaud / @rno http://twitter.com/rno On Mon, May 23, 2011 at 3:26 PM, Tyson Lowery tysonlow...@gmail.com wrote: I think I found the answer from themattharris: How do we know what the access level of a user token is? This is a great idea and one the team has discussed. What we are going to do is add a new header to authentication requests that will tell you the access level of the token you authenticated with. We’re working on this now and hope to have it released in the next few days. -- 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] Twitter Streaming API blocked user
Hi Taylor, What about no retweets from this user information? I wasn't able to find an API call that would provide me this information, apparently it's not available inside the status or user objects either. -- Cezar Sá Espinola On Wed, May 18, 2011 at 11:30 AM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Fabien, The Streaming API/Site Streams/User Streams don't support certain kinds of post-filter user settings like blocked users/no retweets from this user/etc. -- if you want to provide that filtering, you can keep an index of the users they block and filter in real time. http://dev.twitter.com/doc/get/blocks/blocking/ids to get the ids. @episod http://twitter.com/episod - Taylor Singletary On Tue, May 17, 2011 at 11:33 PM, Fabien Penso fabienpe...@gmail.comwrote: Hi, I'm using the streaming API (sitestream) and one of my user @thecivvie blocked @fabientest but if @fabientest tweets, I see those tweets for @thecivvie coming. Is that an implementation bug, is it supposed to be like this, or have I missed something? Thanks. -- 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
Re: [twitter-dev] Re: Checking whether a user has given permission to Private Messages
Hey again, For more consistency, the X-Access-Level header value for the Read, Write Direct Message scope is going to be read-write-directmessages (rather than read-write-privatemessages). We'll also update the Client Application management pages (using Direct Messages and not Private Messages) to match the API methods being called. Arnaud / @rno http://twitter.com/rno On Mon, May 23, 2011 at 4:18 PM, Arnaud Meunier arn...@twitter.com wrote: We just started to return the X-Access-Level header for authenticated API requests, that tells you what access level the user token has: - read (Read-only) - read-write (Read Write) - read-write-privatemessages (Read, Write, Private Message) The FAQ on http://dev.twitter.com/pages/application-permission-model-faqwill be udpated in a minute :) Hope that helps, Arnaud / @rno http://twitter.com/rno On Mon, May 23, 2011 at 3:26 PM, Tyson Lowery tysonlow...@gmail.comwrote: I think I found the answer from themattharris: How do we know what the access level of a user token is? This is a great idea and one the team has discussed. What we are going to do is add a new header to authentication requests that will tell you the access level of the token you authenticated with. We’re working on this now and hope to have it released in the next few days. -- 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] Question about rate limiting
I am developing an app that allows users to login with twitter. I'm a bit confused about the rate limiting applied to verifying credentials of users. Is it 350/hour for the application, or per user that uses the application? For example, could 1000 people signin within an hour, or am I limited to 350 per hour? -- 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
