Re: [twitter-dev] how do i know that a tweet i posted in twitter from my rails application?
Thanks Arnaud. Looking forward to see this feature implemented soon. Anu On Wed, Apr 13, 2011 at 3:17 AM, Arnaud Meunier arn...@twitter.com wrote: Hey Anu, The tweet button currently doesn't support callbacks. However, there's this Enhancement ticket you can vote for: http://code.google.com/p/twitter-api/issues/detail?id=1835 Arnaud / @rno http://twitter.com/rno On Mon, Apr 11, 2011 at 10:39 PM, anu anu...@gmail.com wrote: Hi all, I am sharing the posts made in my rails application in twitter. Here is the code I am using: div id=custom-tweet-button a href=http://twitter.com/share?url=[url_value in this palce]text=This is a test target=_blank %=image_tag(../images/share_icons/ share_this_on_twitter.png, :id=twitshare, :border = 0) % /a /div When the user clicks on the twitter sharing image, another window will open in which it asks the user to login to twitter if he is not already logged in. Then after that tweet box will appear there with text populated in it. The user can click the tweet button there and the tweet will be posted in the logged in twitter account and a confirmation message will be displayed in this window and the window will be closed in few seconds. But my problem is this: How does my application know that the tweet is posted in twitter? the application needs to give some rewards to the user upon successful tweets in twitter. Any help? Thanks, Anu -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Digest for twitter-development-talk@googlegroups.com - 13 Messages in 8 Topics
Thank you for your kindness and patience answer.
The ordinary man was MY BOSS..
Thanks again.
2011/4/13 twitter-development-talk+nore...@googlegroups.com:
Today's Topic Summary
Group: http://groups.google.com/group/twitter-development-talk/topics
Get friends who registered on my website? [1 Update]
how do i know that a tweet i posted in twitter from my rails application? [1
Update]
Users/Lookup [4 Updates]
Problem with twitter API [1 Update]
The thinking behind not drawing attention to Unfollows? [2 Updates]
Get user email from twitter [2 Updates]
users/lookup.json [1 Update]
Auto updates to twitter page [1 Update]
Topic: Get friends who registered on my website?
Ig0r ryzhkov.i...@gmail.com Apr 12 04:20PM -0700 ^
Anyone have any thoughts on this?
Please guys...
Thanks once again!
Topic: how do i know that a tweet i posted in twitter from my rails
application?
Arnaud Meunier arn...@twitter.com Apr 12 02:47PM -0700 ^
Hey Anu,
The tweet button currently doesn't support callbacks. However, there's this
Enhancement ticket you can vote for:
http://code.google.com/p/twitter-api/issues/detail?id=1835
Arnaud / @rno http://twitter.com/rno
Topic: Users/Lookup
Gabe oneill.g...@gmail.com Apr 12 12:15PM -0700 ^
Hi,
I have read all the users/lookup related posts and also scoured the
internet looking for an appropriate example.I posted a question as a
reply on one but don't see it so I am hoping someone can help a
twitter api newbie.
I just want to get results from users/lookup. I am using Abraham's
Oauth library, which I have been able to get to work in other
instances with no problems. I'm hoping it's my lack of understanding
of how the syntax should be. Here is the code:
// all values populated correctly
$connection = new TwitterOAuth(CONSUMER_KEY, CONSUMER_SECRET,
$OAuthKey, $OAuthSecret);
// saw this example as correction of the following line; neither
seems to work
$userDeets = $connection-get('/users/lookup.json',
array('screen_name' = 'biz,twitterapi'));
// $userDeets = $connection-get('/users/lookup.json?
screen_name=biz,twitterapi');
foreach ($userDeets as $item)
{
echo $item-followers_count;
echo br;
}
Thanks in advance for any insight.
-Gabe
Abraham Williams 4bra...@gmail.com Apr 12 12:25PM -0700 ^
Try:
$userDeets = $connection-get('users/lookup' array('screen_name' =
'biz,twitterapi'));
That should work.
Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
http://abrah.amJust launched from Answerly http://answerly.com:
InboxQhttp://inboxq.comfor Chrome
@abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
Gabe oneill.g...@gmail.com Apr 12 12:31PM -0700 ^
Neither works. Am I processing the results correctly?
Gabe oneill.g...@gmail.com Apr 12 01:06PM -0700 ^
Thanks to Abraham for reminding me about var_dump which showed the
results as NULL.
At risk of outing myself as stupid I will do so anyway in case there
might be someone out there who has also been searching for how to do
this, from start to finish.
This code works. The stupid part was not putting the entire URL in the
get statement. I was errantly going by a different example. Assuming
you are familiar with Abraham's Oauth library,
$connection = new TwitterOAuth(CONSUMER_KEY, CONSUMER_SECRET,
$OAuthKey, $OAuthSecret);
$userDeets = $connection-get('http://api.twitter.com/1/users/
lookup.json', array('screen_name' = 'biz, twitterapi'));
//var_dump($userDeets);
foreach ($userDeets as $item)
{
echo $item-screen_name . : ;
echo $item-followers_count;
echo br;
}
Topic: Problem with twitter API
Marco marco.ciab...@gmail.com Apr 12 12:53PM -0700 ^
Hi
I'm writing some SW who interact with twitter and some other social
network.I've to request some information(with the autentication) to
twitter profiles.Specifically i'd like to recover the email address of
the user and also the email address of his friend.I've seen how i can
autenticate with OAUTH and how recover some user profile
inormation,but i haven't found nothing about the email address.
Can you help me??
Thanks
Marco
Topic: The thinking behind not drawing attention to Unfollows?
Whonew haag.j...@gmail.com Apr 11 04:47PM -0700 ^
I just wanted to make clear that I was in no way questioning the rule.
I was just curious about the reasoning behind it, from Twitter's POV.
I, of course, came to the same logical conclusion that you did, Nick.
That it was simply to maintain a positive atmosphere and avoid
contention.
Thanks for your thoughtful replies.
- John
Brian Sutorius bsutor...@twitter.com Apr 12 01:20PM -0700 ^
For a little clarification, this policy item was added to our API
Terms of Service with the release of our User Streams and Site Streams
products. Both streams deliver negative events such as unfollows and
unfavorites
[twitter-dev] Re: Auto updates to twitter page
As I said earlier, there'll be a twitter icon on my application(WWTS Application). If content editor of my application edits this info, saves it and clicks on it, it should redirect tohttp://www.twitter.com/pwc_WWTSand should auto post the update here. Register your app for oAuth with twitter. Then your app can post status update to http://www.twitter.com/pwc_WWTS usin' API call. but first you need to register for oAuth. - Mohan -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Get friends who registered on my website?
Hmm that is a good suggestion. I'll try to do this (store only ids, because users can change their usernames on twitter) Maybe someone tried to do the same widget already? I mean Find your Twitter friends on *anysite*.com? Thanks so much Nicholas! Igor! On Apr 13, 3:31 am, Nicholas Chase nch...@earthlink.net wrote: I would store the Twitter username and id for all of your users. Then you should be able to correlate them from within your own system rather than constantly doing lookups. Nick On 4/12/2011 7:20 PM, Ig0r wrote: Anyone have any thoughts on this? Please guys... Thanks once again! On Apr 10, 5:33 pm, Ig0rryzhkov.i...@gmail.com wrote: Hello I'm coding one website which need a Find your Twitter friends here functionality. What is the best way to do it? At first I've decided to get user friends list. Then get 'name' of friends. And check that field in my website database. If names are the same - It's a possible users friend. There are 2 major problems with this approach: 1) not all users fill their correct names and surnames in twitter and other websites + If users name is too common - we will grab too many false results. 2) I can't get all of users friends: First I recursively get friends/ids 5000 ids at once. after that I make a call to users/lookup - 100 ids at once. My servers fail somewhere at users/lookup iterations. And I'm testing on user with ~5000 friends. Is there any way to get user friends bulk information? Or maybe check from a list of users who already use my twitter app? Is that possible? Thank you very much! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Twitter Search API - Questions Regarding Scaling Out
I'm still looking for a community leader answer on this one. On Apr 11, 5:50 pm, Corey Ballou ball...@gmail.com wrote: Thanks for the reply, I appreciate it. I have concerns regarding the streaming APIs, which mainly concern the following: * usage of logical OR when using locations * firehose limitations * the user’s location field is not used to filter tweets * increased application complexity for parsing the resulting stream of data back out into individual searches I know that the Search API is not Twitter's preferred choice, but it's currently returning the best applicable results for my application. It's also worth noting that the API recently received a drastic improvement to speed which should theoretically relax the strain on the API: http://engineering.twitter.com/2011/04/twitter-search-is-now-3x-faste... I guess I'm mainly interested in knowing whether @twitterapi will allow me to use the Search API in the manner I indicated above? Essentially I would be willing to guarantee the application worker nodes handles 420 rate limiting errors accordingly while still supporting multiple twitter accounts and searches. On Apr 11, 1:05 pm, M. Edward (Ed) Borasky zn...@borasky- research.net wrote: I don't see an answer here, but I'll tell you how *I* would go about implementing this: 1. Switch to the Streaming API. Using Search in an application puts a strain on Twitter's servers and makes it difficult to Twitter to manage capacity. That's why it's rate-limited and why the rate limits aren't publicly disclosed. 2. If your application is a desktop application, use User Streams. If it is a server, use User Streams on a desktop or the low-frequency free access to Streaming on a server to prototype and develop. Your target for a server will be Site Streams, but that's in closed beta at the moment IIRC. 3. *Concurrently with development*, your business development / sales / marketing / planning people, or yourself, if it's a one-person shop, should be negotiating with Twitter for access to Site Streams, I'm assuming an agile development methodology - customer-in-the-loop - and one of the parties that needs to be in the loop is Twitter for Site Streams. You simply *can't* build an at-scale Twitter application without direct business discussions with Twitter! On Mon, Apr 11, 2011 at 8:14 AM, Corey Ballou ball...@gmail.com wrote: I tried speaking with Ryan Sarver directly, but he's forwarding me here to the community advocates to answer. I believe this answer will need to come top down from Twitter, as it's your rate limiting that I'm most worried about. I have a technical question for all of you in regards to the Search API as I want to maintain full compliancy. Currently, the old Search API implementation (albeit slower) provides a fuller result set and allows for more flexibility in the types and combinations of searches allowed. The manner I have developed my application would allow for a number of daemonized worker instances running on different IP addresses to make calls to the search API on behalf of the stored OAuth credentials to avoid rate limiting issues. I had a conversation with the Pluggio developer in which he stated Twitter had threatened to shutdown his application if he didn't switch to a different implementation of the Search API. The problem indicated was that he was performing searches for multiple Twitter accounts, which is exactly my use case. Site streams does not make as much sense for my application given the search queries I wish to perform and the necessity for logical AND operations on geo-location. Do you foresee any problems with my current method of using different IP addresses to stay under the rate limit? I'm trying to stay in full compliance with Twitter's TOS and would love to find the most applicable and API friendly solution. I know headway is being made with Twitter's new search implementation so I would like to stay ahead of the curve and not get myself stuck in a box. I still need a method for polling for new search results (say, every 30 minutes, dependent upon the pricing plan) for non-logged in users. Below is a scaled down representation of how I'm currently handling searches to help you decide the best plan of action: 1) Searches are performed on a rolling queue basis, say one search every thirty minutes. There can be a finite number of searches per Twitter user (say 5 searches per Twitter account). There can be any number of Twitter accounts. 2) Search results are stored locally for retrieval by a javascript AJAX long-poller every minute to check for frequent changes. 3) When a user visits the search results page and filters results, no API calls to Twitter are made, only a local query is required Due to this process, the queue is constantly searching for the next searches
Re: [twitter-dev] Twitter Search API - Questions Regarding Scaling Out
You may want to take a look at http://datasift.net/ -Stuart -- Stuart Dallas 3ft9 Ltd http://3ft9.com/ On Monday, 11 April 2011 at 16:14, Corey Ballou wrote: I tried speaking with Ryan Sarver directly, but he's forwarding me here to the community advocates to answer. I believe this answer will need to come top down from Twitter, as it's your rate limiting that I'm most worried about. I have a technical question for all of you in regards to the Search API as I want to maintain full compliancy. Currently, the old Search API implementation (albeit slower) provides a fuller result set and allows for more flexibility in the types and combinations of searches allowed. The manner I have developed my application would allow for a number of daemonized worker instances running on different IP addresses to make calls to the search API on behalf of the stored OAuth credentials to avoid rate limiting issues. I had a conversation with the Pluggio developer in which he stated Twitter had threatened to shutdown his application if he didn't switch to a different implementation of the Search API. The problem indicated was that he was performing searches for multiple Twitter accounts, which is exactly my use case. Site streams does not make as much sense for my application given the search queries I wish to perform and the necessity for logical AND operations on geo-location. Do you foresee any problems with my current method of using different IP addresses to stay under the rate limit? I'm trying to stay in full compliance with Twitter's TOS and would love to find the most applicable and API friendly solution. I know headway is being made with Twitter's new search implementation so I would like to stay ahead of the curve and not get myself stuck in a box. I still need a method for polling for new search results (say, every 30 minutes, dependent upon the pricing plan) for non-logged in users. Below is a scaled down representation of how I'm currently handling searches to help you decide the best plan of action: 1) Searches are performed on a rolling queue basis, say one search every thirty minutes. There can be a finite number of searches per Twitter user (say 5 searches per Twitter account). There can be any number of Twitter accounts. 2) Search results are stored locally for retrieval by a javascript AJAX long-poller every minute to check for frequent changes. 3) When a user visits the search results page and filters results, no API calls to Twitter are made, only a local query is required Due to this process, the queue is constantly searching for the next searches and mentions to perform. I foresee rate limiting concerns cropping up with searches being performed for any number of users. Can you steer me in the right direction to avoid shutdown notices or access revocation? Regards, Corey @cballou -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Going All the way back on user timeline
Hi, I need the best way to go all the way back in a users timeline. Is this something I will want to be white listed for in the future? My idea was to start at a period of time do I just like do a sinceid of something really far back, then keep going by 3,200. to get all the tweets? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] 401 unauthorized on blackberry after appending ;interface=wifi
Hi On blackberry with httpConnection, I need to add network transport string such as ;interface=wifi to the url. The problem is, once I added the network transport string, I get 401 unauthorized for status update and GET statuses/user_timeline. If I remove the transport string, then I can POST updates and GET statuses everything runs fine. So it seems the request I'm sending to twitter api is correct. Is there anything special with the transport string that might cause problems? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: 401 unauthorized on blackberry after appending ;interface=wifi
There are two possible issue you are having.. Most likely you simply need to append the network transport AFTER all signatures have been generated. If you append it before, then those additional characters are being included in the signature but the BlackBerry does not actually send that part of the connection string to anyone, it is only used internally. Less likely but possible, the WIFI you are using is routing you redirecting to you a landing page to login to the WIFI access. --Naveen Ayyagari SocialScope On Apr 13, 12:41 pm, Mickey ng.mic...@gmail.com wrote: Hi On blackberry with httpConnection, I need to add network transport string such as ;interface=wifi to the url. The problem is, once I added the network transport string, I get 401 unauthorized for status update and GET statuses/user_timeline. If I remove the transport string, then I can POST updates and GET statuses everything runs fine. So it seems the request I'm sending to twitter api is correct. Is there anything special with the transport string that might cause problems? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: 401 unauthorized on blackberry after appending ;interface=wifi
Still receiving 401 during update status. There are 2 parts of my code that uses the HttpConnection where I was adding connection transport string. 1. To get the OAuth access token. The end point is https:// api.twitter.com/oauth/request_token. I removed the code to add transport string here. So my signature should not contain the transport string. 2. Doing an update, the URL thus becomes http://api.twitter.com/1/ statuses/update.json;interface=wifi The result is still 401. Any idea? Thanks On Apr 13, 4:04 pm, Naveen knig...@gmail.com wrote: There are two possible issue you are having.. Most likely you simply need to append the network transport AFTER all signatures have been generated. If you append it before, then those additional characters are being included in the signature but the BlackBerry does not actually send that part of the connection string to anyone, it is only used internally. Less likely but possible, the WIFI you are using is routing you redirecting to you a landing page to login to the WIFI access. --Naveen Ayyagari SocialScope On Apr 13, 12:41 pm, Mickey ng.mic...@gmail.com wrote: Hi On blackberry with httpConnection, I need to add network transport string such as ;interface=wifi to the url. The problem is, once I added the network transport string, I get 401 unauthorized for status update and GET statuses/user_timeline. If I remove the transport string, then I can POST updates and GET statuses everything runs fine. So it seems the request I'm sending to twitter api is correct. Is there anything special with the transport string that might cause problems? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] How to detect a gap in timeline ?
Most iPhone apps have the feature to detect gaps in timeline ? how can i know that there's a gap between to tweets ??? thank you. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Inconsistent OAuth behavior in streaming api
Hi there, I'm working on a ruby client for the streaming API and am getting hung up on OAuth. When making requests to /1/statuses/filter.json with an OAuth authorization header via a POST, I immediately receive a 401 Unauthorized. GET requests with an OAuth authorization header are working however. This behavior appears to contradict the streaming documentation which says that the request method for statuses/filter should be a POST. http://dev.twitter.com/pages/streaming_api_methods#statuses-filter Is this a known issue or am I missing something here? Thanks, Steve -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
