Re: [twitter-dev] Re: Could not authenticate using OAuth...
Is This a webapplication or mobile application? //kamesh On Mon, Jul 11, 2011 at 10:45 PM, Astralis astralis...@gmail.com wrote: Anyone? -- 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] Twitter Stream closed when another stream tries to connect with the same credentials..
Hi, As per the documentation, Twitter stream is closed when another stream is connected with the same credentials. Is there any method to force such that the already connected stream is not closed when another stream tries to connect with the same credentials. Thanks, Sushant -- 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 Stream closed when another stream tries to connect with the same credentials..
No, its designed to do that to prevent you from connecting more than once with a set of credentials. On 12 Jul 2011, at 10:07, sush wrote: Hi, As per the documentation, Twitter stream is closed when another stream is connected with the same credentials. Is there any method to force such that the already connected stream is not closed when another stream tries to connect with the same credentials. Thanks, Sushant -- 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 -- 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
[twitter-dev] twitter libraries
Why not classic ASP library for oauth? -- 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: Getting invalid timestamps from search API
I have started seeing this issue too. On Jul 12, 6:05 am, Doza mcard...@gmail.com wrote: Can anybody from Twitter let us know what is going on? Seems like it is not an isolated issue. Thanks, Mike On Jul 11, 10:37 pm, Adam Kent adam.k...@gmail.com wrote: I have been seeing this exact 24:00 timestamp issue too for the last few days too. Also using tweepy. thanks Adam On Jul 10, 10:37 am, Doza mcard...@gmail.com wrote: Hi everybody, My application queries the search API periodically throughout the day. I'm still working on a solution using the streaming API, but this has been working fairly well for my needs. About 4 days ago I started getting errors from the Python library that I use to perform the queries (tweepy.) It appears that some results contain what appear to be invalid timestamps. Here is a sample of the times that I see for some tweets: ValueError: time data u'Thu, 07 Jul 2011 24:58:43 +' does not match format '%a, %d %b %Y %H:%M:%S +' ValueError: time data u'Thu, 07 Jul 2011 24:59:45 +' does not match format '%a, %d %b %Y %H:%M:%S +' ValueError: time data u'Fri, 08 Jul 2011 24:58:03 +' does not match format '%a, %d %b %Y %H:%M:%S +' ValueError: time data u'Fri, 08 Jul 2011 24:33:41 +' does not match format '%a, %d %b %Y %H:%M:%S +' These timestamps all have 24 as the hour, which doesn't seem correct. Is anybody else seeing the same thing? Thanks, Mike -- 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: Getting invalid timestamps from search API
We'll look into this, thanks for the report. Would be very helpful if you can provide specific Tweet IDs where you've encountered this issue. Thanks! @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Tue, Jul 12, 2011 at 3:08 AM, Rachel Green rachelmgree...@gmail.comwrote: I have started seeing this issue too. On Jul 12, 6:05 am, Doza mcard...@gmail.com wrote: Can anybody from Twitter let us know what is going on? Seems like it is not an isolated issue. Thanks, Mike On Jul 11, 10:37 pm, Adam Kent adam.k...@gmail.com wrote: I have been seeing this exact 24:00 timestamp issue too for the last few days too. Also using tweepy. thanks Adam On Jul 10, 10:37 am, Doza mcard...@gmail.com wrote: Hi everybody, My application queries the search API periodically throughout the day. I'm still working on a solution using the streaming API, but this has been working fairly well for my needs. About 4 days ago I started getting errors from the Python library that I use to perform the queries (tweepy.) It appears that some results contain what appear to be invalid timestamps. Here is a sample of the times that I see for some tweets: ValueError: time data u'Thu, 07 Jul 2011 24:58:43 +' does not match format '%a, %d %b %Y %H:%M:%S +' ValueError: time data u'Thu, 07 Jul 2011 24:59:45 +' does not match format '%a, %d %b %Y %H:%M:%S +' ValueError: time data u'Fri, 08 Jul 2011 24:58:03 +' does not match format '%a, %d %b %Y %H:%M:%S +' ValueError: time data u'Fri, 08 Jul 2011 24:33:41 +' does not match format '%a, %d %b %Y %H:%M:%S +' These timestamps all have 24 as the hour, which doesn't seem correct. Is anybody else seeing the same thing? Thanks, Mike -- 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] Is there a standard PHP linkify routine?
Every PHP app that displays tweets needs to apply the entities as links. Is there a standard function for this available, or are hundreds of thousands of developers each rolling their own? If you have a favorite code snippet, please point it out here. Maybe we can all review them and figure out which is best. I'me specially interested in solving UTF8 character problems, which cause invalid link positioning. -- 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] Is there a standard PHP linkify routine?
I've never looked at entities but I turn URLs into links using this: $linkedtext = ereg_replace([[:alpha:]]+://[^[:space:]]+[[:alnum:]/],a href=\\\0\\\0/a, $tweet['statustext']); On Tue, Jul 12, 2011 at 10:30 AM, Adam Green 140...@gmail.com wrote: Every PHP app that displays tweets needs to apply the entities as links. Is there a standard function for this available, or are hundreds of thousands of developers each rolling their own? If you have a favorite code snippet, please point it out here. Maybe we can all review them and figure out which is best. I'me specially interested in solving UTF8 character problems, which cause invalid link positioning. -- 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: Access level changed to Read, Write AND Direct Message but still can't access DMs!
The same problem here - i am not sure if the api guys are aware of the consequences every change they make... On Jul 12, 1:33 am, Mr Blog mrblogdot...@gmail.com wrote: I have the same problem. On the App settings it is set to: Read, Write and Accessdirectmessages But when users authenticate with OAuth, it's telling users: This application will not be able to: Access yourdirectmessages. How do we fix this? On Jul 4, 5:38 pm, alexre...@gmail.com alexre...@gmail.com wrote: Most of my apps require read access forDirectMessages, but they're only reading from one account. Many users DM to one account and I need access to that one account to grab all the DMs (which no longer works as of June 30th). I changed the Access Level of all my apps to Read, Write andDirect Message, but it doesn't seem that the change has taken place, or I'm missing something, somewhere in terms of what I need to do? When I try and re-authorize an account I see the following on the Twitter / Authorize screen: This application will not be able to: Access yourdirectmessages. See your Twitter password. What else do I need to do? I have confirmed that the application settings on Twitter do say, Read, Write andDirectMessagesfor my app but I can only use my access token (for the Twitter handle associated with the app) to accessdirectmessages, anytime I try and re-authorize any account through my actual app, I see: This application will not be able to: Access yourdirectmessages. See your Twitter password. ... which isn't inline with how I setup the settings. Any help would be greatly appreciated. I'm really hoping I'm missing something small here. -- 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: Access level changed to Read, Write AND Direct Message but still can't access DMs!
Hi everyone on the thread, When you're having this problem, what endpoints are you using for authentication? Make sure that you're using https://api.twitter.com/oauth/authorize on the redirect to Twitter step of OAuth. If you're using https://api.twitter.com/oauth/authenticate, you'll never be able to negotiate a higher than RW access level token, regardless of what you've configured in your application detail settings. @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Tue, Jul 12, 2011 at 7:54 AM, twittme_mobi nlupa...@googlemail.comwrote: The same problem here - i am not sure if the api guys are aware of the consequences every change they make... On Jul 12, 1:33 am, Mr Blog mrblogdot...@gmail.com wrote: I have the same problem. On the App settings it is set to: Read, Write and Accessdirectmessages But when users authenticate with OAuth, it's telling users: This application will not be able to: Access yourdirectmessages. How do we fix this? On Jul 4, 5:38 pm, alexre...@gmail.com alexre...@gmail.com wrote: Most of my apps require read access forDirectMessages, but they're only reading from one account. Many users DM to one account and I need access to that one account to grab all the DMs (which no longer works as of June 30th). I changed the Access Level of all my apps to Read, Write andDirect Message, but it doesn't seem that the change has taken place, or I'm missing something, somewhere in terms of what I need to do? When I try and re-authorize an account I see the following on the Twitter / Authorize screen: This application will not be able to: Access yourdirectmessages. See your Twitter password. What else do I need to do? I have confirmed that the application settings on Twitter do say, Read, Write andDirectMessagesfor my app but I can only use my access token (for the Twitter handle associated with the app) to accessdirectmessages, anytime I try and re-authorize any account through my actual app, I see: This application will not be able to: Access yourdirectmessages. See your Twitter password. ... which isn't inline with how I setup the settings. Any help would be greatly appreciated. I'm really hoping I'm missing something small here. -- 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: Access level changed to Read, Write AND Direct Message but still can't access DMs!
Hello, if you refer to the OAuth settings, yes, I have: OAuth settings Your application's OAuth settings. Keep the Consumer secret a secret. This key should never be human-readable in your application. Access level Read, write, and direct messages About the application permission modelhttps://dev.twitter.com/docs/application-permission-model Request token URL https://api.twitter.com/oauth/request_token Authorize URL https://api.twitter.com/oauth/authorize Access token URL https://api.twitter.com/oauth/access_token Callback URL http://twittme.mobi/oa/callback.php I also reset the key and the secred and re-authorized one of the users but no luck. When the user is aske for permissions, I get: This application *will not be able to*: - *Access your direct messages*. - See your Twitter password. I would be really happy if I am making a mistake somewhere and you can point it out but something is just not ok here cheers! On 12 July 2011 16:13, Taylor Singletary taylorsinglet...@twitter.comwrote: Hi everyone on the thread, When you're having this problem, what endpoints are you using for authentication? Make sure that you're using https://api.twitter.com/oauth/authorize on the redirect to Twitter step of OAuth. If you're using https://api.twitter.com/oauth/authenticate, you'll never be able to negotiate a higher than RW access level token, regardless of what you've configured in your application detail settings. @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Tue, Jul 12, 2011 at 7:54 AM, twittme_mobi nlupa...@googlemail.comwrote: The same problem here - i am not sure if the api guys are aware of the consequences every change they make... On Jul 12, 1:33 am, Mr Blog mrblogdot...@gmail.com wrote: I have the same problem. On the App settings it is set to: Read, Write and Accessdirectmessages But when users authenticate with OAuth, it's telling users: This application will not be able to: Access yourdirectmessages. How do we fix this? On Jul 4, 5:38 pm, alexre...@gmail.com alexre...@gmail.com wrote: Most of my apps require read access forDirectMessages, but they're only reading from one account. Many users DM to one account and I need access to that one account to grab all the DMs (which no longer works as of June 30th). I changed the Access Level of all my apps to Read, Write andDirect Message, but it doesn't seem that the change has taken place, or I'm missing something, somewhere in terms of what I need to do? When I try and re-authorize an account I see the following on the Twitter / Authorize screen: This application will not be able to: Access yourdirectmessages. See your Twitter password. What else do I need to do? I have confirmed that the application settings on Twitter do say, Read, Write andDirectMessagesfor my app but I can only use my access token (for the Twitter handle associated with the app) to accessdirectmessages, anytime I try and re-authorize any account through my actual app, I see: This application will not be able to: Access yourdirectmessages. See your Twitter password. ... which isn't inline with how I setup the settings. Any help would be greatly appreciated. I'm really hoping I'm missing something small here. -- 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: Access level changed to Read, Write AND Direct Message but still can't access DMs!
Hi again,
here is what i have set in my Oauth library:
function accessTokenURL() { return 'https://twitter.com/oauth/access_token';
}
function authenticateURL() { return '
https://twitter.com/oauth/authenticate'; }
function authorizeURL() { return 'https://twitter.com/oauth/authorize'; }
function requestTokenURL() { return '
https://twitter.com/oauth/request_token'; }
Please advice if it needs to be changed?
On 12 July 2011 16:13, Taylor Singletary taylorsinglet...@twitter.comwrote:
Hi everyone on the thread,
When you're having this problem, what endpoints are you using for
authentication?
Make sure that you're using https://api.twitter.com/oauth/authorize on the
redirect to Twitter step of OAuth. If you're using
https://api.twitter.com/oauth/authenticate, you'll never be able to
negotiate a higher than RW access level token, regardless of what you've
configured in your application detail settings.
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
On Tue, Jul 12, 2011 at 7:54 AM, twittme_mobi nlupa...@googlemail.comwrote:
The same problem here - i am not sure if the api guys are aware of the
consequences every change they make...
On Jul 12, 1:33 am, Mr Blog mrblogdot...@gmail.com wrote:
I have the same problem.
On the App settings it is set to:
Read, Write and Accessdirectmessages
But when users authenticate with OAuth, it's telling users:
This application will not be able to:
Access yourdirectmessages.
How do we fix this?
On Jul 4, 5:38 pm, alexre...@gmail.com alexre...@gmail.com wrote:
Most of my apps require read access forDirectMessages, but they're
only reading from one account. Many users DM to one account and I
need access to that one account to grab all the DMs (which no longer
works as of June 30th).
I changed the Access Level of all my apps to Read, Write andDirect
Message, but it doesn't seem that the change has taken place, or I'm
missing something, somewhere in terms of what I need to do?
When I try and re-authorize an account I see the following on the
Twitter / Authorize screen:
This application will not be able to:
Access yourdirectmessages.
See your Twitter password.
What else do I need to do? I have confirmed that the application
settings on Twitter do say, Read, Write andDirectMessagesfor my app
but I can only use my access token (for the Twitter handle
associated with the app) to accessdirectmessages, anytime I try and
re-authorize any account through my actual app, I see:
This application will not be able to:
Access yourdirectmessages.
See your Twitter password.
... which isn't inline with how I setup the settings. Any help would
be greatly appreciated. I'm really hoping I'm missing something small
here.
--
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: Access level changed to Read, Write AND Direct Message but still can't access DMs!
On the step where you arrive at Twitter's credential screen, what URL do you
see in the browser bar?
If it's the URL that's being returned by your authenticateURL function, then
it's a URL that can't upgrade your tokens. You want to use the URL returned
in the autorizeURL function instead.
Also, these URLs are out-of-date. They should have the api subdomain
attached, like https://api.twitter.com/oauth/access_token
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
On Tue, Jul 12, 2011 at 9:05 AM, Nencho Lupanov nlupa...@googlemail.comwrote:
Hi again,
here is what i have set in my Oauth library:
function accessTokenURL() { return '
https://twitter.com/oauth/access_token'; }
function authenticateURL() { return '
https://twitter.com/oauth/authenticate'; }
function authorizeURL() { return 'https://twitter.com/oauth/authorize';
}
function requestTokenURL() { return '
https://twitter.com/oauth/request_token'; }
Please advice if it needs to be changed?
On 12 July 2011 16:13, Taylor Singletary taylorsinglet...@twitter.comwrote:
Hi everyone on the thread,
When you're having this problem, what endpoints are you using for
authentication?
Make sure that you're using https://api.twitter.com/oauth/authorize on
the redirect to Twitter step of OAuth. If you're using
https://api.twitter.com/oauth/authenticate, you'll never be able to
negotiate a higher than RW access level token, regardless of what you've
configured in your application detail settings.
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
On Tue, Jul 12, 2011 at 7:54 AM, twittme_mobi nlupa...@googlemail.comwrote:
The same problem here - i am not sure if the api guys are aware of the
consequences every change they make...
On Jul 12, 1:33 am, Mr Blog mrblogdot...@gmail.com wrote:
I have the same problem.
On the App settings it is set to:
Read, Write and Accessdirectmessages
But when users authenticate with OAuth, it's telling users:
This application will not be able to:
Access yourdirectmessages.
How do we fix this?
On Jul 4, 5:38 pm, alexre...@gmail.com alexre...@gmail.com wrote:
Most of my apps require read access forDirectMessages, but they're
only reading from one account. Many users DM to one account and I
need access to that one account to grab all the DMs (which no longer
works as of June 30th).
I changed the Access Level of all my apps to Read, Write andDirect
Message, but it doesn't seem that the change has taken place, or I'm
missing something, somewhere in terms of what I need to do?
When I try and re-authorize an account I see the following on the
Twitter / Authorize screen:
This application will not be able to:
Access yourdirectmessages.
See your Twitter password.
What else do I need to do? I have confirmed that the application
settings on Twitter do say, Read, Write andDirectMessagesfor my app
but I can only use my access token (for the Twitter handle
associated with the app) to accessdirectmessages, anytime I try and
re-authorize any account through my actual app, I see:
This application will not be able to:
Access yourdirectmessages.
See your Twitter password.
... which isn't inline with how I setup the settings. Any help would
be greatly appreciated. I'm really hoping I'm missing something
small
here.
--
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 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: Access level changed to Read, Write AND Direct Message but still can't access DMs!
Hello,
you are right!
I put the api in the front and I changed the authenticate to authorize and
it worked!
thanks - I will refer your twitter username to our app fans!
On 12 July 2011 17:11, Taylor Singletary taylorsinglet...@twitter.comwrote:
On the step where you arrive at Twitter's credential screen, what URL do
you see in the browser bar?
If it's the URL that's being returned by your authenticateURL function,
then it's a URL that can't upgrade your tokens. You want to use the URL
returned in the autorizeURL function instead.
Also, these URLs are out-of-date. They should have the api subdomain
attached, like https://api.twitter.com/oauth/access_token
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
On Tue, Jul 12, 2011 at 9:05 AM, Nencho Lupanov
nlupa...@googlemail.comwrote:
Hi again,
here is what i have set in my Oauth library:
function accessTokenURL() { return '
https://twitter.com/oauth/access_token'; }
function authenticateURL() { return '
https://twitter.com/oauth/authenticate'; }
function authorizeURL() { return 'https://twitter.com/oauth/authorize';
}
function requestTokenURL() { return '
https://twitter.com/oauth/request_token'; }
Please advice if it needs to be changed?
On 12 July 2011 16:13, Taylor Singletary taylorsinglet...@twitter.comwrote:
Hi everyone on the thread,
When you're having this problem, what endpoints are you using for
authentication?
Make sure that you're using https://api.twitter.com/oauth/authorize on
the redirect to Twitter step of OAuth. If you're using
https://api.twitter.com/oauth/authenticate, you'll never be able to
negotiate a higher than RW access level token, regardless of what you've
configured in your application detail settings.
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
On Tue, Jul 12, 2011 at 7:54 AM, twittme_mobi
nlupa...@googlemail.comwrote:
The same problem here - i am not sure if the api guys are aware of the
consequences every change they make...
On Jul 12, 1:33 am, Mr Blog mrblogdot...@gmail.com wrote:
I have the same problem.
On the App settings it is set to:
Read, Write and Accessdirectmessages
But when users authenticate with OAuth, it's telling users:
This application will not be able to:
Access yourdirectmessages.
How do we fix this?
On Jul 4, 5:38 pm, alexre...@gmail.com alexre...@gmail.com wrote:
Most of my apps require read access forDirectMessages, but they're
only reading from one account. Many users DM to one account and I
need access to that one account to grab all the DMs (which no longer
works as of June 30th).
I changed the Access Level of all my apps to Read, Write andDirect
Message, but it doesn't seem that the change has taken place, or I'm
missing something, somewhere in terms of what I need to do?
When I try and re-authorize an account I see the following on the
Twitter / Authorize screen:
This application will not be able to:
Access yourdirectmessages.
See your Twitter password.
What else do I need to do? I have confirmed that the application
settings on Twitter do say, Read, Write andDirectMessagesfor my app
but I can only use my access token (for the Twitter handle
associated with the app) to accessdirectmessages, anytime I try and
re-authorize any account through my actual app, I see:
This application will not be able to:
Access yourdirectmessages.
See your Twitter password.
... which isn't inline with how I setup the settings. Any help
would
be greatly appreciated. I'm really hoping I'm missing something
small
here.
--
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 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:
Re: [twitter-dev] Re: Could not authenticate using OAuth...
Web application. -- 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: Could not authenticate using OAuth...
It depends on what you mean by log out -- if they log out of Twitter and you have an access token they granted your application, you can use that access token until the end-user revokes your access. You can store the token forever, but that doesn't necessarily mean it will be valid forever -- the user can sever your application's access at any time. The tokens themselves do not expire without user intervention though. @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Tue, Jul 12, 2011 at 9:38 AM, Astralis astralis...@gmail.com wrote: Web application. -- 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 -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
Re: [twitter-dev] Re: Could not authenticate using OAuth...
I might be missing how this works, but I am storing the user tokens and I'm able to post through the web app onto Twitter with success. But, I found that when the user logs out of Twitter (via the Twitter website), the user's no longer able to post and the tokens seem to be invalid and I receive an error message that oAuth could not authenticate. When the user logs back into Twitter (again via the Twitter website) the tokens work again. Thoughts? -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
Re: [twitter-dev] Re: Could not authenticate using OAuth...
When your end-users are using the API, are they doing so client-side in their browser or are you making server-to-server requests on their behalf? @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Tue, Jul 12, 2011 at 10:12 AM, Astralis astralis...@gmail.com wrote: I might be missing how this works, but I am storing the user tokens and I'm able to post through the web app onto Twitter with success. But, I found that when the user logs out of Twitter (via the Twitter website), the user's no longer able to post and the tokens seem to be invalid and I receive an error message that oAuth could not authenticate. When the user logs back into Twitter (again via the Twitter website) the tokens work again. Thoughts? -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
Re: [twitter-dev] Re: Could not authenticate using OAuth...
Server-to-server requests on their behalf. -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
Re: [twitter-dev] twitter libraries
Hi Ozgur, Our list of libraries is curated from those provided to us by developers but we haven't had any OAuth compatible ASP libraries recommended to us yet. If you know of any ASP libraries let me know so we can check them out. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Twitter On Tue, Jul 12, 2011 at 1:56 AM, ozgur iamoz...@gmail.com wrote: Why not classic ASP library for oauth? -- 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 -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
[twitter-dev] Re: Getting invalid timestamps from search API
Hi Taylor, Thanks for the response. It looks like the following Tweets generated those invalid timestamps. 90208830268510208: Mon, 11 Jul 2011 24:00:35 + 90582035785195520: Tue, 12 Jul 2011 24:43:34 + 90572723142660097: Tue, 12 Jul 2011 24:06:34 + Let me know if I can provide you with any more information. Thanks, Mike On Jul 12, 10:12 am, Taylor Singletary taylorsinglet...@twitter.com wrote: We'll look into this, thanks for the report. Would be very helpful if you can provide specific Tweet IDs where you've encountered this issue. Thanks! @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Tue, Jul 12, 2011 at 3:08 AM, Rachel Green rachelmgree...@gmail.comwrote: I have started seeing this issue too. On Jul 12, 6:05 am, Doza mcard...@gmail.com wrote: Can anybody from Twitter let us know what is going on? Seems like it is not an isolated issue. Thanks, Mike On Jul 11, 10:37 pm, Adam Kent adam.k...@gmail.com wrote: I have been seeing this exact 24:00 timestamp issue too for the last few days too. Also using tweepy. thanks Adam On Jul 10, 10:37 am, Doza mcard...@gmail.com wrote: Hi everybody, My application queries the search API periodically throughout the day. I'm still working on a solution using the streaming API, but this has been working fairly well for my needs. About 4 days ago I started getting errors from the Python library that I use to perform the queries (tweepy.) It appears that some results contain what appear to be invalid timestamps. Here is a sample of the times that I see for some tweets: ValueError: time data u'Thu, 07 Jul 2011 24:58:43 +' does not match format '%a, %d %b %Y %H:%M:%S +' ValueError: time data u'Thu, 07 Jul 2011 24:59:45 +' does not match format '%a, %d %b %Y %H:%M:%S +' ValueError: time data u'Fri, 08 Jul 2011 24:58:03 +' does not match format '%a, %d %b %Y %H:%M:%S +' ValueError: time data u'Fri, 08 Jul 2011 24:33:41 +' does not match format '%a, %d %b %Y %H:%M:%S +' These timestamps all have 24 as the hour, which doesn't seem correct. Is anybody else seeing the same thing? Thanks, Mike -- 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 -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
Re: [twitter-dev] Re: Getting invalid timestamps from search API
Thanks for the helpful ids. We've identified the issue and are working on a fix. Hope to have it out later today but it's possible it won't be until later this week. Thanks for your patience! @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Tue, Jul 12, 2011 at 11:24 AM, Doza mcard...@gmail.com wrote: Hi Taylor, Thanks for the response. It looks like the following Tweets generated those invalid timestamps. 90208830268510208: Mon, 11 Jul 2011 24:00:35 + 90582035785195520: Tue, 12 Jul 2011 24:43:34 + 90572723142660097: Tue, 12 Jul 2011 24:06:34 + Let me know if I can provide you with any more information. Thanks, Mike On Jul 12, 10:12 am, Taylor Singletary taylorsinglet...@twitter.com wrote: We'll look into this, thanks for the report. Would be very helpful if you can provide specific Tweet IDs where you've encountered this issue. Thanks! @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Tue, Jul 12, 2011 at 3:08 AM, Rachel Green rachelmgree...@gmail.com wrote: I have started seeing this issue too. On Jul 12, 6:05 am, Doza mcard...@gmail.com wrote: Can anybody from Twitter let us know what is going on? Seems like it is not an isolated issue. Thanks, Mike On Jul 11, 10:37 pm, Adam Kent adam.k...@gmail.com wrote: I have been seeing this exact 24:00 timestamp issue too for the last few days too. Also using tweepy. thanks Adam On Jul 10, 10:37 am, Doza mcard...@gmail.com wrote: Hi everybody, My application queries the search API periodically throughout the day. I'm still working on a solution using the streaming API, but this has been working fairly well for my needs. About 4 days ago I started getting errors from the Python library that I use to perform the queries (tweepy.) It appears that some results contain what appear to be invalid timestamps. Here is a sample of the times that I see for some tweets: ValueError: time data u'Thu, 07 Jul 2011 24:58:43 +' does not match format '%a, %d %b %Y %H:%M:%S +' ValueError: time data u'Thu, 07 Jul 2011 24:59:45 +' does not match format '%a, %d %b %Y %H:%M:%S +' ValueError: time data u'Fri, 08 Jul 2011 24:58:03 +' does not match format '%a, %d %b %Y %H:%M:%S +' ValueError: time data u'Fri, 08 Jul 2011 24:33:41 +' does not match format '%a, %d %b %Y %H:%M:%S +' These timestamps all have 24 as the hour, which doesn't seem correct. Is anybody else seeing the same thing? Thanks, Mike -- 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 -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
[twitter-dev] Re: Twitter Mentions since_id
Thank you Taylor, I finally got it working (oh btw i scambled up my keys above before posting :) ) Mentions is now working without a problem, now im busy (and getting stuck) with direct messages as this seems to use SSL and not just the normal http as per the mentions. But I will try and sort it out myself, otherwise i know where to find help :) On Jul 6, 4:05 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hey there Paul, First, you'll want to change/reset your API keys ASAP -- you should never post your consumer secret (that signing key) on a public forum. One thing that may be amiss in your request here is that you're including an oauth_callback parameter in your header that is not in your signature base string. In fact, you shouldn't be setting an oauth_callback on any other API method other than oauth/request_token. This sort of inconsistency can easily invalidate a request. Make sure to strip this parameter out of your authorization header. When you finally get back to your mission, including since_id -- be sure and add it to your signature base string, and since this is in lexicographical order and s comes after o, it'll be the last parameter in your signature base string assuming you don't add any other additional parameters. You'll also need to include it on the querystring of your request. Hope this helps. @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Wed, Jul 6, 2011 at 5:20 AM, Paul jpb@gmail.com wrote: This is really frustrating. Thank you Tom, made the changes but no effect. Here is everything I pass and get. Im trying to do a GET for mentions. Whats the problem? :( - Generate Base URL - base=GEThttp%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses %2Fmentions.xmloauth_consumer_key%3D0RaXE4T4CuMFJHI1jViEQ %26oauth_nonce%3DDGTQVDPXRAYASJJFJLJF%26oauth_signature_method%3DHMAC- SHA1%26oauth_timestamp%3D1309954505%26oauth_token %3D298006718-8yTikfcuvQ3Xq1ZGuykhkxK2wY0ZAOxcI0jesRxd%26oauth_version %3D1.0 -- - Build Signature - -- - Request twit Start - postvars= url=http://api.twitter.com/1/statuses/mentions.xml -- - Socket Before Header Send - GET /1/statuses/mentions.xml HTTP/1.0 Accept: */* Referer:http://eden.fm User-Agent: Mozilla/4.0 (compatible; ICS) Host: api.twitter.com Authorization: OAuth oauth_nonce=DGTQVDPXRAYASJJFJLJF, oauth_callback=oob, oauth_token=298006718-8yTikfcuvQ3Xq1ZGuykhkxK2wY0ZAOxcI0jesRxd, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1309954505, oauth_consumer_key=0RaXE4T4CuMFJHI1jViEQ, oauth_signature=Q844NOw7T0oq8tNQkdR%2F6ez6Z8s%3D, oauth_version=1.0 -- - Socket Header End - HTTP/1.1 401 Unauthorized Date: Wed, 06 Jul 2011 12:16:11 GMT Server: hi Status: 401 Unauthorized WWW-Authenticate: OAuth realm=http://api.twitter.com; X-Runtime: 0.00899 Content-Type: application/xml; charset=utf-8 Content-Length: 152 Cache-Control: no-cache, max-age=1800 Set-Cookie: k=41.133.180.120.1309954571265496; path=/; expires=Wed, 13- Jul-11 12:16:11 GMT; domain=.twitter.com Set-Cookie: guest_id=v1%3A130995457172572573; domain=.twitter.com; path=/; expires=Sat, 06 Jul 2013 00:16:11 GMT Set-Cookie: original_referer=ojItV1ByhTzWh74Jc1NQEw%3D%3D; path=/ Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCNR9YP8wAToHaWQiJTQzZGVmMTE3YTI5ZjEz %250AOGYzZWEwYjlmNTRlM2I3MzA2IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA-- dd24ddb28d1207c2ebf479e57b6f9edb82553bbe; domain=.twitter.com; path=/; HttpOnly Expires: Wed, 06 Jul 2011 12:46:11 GMT Vary: Accept-Encoding Connection: close -- - Request Done Socket DocEnd - result= status code=401 headers=HTTP/1.1 401 Unauthorized Date: Wed, 06 Jul 2011 12:16:11 GMT Server: hi Status: 401 Unauthorized WWW-Authenticate: OAuth realm=http://api.twitter.com; X-Runtime: 0.00899 Content-Type: application/xml; charset=utf-8 Content-Length: 152 Cache-Control: no-cache, max-age=1800 Set-Cookie: k=41.133.180.120.1309954571265496; path=/; expires=Wed, 13- Jul-11 12:16:11 GMT; domain=.twitter.com Set-Cookie: guest_id=v1%3A130995457172572573; domain=.twitter.com; path=/; expires=Sat, 06 Jul 2013 00:16:11 GMT Set-Cookie: original_referer=ojItV1ByhTzWh74Jc1NQEw%3D%3D; path=/ Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCNR9YP8wAToHaWQiJTQzZGVmMTE3YTI5ZjEz %250AOGYzZWEwYjlmNTRlM2I3MzA2IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA-- dd24ddb28d1207c2ebf479e57b6f9edb82553bbe; domain=.twitter.com; path=/; HttpOnly Expires: Wed, 06 Jul 2011 12:46:11 GMT Vary: Accept-Encoding Connection: close -- result=?xml version=1.0 encoding=UTF-8? hash errorCould not
[twitter-dev] Re: Getting invalid timestamps from search API
Thanks, Taylor! On Jul 12, 2:47 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Thanks for the helpful ids. We've identified the issue and are working on a fix. Hope to have it out later today but it's possible it won't be until later this week. Thanks for your patience! @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Tue, Jul 12, 2011 at 11:24 AM, Doza mcard...@gmail.com wrote: Hi Taylor, Thanks for the response. It looks like the following Tweets generated those invalid timestamps. 90208830268510208: Mon, 11 Jul 2011 24:00:35 + 90582035785195520: Tue, 12 Jul 2011 24:43:34 + 90572723142660097: Tue, 12 Jul 2011 24:06:34 + Let me know if I can provide you with any more information. Thanks, Mike On Jul 12, 10:12 am, Taylor Singletary taylorsinglet...@twitter.com wrote: We'll look into this, thanks for the report. Would be very helpful if you can provide specific Tweet IDs where you've encountered this issue. Thanks! @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Tue, Jul 12, 2011 at 3:08 AM, Rachel Green rachelmgree...@gmail.com wrote: I have started seeing this issue too. On Jul 12, 6:05 am, Doza mcard...@gmail.com wrote: Can anybody from Twitter let us know what is going on? Seems like it is not an isolated issue. Thanks, Mike On Jul 11, 10:37 pm, Adam Kent adam.k...@gmail.com wrote: I have been seeing this exact 24:00 timestamp issue too for the last few days too. Also using tweepy. thanks Adam On Jul 10, 10:37 am, Doza mcard...@gmail.com wrote: Hi everybody, My application queries the search API periodically throughout the day. I'm still working on a solution using the streaming API, but this has been working fairly well for my needs. About 4 days ago I started getting errors from the Python library that I use to perform the queries (tweepy.) It appears that some results contain what appear to be invalid timestamps. Here is a sample of the times that I see for some tweets: ValueError: time data u'Thu, 07 Jul 2011 24:58:43 +' does not match format '%a, %d %b %Y %H:%M:%S +' ValueError: time data u'Thu, 07 Jul 2011 24:59:45 +' does not match format '%a, %d %b %Y %H:%M:%S +' ValueError: time data u'Fri, 08 Jul 2011 24:58:03 +' does not match format '%a, %d %b %Y %H:%M:%S +' ValueError: time data u'Fri, 08 Jul 2011 24:33:41 +' does not match format '%a, %d %b %Y %H:%M:%S +' These timestamps all have 24 as the hour, which doesn't seem correct. Is anybody else seeing the same thing? Thanks, Mike -- 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 -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussionsyet? Twitter developer links: Documentation and resources:https://dev.twitter.com/docs API updates via Twitter:https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
[twitter-dev] Place API Stream Filter?
We want to be able to filter our request on the existence of a place. If place = nil, we do not want it. Any ideas on what filter to use? -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
[twitter-dev] Tweet Button with Hashtag
I've added a hashtag to my tweet button but it appears after the title of the post and before the URL and I'd like it to appear after the URL - is this possible? -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
[twitter-dev] Re: Twitter Sentiment
I have come across many API from Twitter that help people integrate Twitter into their software. I am developing an application that Analyzes Twitter sentiments as to determine their polarity (positive or negative), for my MSc project. I am however yet to find a way to integrate Twitter into the Netbeans project so that users can be able to search for Twitter topics (through the program) and thus allowing the program to analyze the search results. Please can you help me with such API and possibly a tutorial on how it could be used. Will the tweetsentiments API be useful in your case? http://www.readwriteweb.com/hack/2010/11/api-of-the-week-tweetsentiment.php - Mohan -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
