[twitter-dev] xAuth - sometimes success response, sometimes Error-response
Hello, I´m using xAuth in an ActionScript 3.0 Project. I still have problems that I sometimes get a successful response, and a couple of times a faulty response. If I get a bad response, then I have the HTTP status code 401 with following error message: Failed to validate oauth signature and token The values that are different are the oAuth_nonce and oAuth_timestamp. The oAuth_nonce is determined by a random number. This is determined by the uuid of the current date. Subcontent special characters such as: - removed. Such uuid should be unique. I wonder why I for similar calculations of the nonce, etc. sometimes successful and sometimes get a bad response! -- 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] Re: Help converting Basic Auth to oAuth
It might be the following but you can var_dump() $tweets and see the
structure of it to be sure.
foreach ($tweets as $tweet) {
echo $tweet->status->text;
}
Abraham
-
Abraham Williams | Hacker Advocate | http://abrah.am
Update: http://blog.abrah.am/2010/10/organizing-my-life.html
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Fri, Oct 1, 2010 at 02:17, Lorraine wrote:
> Thanks again, but now am getting:
> Warning: Invalid argument supplied for foreach()
>
> It looks correct to me, so I'm confused about the warning.
>
> Thanks
> Lorraine
>
> On Fri, Oct 1, 2010 at 3:54 AM, Abraham Williams <4bra...@gmail.com>wrote:
>
>> You don't need the cURL and XML code.
>>
>> require_once('twitteroauth.php');
>> $connection = new TwitterOAuth('consumer key', 'consumer secret', 'access
>> token', 'access token secret');
>> $tweets = $connection->get('statuses/friends_timeline');
>> $latesttweets = count($tweets);
>>
>> foreach ($tweets->status as $tweet) {
>> echo $tweet->text;
>> }
>>
>>
>> Abraham
>> -
>> Abraham Williams | Hacker Advocate | http://abrah.am
>> @abraham | http://projects.abrah.am | http://blog.abrah.am
>> This email is: [ ] shareable [x] ask first [ ] private.
>>
>>
>> On Thu, Sep 30, 2010 at 11:38, Lorraine wrote:
>>
>>> Thank you so much, Abraham! I'm getting an error "String could not be
>>> parsed as XML" now- this is what I now have (with my reset consumer keys put
>>> in :-)):
>>>
>>>
>>> require_once('twitteroauth.php');
>>> $connection = new TwitterOAuth('consumer key', 'consumer secret', 'access
>>> token', 'access token secret');
>>> $tweets = $connection->get('statuses/friends_timeline');
>>> $latesttweets = count($tweets);
>>>
>>> $tw = curl_init();
>>> curl_setopt($tw, CURLOPT_URL, $tweets);
>>> curl_setopt($tw, CURLOPT_RETURNTRANSFER, TRUE);
>>>
>>> $twi = curl_exec($tw);
>>> $tweeters = new SimpleXMLElement($twi);
>>>
>>> I then go on to grab data using
>>> foreach ($tweeters->status as $twit1) {
>>>
>>> etc.
>>>
>>> Thanks again,
>>> Lorraine
>>>
>>> On Fri, Oct 1, 2010 at 2:13 AM, Abraham Williams <4bra...@gmail.com>wrote:
>>>
Make sure you reset your consumer key on http://dev.twitter.com/appsand
try not to post them in public in the future.
This should work. I switched it to json as it didn't look like you
needed the actual xml and dropped the count as 20 is the default.
require_once('twitteroauth.php');
$connection = new TwitterOAuth('consumer key', 'consumer secret',
'access token', 'access token secret');
$tweets = $connection->get('statuses/friends_timeline');
$latesttweets = count($tweets);
Abraham
-
Abraham Williams | Hacker Advocate | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Thu, Sep 30, 2010 at 02:38, Lorraine wrote:
> Maybe I should explain what I'm trying to do-- basically just want to
> get my own status updates and the (public) details & updates of my
> friends.
>
> Would it work if I replaced this:
> $login = "mytwitterusername:mytwitterpassword";
> $tweets = "http://twitter.com/statuses/friends_timeline.xml?count=20";;
>
> with this?:
>
> require_once('twitteroauth.php');
> $connection = new TwitterOAuth('6Oe8P3U72LimBkfGsj0h1A',
> 'XVX67blKxfro001KDq1PZLV6QwZ5Et1TnmeVBexMqI', '769601-
> PXr5egoxYccGKnua9cg58QNfVMIyiXsEFUtkOPoH0',
> 'P7JiGIKvMg8TsaKgxU9azAi8cZwerZyshu1VHwoPbD8');
> $connection->format = 'xml';
> $tweets = $connection->get('statuses/friends_timeline.xml?count=20');
>
> $tw = curl_init();
> curl_setopt($tw, CURLOPT_URL, $tweets);
> curl_setopt($tw, CURLOPT_RETURNTRANSFER, TRUE);
>
> $twi = curl_exec($tw);
> $tweeters = new SimpleXMLElement($twi);
> $latesttweets = count($tweeters);
>
> ... or am I completely off the mark?
>
> Thanks very much :)
> Lorraine
>
> --
> 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 developer documentation and resources:
>>> http://dev.twitter.com/doc
>>> API updates via Twitter: http://twitter.com/twitterap
[twitter-dev] Re: twitter streams API question
Thanks John and Tom. Appreciate it. Rakesh On Sep 30, 6:33 pm, John Kalucki wrote: > If the result set size per time period is below the rate limit, you > get the full result set. Otherwise the part of the result set above > the limit is discarded, and you get a notice to that effect. Note that > with relevance enabled in search, it's not always full-fidelity result > set either, especially for higher velocity predicates. > > Seehttp://dev.twitter.com/pages/streaming_api_concepts#filter-limiting > for more details` > > -John Kaluckihttp://twitter.com/jkalucki > Twitter, Inc. > > On Thu, Sep 30, 2010 at 5:37 AM, Tom van der Woerdt wrote: > > > > > Filter = all, just like search. > > > Tom > > > On Sep 30, 2010, at 2:24 PM, rakesh wrote: > > >> Hi All - > > >> Could someone please answer this for me - > > >> If I use curl to execute the following - > > >> curl -d @locationshttp://stream.twitter.com/1/statuses/filter.json- > >> uAnyTwitterUser:Password > > >> and my 'locations' parameter had a bounding box for 'dallas, tx' - > >> would I then get ALL (exhaustively) tweets from the public timeline > >> from Dallas with geocodes? > > >> Would this be a sample of tweets and not all of them? > > >> Could someone answer conclusively? > > >> Thx > > >> Rakesh > > >> -- > >> 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 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] Re: search results - how far does it go back
Hey Quy, Search is focused on real-time relevant Tweets, so the index is fairly short. At the moment the index is ~5 days of relevant Tweets. I hope that answers your question, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Mon, Oct 4, 2010 at 1:32 PM, Tim Bull wrote: > The time window depends on how busy Twitter is as a whole - the search > is not a fixed timeframe. > > On Oct 5, 7:16 am, Quy wrote: >> When try to search on results from a user like "from:mashable", I only >> see results going as far back as 24 hours? I thought the archive went >> back further for a search. > > -- > 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] Trying to get multiple related values working for the Twitter Button
Hey Duncan, What you are doing is correct. Up to two accounts can be recommended and are added the way you have coded. For example: data-related="twitter,twitterapi" or: related=twitter,twitterapi If the account doesn't show as a related account when it should - which appears to be the case here - the account holder should contact our user support team so they can check everything is ok. Hope that answers your question, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Mon, Oct 4, 2010 at 2:53 PM, Duncan Mackenzie wrote: > Hey folks, on my pages (like ...) I'm writing out a script reference > that includes a via account and multiple twitter accounts in the > related param and the related values don't seem to be picked up > > the script reference on that page linked above is > http://platform.twitter.com/widgets/tweet_button.html?_=1286227939014&count=horizontal&lang=en&text=SIlverlight%20TV%2047:%20Silverlight%20and%20Windows%20Phone%207%20Performance%20Tips%20%7C%20Silverlight%20TV%20%7C%20Channel%209&url=http://channel9.msdn.com/Shows/SilverlightTV/SIlverlight-TV-47-Silverlight-and-Windows-Phone-7-Performance-Tips&via=ch9&related=John_Papa,ch9 > > (the docs don't describe how to include multiple accounts, but on > http://groups.google.com/group/twitter-development-talk/browse_thread/thread/6e1571d1c2ad49aa/9389f8b6fdecd338?lnk=gst&q=related#9389f8b6fdecd338 > it mentions "related attribute takes a comma separated list of > accounts") > > The resulting pop-up dialog : has a URL of > http://twitter.com/share?_=1286227939014&count=horizontal&original_referer=http%3A%2F%2Fchannel9.msdn.com%2FShows%2FSilverlightTV%2FSIlverlight-TV-47-Silverlight-and-Windows-Phone-7-Performance-Tips&related=John_Papa%2Cch9&text=SIlverlight%20TV%2047%3A%20Silverlight%20and%20Windows%20Phone%207%20Performance%20Tips%20|%20Silverlight%20TV%20|%20Channel%209&url=http%3A%2F%2Fchannel9.msdn.com%2FShows%2FSilverlightTV%2FSIlverlight-TV-47-Silverlight-and-Windows-Phone-7-Performance-Tips&via=ch9 > > the 'related' data is ending up in that URL, but the John_Papa account > is not being recommended (and the tweeting account does *not* follow > John_Papa already), only the via account (ch9) is ever being > recommended. > > Anyone have any advice on making multiple related values work via the > query parameter of the script reference? > > -- > 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] Re: How long is it taking for support tickets to be reviewed and is it possible to expedite them?
Thanks Taylor, I appreciate you taking a look. It's interesting that "the account is suspended, not the application". One side effect of this appears to be that while users who have authenticated continue to remain authenticated to our application, the OAuth API appears to be refusing to issue tokens for new users - presumably because our account is suspended? Anyway, on to how we would avoid this in the future. Simply put, in this proving stage for a new application we try to quickly approach a Minimum Viable Product (MVP) and we were quite ruthless in throwing out features / enhancements if there was another manual way of doing something in the very short-term. In terms of gaining feedback from our users, the approach we took of sending @messages to the authenticated users clearly upsets the Spam Gods and therefore isn't a suitable mechanism - we should of invested in a different approach. Here's four things we could of done differently to achieve a similar outcome that wouldn't upset Twitter: 1. Collect the users email address before, or after they authenticate with OAuth and make it part of the profile we store. We could make this a mandatory or optional step for using our application. Either way we'd have at least some email addresses and permission to email users directly so we could send the survey to them. We would make it optional given we allow anonymous users anyway! 2. Provide a link or callout on the homepage with the survey for returning users. 3. After some period of use, popup a call out in the application asking users to provide feedback. Annoying yes, but valuable to us in this early stage and we need only do it once. This has a big advantage in that it would capture both Authenticated and Anonymous users. 4. On close of the application, popup a survey link. Of these options a combination of 2 and 3 would probably be the most suitable for us, especially if we made sure that once a user had seen a message they didn't see it again (or perhaps if they saw message 3 and cancelled, they'd see message 2 on return and never again if they cancelled after that). Cheers, Tim On Oct 5, 8:14 am, Taylor Singletary wrote: > Hi Tim, > > We looked into your request but unfortunately cannot expedite resolving it > right now. In this case, the account used to post the tweets was suspended > -- not your application. While there's obviously a good deal of overlap > between API policy/enforcement and account policy/enforcement, this kind of > suspension falls squarely in the "account policy" camp. The support team's > response time is actually quite good right now, and I imagine you'll be > hearing back from them soon. > > Thanks for the keen understanding on what went wrong here -- since there are > obviously many developers who might find themselves facing the same scenario > at some point, can you share a bit on what actions you'll take to avoid this > in the future? > > Thanks! > Taylor > > > > On Mon, Oct 4, 2010 at 1:48 PM, Tim Bull wrote: > > Our application (twitter.com/distlr) has had it's account suspended > > and I need this reviewed. I (think I) understand why it was > > suspended, which was stupidity on my part rather than anything > > malicious or bad on the part of the application itself. > > > We follow a very lean start-up approach: > > > * We had the idea for Distlr and immediately interviewed people and > > asked them if they'd use it. > > * When they said Yes, we prototyped it with @anywhere and put it in > > front of them, then surveyed them and asked if they'd use it. > > * When they said yes, we developed a very alpha version with full > > OAuth integration, incorporating their feedback and put it front of a > > bigger audience. Around 60 people registered and 400 used it > > anonymously. > > > Unsurprisingly if you follow the thread here, I then went to survey > > these 60 registered users - I created a Google Form and then (being > > very lean and not trying over engineering things) started sending the > > messages from the Distlr account to each of the registered users. > > > "@usera @userb @etc Thanks for using Distlr. Would love your feedback > > via this short survey:http://bit.ly/distlrsurvey"; > > > After several of these, the Distlr account was suspended. > > > Immediately when this happened, I've slapped my forehead with the > > biggest "Doh!" you've heard. As I've explained in the ticket, this is > > more user stupidity on my part rather than anything malicious the > > application itself is doing. > > > It's holding us up because while the ticket is Open, I'm loath to move > > the app to a new account as it may look like we are trying to be > > underhanded, which we absolutely aren't. Unless Twitter knows > > differently, I really don't think the app itself is misbehaving, I > > think it's just these survey links which have caused the concern. > > > How long are these support tickets taking to be reviewed (it's been > > open over 17 hours now) and is
[twitter-dev] Trying to get multiple related values working for the Twitter Button
Hey folks, on my pages (like ...) I'm writing out a script reference that includes a via account and multiple twitter accounts in the related param and the related values don't seem to be picked up the script reference on that page linked above is http://platform.twitter.com/widgets/tweet_button.html?_=1286227939014&count=horizontal&lang=en&text=SIlverlight%20TV%2047:%20Silverlight%20and%20Windows%20Phone%207%20Performance%20Tips%20%7C%20Silverlight%20TV%20%7C%20Channel%209&url=http://channel9.msdn.com/Shows/SilverlightTV/SIlverlight-TV-47-Silverlight-and-Windows-Phone-7-Performance-Tips&via=ch9&related=John_Papa,ch9 (the docs don't describe how to include multiple accounts, but on http://groups.google.com/group/twitter-development-talk/browse_thread/thread/6e1571d1c2ad49aa/9389f8b6fdecd338?lnk=gst&q=related#9389f8b6fdecd338 it mentions "related attribute takes a comma separated list of accounts") The resulting pop-up dialog : has a URL of http://twitter.com/share?_=1286227939014&count=horizontal&original_referer=http%3A%2F%2Fchannel9.msdn.com%2FShows%2FSilverlightTV%2FSIlverlight-TV-47-Silverlight-and-Windows-Phone-7-Performance-Tips&related=John_Papa%2Cch9&text=SIlverlight%20TV%2047%3A%20Silverlight%20and%20Windows%20Phone%207%20Performance%20Tips%20|%20Silverlight%20TV%20|%20Channel%209&url=http%3A%2F%2Fchannel9.msdn.com%2FShows%2FSilverlightTV%2FSIlverlight-TV-47-Silverlight-and-Windows-Phone-7-Performance-Tips&via=ch9 the 'related' data is ending up in that URL, but the John_Papa account is not being recommended (and the tweeting account does *not* follow John_Papa already), only the via account (ch9) is ever being recommended. Anyone have any advice on making multiple related values work via the query parameter of the script reference? -- 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] How long is it taking for support tickets to be reviewed and is it possible to expedite them?
Hi Tim, We looked into your request but unfortunately cannot expedite resolving it right now. In this case, the account used to post the tweets was suspended -- not your application. While there's obviously a good deal of overlap between API policy/enforcement and account policy/enforcement, this kind of suspension falls squarely in the "account policy" camp. The support team's response time is actually quite good right now, and I imagine you'll be hearing back from them soon. Thanks for the keen understanding on what went wrong here -- since there are obviously many developers who might find themselves facing the same scenario at some point, can you share a bit on what actions you'll take to avoid this in the future? Thanks! Taylor On Mon, Oct 4, 2010 at 1:48 PM, Tim Bull wrote: > Our application (twitter.com/distlr) has had it's account suspended > and I need this reviewed. I (think I) understand why it was > suspended, which was stupidity on my part rather than anything > malicious or bad on the part of the application itself. > > We follow a very lean start-up approach: > > * We had the idea for Distlr and immediately interviewed people and > asked them if they'd use it. > * When they said Yes, we prototyped it with @anywhere and put it in > front of them, then surveyed them and asked if they'd use it. > * When they said yes, we developed a very alpha version with full > OAuth integration, incorporating their feedback and put it front of a > bigger audience. Around 60 people registered and 400 used it > anonymously. > > Unsurprisingly if you follow the thread here, I then went to survey > these 60 registered users - I created a Google Form and then (being > very lean and not trying over engineering things) started sending the > messages from the Distlr account to each of the registered users. > > "@usera @userb @etc Thanks for using Distlr. Would love your feedback > via this short survey: http://bit.ly/distlrsurvey"; > > After several of these, the Distlr account was suspended. > > Immediately when this happened, I've slapped my forehead with the > biggest "Doh!" you've heard. As I've explained in the ticket, this is > more user stupidity on my part rather than anything malicious the > application itself is doing. > > It's holding us up because while the ticket is Open, I'm loath to move > the app to a new account as it may look like we are trying to be > underhanded, which we absolutely aren't. Unless Twitter knows > differently, I really don't think the app itself is misbehaving, I > think it's just these survey links which have caused the concern. > > How long are these support tickets taking to be reviewed (it's been > open over 17 hours now) and is it possible that someone from the > Twitter dev support team can help out with getting it reviewed sooner > please? If we have to wait, we have to wait, but we'd love to > progress forwards with the feedback we did get from the few people > that filled out the survey before the account got suspended. > > The ticket is http://support.twitter.com/tickets/1256917 > > Thanks! > > Tim Bull > > -- > 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] How long is it taking for support tickets to be reviewed and is it possible to expedite them?
Our application (twitter.com/distlr) has had it's account suspended and I need this reviewed. I (think I) understand why it was suspended, which was stupidity on my part rather than anything malicious or bad on the part of the application itself. We follow a very lean start-up approach: * We had the idea for Distlr and immediately interviewed people and asked them if they'd use it. * When they said Yes, we prototyped it with @anywhere and put it in front of them, then surveyed them and asked if they'd use it. * When they said yes, we developed a very alpha version with full OAuth integration, incorporating their feedback and put it front of a bigger audience. Around 60 people registered and 400 used it anonymously. Unsurprisingly if you follow the thread here, I then went to survey these 60 registered users - I created a Google Form and then (being very lean and not trying over engineering things) started sending the messages from the Distlr account to each of the registered users. "@usera @userb @etc Thanks for using Distlr. Would love your feedback via this short survey: http://bit.ly/distlrsurvey"; After several of these, the Distlr account was suspended. Immediately when this happened, I've slapped my forehead with the biggest "Doh!" you've heard. As I've explained in the ticket, this is more user stupidity on my part rather than anything malicious the application itself is doing. It's holding us up because while the ticket is Open, I'm loath to move the app to a new account as it may look like we are trying to be underhanded, which we absolutely aren't. Unless Twitter knows differently, I really don't think the app itself is misbehaving, I think it's just these survey links which have caused the concern. How long are these support tickets taking to be reviewed (it's been open over 17 hours now) and is it possible that someone from the Twitter dev support team can help out with getting it reviewed sooner please? If we have to wait, we have to wait, but we'd love to progress forwards with the feedback we did get from the few people that filled out the survey before the account got suspended. The ticket is http://support.twitter.com/tickets/1256917 Thanks! Tim Bull -- 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: search results - how far does it go back
The time window depends on how busy Twitter is as a whole - the search is not a fixed timeframe. On Oct 5, 7:16 am, Quy wrote: > When try to search on results from a user like "from:mashable", I only > see results going as far back as 24 hours? I thought the archive went > back further for a search. -- 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] search results - how far does it go back
When try to search on results from a user like "from:mashable", I only see results going as far back as 24 hours? I thought the archive went back further for a search. -- 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: Ultimately send my twitter followers direct messages from my application
Our Automation Rules ( http://support.twitter.com/articles/76915 ) include guidelines for automating DMs when a user follows you. Specifically, we do not prohibit this behavior but we do not recommend it. The 250 DMs per day limit that Thomas mentioned is correct. Brian Sutorius On Oct 2, 11:25 am, Thomas Mango wrote: > Yes, there's a limit of 250 direct messages per day according > to:http://support.twitter.com/forums/10711/entries/15364 > > I'm not sure if there are any policies against automatically direct messaging > someone when they follow you, but a 250/day would certainly prevent that at > some point. I don't know the details of your application, but if you were > only planning to send new followers a direct message, perhaps you can avoid > asking them to follow you and sending them a direct message by just showing > them what you wanted to message them when they come back from the OAuth > authorization. > > -- > Thomas Mango > > On Oct 2, 2010, at 1:12 PM, "Dean Collins" wrote: > > > > > Thomas are there restrictions on what/how many direct messages can be sent? > > > I haven't been paying attention with twitter for a while but I thought > > twitter banned automatic direct messages. > > > Thanks in advance, > > Dean > > > I think what you described is exactly right. You're looking for an app > > that users can authorize with using OAuth. Once they're redirected back > > to your site (part of the OAuth process), you can create a user account > > for them locally and ask them to follow your Twitter account. Because > > they've authorized your application, when they agree to follow you, you > > can use the /friendships/create API method on their behalf. > > > Relevant API documentation: > >http://dev.twitter.com/pages/auth > >http://dev.twitter.com/doc/post/friendships/create > > > Dialflow wrote: > >> Hi: > > >> I was wondering if any one could suggest an elegant approach to > >> ultimately sending direct messages to my Twitter followers from my > >> application. > > >> I'd like people that join web site to do the following: > > >> From their member page on my site, I'd like for them to click a > >> Twitter follow button, go to Twitter, follow me, then return to their > >> member page on my site. > > >> After they do this, I want capture their twitter ID and associate it > >> with their user account on my site so I can send them direct messages > >> from my application. > > >> I'd really appreciate an elegant approach to solving this. > > >> I guess I'm looking for an answer like: "Use oAuth to have the user > >> authorize your app on Twitter, then redirect redirect back to your > >> app, click a twittter follow button, and extract their Twitter ID from > >> "x_file" and then" > > >> My days of programming are way behind me so I hope that makes some > >> sense. > > >> Thanks so much. > >> Curtis > > > -- > > Thomas Mango > > tsma...@gmail.com > > > -- > > 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 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] Re: Streaming API test: Adding new_id field to statuses at 17:00 UTC Sept 29
I dug back to Mark's email for context, but I still can't puzzle out what Mark was referring to and what you are asking for. The answer might be buried somewhere in that 74 message thread. Could you restate your question? Does the count parameter do what you need? -John Kalucki http://twitter.com/jkalucki Twitter, Inc On Sun, Oct 3, 2010 at 9:28 PM, Walter Santos wrote: > Hi, John > > Does Twitter still plan to implement backfill support in streaming > API? In an older post from > Mark McBride (April, 2010), he said: > > "To alleviate some of the concerns raised in this > thread we thought it would be useful to give more details about how we > plan > to generate IDs ... > ... 4) We will provide a way to backfill from the streaming API. ..." > > Thanks! > > On 28 set, 18:34, John Kalucki wrote: >> Tomorrow, Wednesday September 29, at 10:00 AM PDT / 17:00 UTC, we will >> briefly introduce a field called new_id to statuses delivered over >> theStreamingAPI. If this 10 minute test is successful, we will enable >> the new_id field continuously on Thursday September 30th at about the >> same time. Note that timelines returned by the REST and Search APIs >> will not contain this field. This new_id field will allow applications >> to preview thenewstatusidgeneration scheme before the primary key >> transition scheduled for Tuesday October 12th. >> >> For more information on our statusidtransition: >> >> http://groups.google.com/group/twitter-api-announce/browse_thread/thr...http://groups.google.com/group/twitter-api-announce/browse_thread/thr... >> >> -John Kaluckihttp://twitter.com/jkalucki >> Twitter, Inc. > > -- > 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] Tweet Button Problems
I am not a developer, but when I asked for help from Twitter support, they directed me to ask this group my question. Here is my problem that I sent to Twitter support: "I need help with the Tweet button. When I customize under URL to "The URL for the page the button is on" then tweet from it, it doesn't go to the blog post the button is on. Rather it takes me to a blank page with the tiny tweet button up in the left-hand corner. I'm confused. Maybe my blog won't allow it to work that way? I have since changed the button in my latest post to just link to my blog's main URL, so it just goes to the homepage rather than the newest post. My blog is made in iWeb. Is that the problem? Thank you!" Any guidance would be greatly appreciated. -- 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] twurl errors in cron
Hi TJ, The shell environment in a cron job is not necessarily the same environment as when you execute scripts from your user account. Here's an article with some tips on debugging the running environment while in a cron job: http://stackoverflow.com/questions/2135478/how-to-simulate-the-environment-cron-executes-a-script-with Essentially, you'll need to make sure that the environment is aware of the location of Ruby, Rubygems, and the gems required to execute Twurl. Taylor On Mon, Oct 4, 2010 at 11:56 AM, TJ Luoma wrote: > I'm getting the following error when running > > twurl -t "/1/statuses/user_timeline/amazondeals.rss" > > in a cron script: > > > /home/luomat/.gem/ruby/1.8/gems/twurl-0.6.0/bin/../lib/twurl/configuration_controller.rb:2: > uninitialized constant Twurl::AbstractCommandController (NameError) > from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in > `gem_original_require' > from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require' > from > /home/luomat/.gem/ruby/1.8/gems/twurl-0.6.0/bin/../lib/twurl.rb:10 > from > /home/luomat/.gem/ruby/1.8/gems/twurl-0.6.0/bin/../lib/twurl.rb:9:in > `each' > from > /home/luomat/.gem/ruby/1.8/gems/twurl-0.6.0/bin/../lib/twurl.rb:9 > from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in > `gem_original_require' > from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require' > from /home/luomat/.gem/ruby/1.8/gems/twurl-0.6.0/bin/twurl:2 > from /home/luomat/bin/twurl:19:in `load' > from /home/luomat/bin/twurl:19 > > I have no idea what this means, or if it is important or not. > > TjL > > -- > 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] twurl errors in cron
I'm getting the following error when running twurl -t "/1/statuses/user_timeline/amazondeals.rss" in a cron script: /home/luomat/.gem/ruby/1.8/gems/twurl-0.6.0/bin/../lib/twurl/configuration_controller.rb:2: uninitialized constant Twurl::AbstractCommandController (NameError) from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require' from /home/luomat/.gem/ruby/1.8/gems/twurl-0.6.0/bin/../lib/twurl.rb:10 from /home/luomat/.gem/ruby/1.8/gems/twurl-0.6.0/bin/../lib/twurl.rb:9:in `each' from /home/luomat/.gem/ruby/1.8/gems/twurl-0.6.0/bin/../lib/twurl.rb:9 from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require' from /home/luomat/.gem/ruby/1.8/gems/twurl-0.6.0/bin/twurl:2 from /home/luomat/bin/twurl:19:in `load' from /home/luomat/bin/twurl:19 I have no idea what this means, or if it is important or not. TjL -- 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: Got rejected to be on Twitter whitelist and i'm not sure why
Great, thanks for your prompt response! On Oct 4, 2:01 pm, Taylor Singletary wrote: > I don't mean that, strictly, no. Most Twitter API calls have the concept of > a "current user" -- in basic auth, that concept of a "current user" was > indicated by a valid username and password associated with each API call. > Our most employed authorization form at this time is OAuth 1.0a, which > exchanges the user's express permission for you to act on their behalf for > an access token that represents that permission. It's this access token that > would accompany requests made on a user's behalf, and > ultimately represent the user in the same way a login and password did in > the past. > > Taylor > > > > On Mon, Oct 4, 2010 at 10:55 AM, Theswalker wrote: > > When you say "if your API calls are > > executed from the perspective of a member (represented by an access > > token)" Do you mean require the user to pass username and password > > credentials to get updates? > > > On Oct 4, 1:05 pm, Taylor Singletary > > wrote: > > > There are many options with the Twitter API today. There are a number of > > > streaming-based products, like the core Streaming API, User Streams, and > > > Site Streams. Streaming technologies give developers alternate > > > implementation paths to monitor tweets of certain users, certain keyword > > > searches, and numerous other use cases. > > > > By using Streaming in conjunction with the REST API, the vast majority of > > > developers should never require whitelisting. Further, if your API calls > > are > > > executed from the perspective of a member (represented by an access > > token), > > > you'll have 350 requests per hour/user for supplemental API requests. > > > > If your application requires more API calls than this to continue > > > functioning, you may need to explore other implementation options, such > > as > > > streaming APIs, even more aggressive caching, or more complex request > > > queueing systems. Have a user that needs more than 350 requests in an > > hour > > > to completely process for some operation in your application? Queue the > > rest > > > of your operations for later. You essentially have 8,400 requests per day > > to > > > make requests on behalf of a user. > > > > Taylor > > > > On Mon, Oct 4, 2010 at 9:50 AM, Theswalker > > wrote: > > > > I was rejected just now and i'm not sure why really. I read the link > > > > they sent me and i comply with all of the requests. I have a caching > > > > server that updates users latest tweets that puts that information in > > > > a database. When someone visits a users profile page, i return the > > > > cached results instead of updating on page loads. My site has over 200 > > > > users right now and i hit the limit every time my server updates the > > > > cache and i dont know what to do now. It's pointless for me to even > > > > have twitter as an option on my site if it wont allow my site to grow > > > > past 150 users. Can anyone help me or give me any pointers on how to > > > > get whitelisted? The link says to do the following: > > > > > 1. Caching - which i do already. > > > > > I update a users stream once every 30 minutes and store that > > > > information in my caching server. > > > > > 2. Rate limiting by active user. If your site keeps track of many > > > > Twitter users (for example, fetching their current status or > > > > statistics about their Twitter usage), please consider only requesting > > > > data for users who have recently signed in to your site. > > > > > The point of my site is to allow users to link different social > > > > networks on their profile and send it around to friends and not have > > > > to login to get it to update. > > > > > Any help will be appreciated. > > > > > Thanks > > > > > -- > > > > 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 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: User_Timeline - include_rts not working
Further note that in testing, if I set the count parameter to 1 to return a single record and page through the friends_timeline, I actually get certain pages that return no data. i.e. I can page through a single tweet at a time and still get some responses that are empty. So the API is clearly first retrieving a record (or group of records) and then applying some other filter to it. Its that other filter that I need to figure out so that I can craft the request to ensure that I always get back the requested number of records (except when there are no more records). I don't see any way to retrieve the TOTAL number of records for a particular query either. If I could know for sure that a shortage of returned records on a particular page was due to some filter and that there truly are more records on subsequent pages, then I could at least use this as a workaround. On Oct 4, 11:48 am, timrnicholson wrote: > Well, I thought i had this problem solved. I am using a library called > twitteroauth and it was stripping off the "&include_rts=true". I > finally figured out that include_rts needed to be placed into an > arguments array instead of being in the request URL. > > So once I got the include_rts parm passed to Twitter everything > wasworkingfine. Or at least it was in most cases. HOWEVER, I am seeing > now that certain requests areNOTreturning the fullcountparameter > worth of records. There must be SOME filtering that the Twitter API is > doing AFTER it retrieves thecountnumber worth of records. I have > this problem regardless of whether I use the home_timeline which is > supposed to always include everything or whether I use the > friends_timeline with the include_rtsparameter. > > Note that I am trying to requestcount= 25 records,notthe defaultcount= 20 > records. I can see that retweets are being included and I'm > still getting ust 24 records back in certain cases. > > On Sep 9, 10:06 am, Matt Harris wrote: > > > > > Hey Tim, > > > When I run: > > curl > > "http://api.twitter.com/1/statuses/user_timeline/RWW.xml?count=20&page..."; > > > I get the expected result of 20 statuses one retweet (from > > @ConanOBrien). When you make the request are you running it like I am > > or are you using a library? > > > To answer your query about thecountparameter. The behavior is this: > > we will try and return up to 'count' statuses in one request, wherecountis > > equal to all statuses in the timeline before any filtering of > > retweets. So, if you request 20 statuses without retweets, and 1 of > > the statuses is a retweet, you will get 19 statuses back. > > > Hope that helps explain what is going on, > > Matt > > > On Thu, Sep 9, 2010 at 7:30 AM, timrnicholson > > wrote: > > > I'm properly calling api.twitter.com/1/statuses/user_timeline with > > > include_rts as true and retweets arenotbeing included. The only > > > stream that I can get to return retweets (because it doesn't even > > > require the include_rtsparameter) is the home_timeline. > > > > For example, the following doesn't work: > > >http://api.twitter.com/1/statuses/user_timeline/RWW.xml?count=20&page... > > > > The worst part about this isnotjust that the include_rtsparameter > > > doesn't work for including retweets, the returned timeline doesn't > > > even have 20 records in it when there are retweets. In other words, > > > the API isnotonly ignoring the include_rtsparameterbut itsnot > > > even returning the right number of requested records when it thinks > > > include_rts is false. > > > > This totally screws up my pagination methods because I'm getting less > > > than the expected number of records back, so my app thinks there's no > > > more timeline to be retrieved. I certainly don't want to just always > > > include a "next page" link when there really aren't any more records > > > left. > > > > Also, thecountparameteris being ignored in all of this as well, but > > > I've latched on to another thread about that. > > > > On Aug 30, 12:50 pm, Taylor Singletary > > > wrote: > > >> Hi Timmerk, > > > >> Make sure you're using api.twitter.com as the host for all of your API > > >> requests. The proper API isnotat twitter.com -- it's at api.twitter.com. > > >> Include_rts willnotwork against twitter.com (and one day you'll find all > > >> of your requests rejected.) > > > >> Also, please note that proper API routes include a version component. The > > >> call you're making should > > >> be:http://api.twitter.com/1/statuses/user_timeline.json?screen_name=NuWa... > > > >> Taylor > > > >> On Mon, Aug 30, 2010 at 10:43 AM, timmerk wrote: > > >> > I'm having the same issue - you can see an example here: > > > >> >http://twitter.com/statuses/user_timeline.json?screen_name=NuWaveGOV&;... > > > >> > As you can see, there are no retweets included in the JSON. > > > >> > Thanks! > > > >> > On Aug 25, 2:30 pm, Matt Harris wrote: > > >> > > Hey Hen, > > > >> > > Are you still finding retweets arenotshowing up for you? > > > >> > > Matt > >
Re: [twitter-dev] Re: User_Timeline - include_rts not working
I'm getting the same issue - http://groups.google.com/group/twitter-development-talk/browse_thread/thread/3c13f89ac3c5a945.Still without any solution :( 2010/10/4 timrnicholson > Well, I thought i had this problem solvIed. I am using a library called > twitteroauth and it was stripping off the "&include_rts=true". I > finally figured out that include_rts needed to be placed into an > arguments array instead of being in the request URL. > > So once I got the include_rts parm passed to Twitter everything was > working fine. Or at least it was in most cases. HOWEVER, I am seeing > now that certain requests are NOT returning the full count parameter > worth of records. There must be SOME filtering that the Twitter API is > doing AFTER it retrieves the count number worth of records. I have > this problem regardless of whether I use the home_timeline which is > supposed to always include everything or whether I use the > friends_timeline with the include_rts parameter. > > Note that I am trying to request count = 25 records, not the default > count = 20 records. I can see that retweets are being included and I'm > still getting ust 24 records back in certain cases. > > On Sep 9, 10:06 am, Matt Harris wrote: > > Hey Tim, > > > > When I run: > > curl " > http://api.twitter.com/1/statuses/user_timeline/RWW.xml?count=20&page..."; > > > > I get the expected result of 20 statuses one retweet (from > > @ConanOBrien). When you make the request are you running it like I am > > or are you using a library? > > > > To answer your query about thecountparameter. The behavior is this: > > we will try and return up to 'count' statuses in one request, > wherecountis equal to all statuses in the timeline before any filtering of > > retweets. So, if you request 20 statuses without retweets, and 1 of > > the statuses is a retweet, you will get 19 statuses back. > > > > Hope that helps explain what is going on, > > Matt > > > > > > > > > > > > On Thu, Sep 9, 2010 at 7:30 AM, timrnicholson > wrote: > > > I'm properly calling api.twitter.com/1/statuses/user_timeline with > > > include_rts as true and retweets arenotbeing included. The only > > > stream that I can get to return retweets (because it doesn't even > > > require the include_rtsparameter) is the home_timeline. > > > > > For example, the following doesn't work: > > >http://api.twitter.com/1/statuses/user_timeline/RWW.xml?count=20&page. > .. > > > > > The worst part about this isnotjust that the include_rtsparameter > > > doesn't work for including retweets, the returned timeline doesn't > > > even have 20 records in it when there are retweets. In other words, > > > the API isnotonly ignoring the include_rtsparameterbut itsnot > > > even returning the right number of requested records when it thinks > > > include_rts is false. > > > > > This totally screws up my pagination methods because I'm getting less > > > than the expected number of records back, so my app thinks there's no > > > more timeline to be retrieved. I certainly don't want to just always > > > include a "next page" link when there really aren't any more records > > > left. > > > > > Also, thecountparameteris being ignored in all of this as well, but > > > I've latched on to another thread about that. > > > > > On Aug 30, 12:50 pm, Taylor Singletary > > > wrote: > > >> Hi Timmerk, > > > > >> Make sure you're using api.twitter.com as the host for all of your > API > > >> requests. The proper API isnotat twitter.com -- it's at > api.twitter.com. > > >> Include_rts willnotwork against twitter.com (and one day you'll find > all > > >> of your requests rejected.) > > > > >> Also, please note that proper API routes include a version component. > The > > >> call you're making should be: > http://api.twitter.com/1/statuses/user_timeline.json?screen_name=NuWa... > > > > >> Taylor > > > > >> On Mon, Aug 30, 2010 at 10:43 AM, timmerk wrote: > > >> > I'm having the same issue - you can see an example here: > > > > >> > > http://twitter.com/statuses/user_timeline.json?screen_name=NuWaveGOV&;... > > > > >> > As you can see, there are no retweets included in the JSON. > > > > >> > Thanks! > > > > >> > On Aug 25, 2:30 pm, Matt Harris wrote: > > >> > > Hey Hen, > > > > >> > > Are you still finding retweets arenotshowing up for you? > > > > >> > > Matt > > > > >> > > On Sat, Aug 21, 2010 at 7:19 AM, henasraf > wrote: > > >> > > > Matt, > > >> > > > Any user I show in my app wouldnotshow retweets, even if they > surely > > >> > > > exist. You can see for yourself athttp:// > wosaic.net/twitguin(still > > >> > > > early stages, don't mind it being a bit lame), see any user such > as > > >> > > > myself athttp://wosaic.net/twitguin/user/henasraf;youmay go > > >> > > > through pages and see that no retweets ever show; they should be > color > > >> > > > coded in orange. You can compare tohttp:// > twitter.com/henasraftosee > > >> > > > retweets that should show. > > > > >> > > > Thanks, > > >> > > > Hen > > > > >> > > >
Re: [twitter-dev] Re: Got rejected to be on Twitter whitelist and i'm not sure why
I don't mean that, strictly, no. Most Twitter API calls have the concept of a "current user" -- in basic auth, that concept of a "current user" was indicated by a valid username and password associated with each API call. Our most employed authorization form at this time is OAuth 1.0a, which exchanges the user's express permission for you to act on their behalf for an access token that represents that permission. It's this access token that would accompany requests made on a user's behalf, and ultimately represent the user in the same way a login and password did in the past. Taylor On Mon, Oct 4, 2010 at 10:55 AM, Theswalker wrote: > When you say "if your API calls are > executed from the perspective of a member (represented by an access > token)" Do you mean require the user to pass username and password > credentials to get updates? > > On Oct 4, 1:05 pm, Taylor Singletary > wrote: > > There are many options with the Twitter API today. There are a number of > > streaming-based products, like the core Streaming API, User Streams, and > > Site Streams. Streaming technologies give developers alternate > > implementation paths to monitor tweets of certain users, certain keyword > > searches, and numerous other use cases. > > > > By using Streaming in conjunction with the REST API, the vast majority of > > developers should never require whitelisting. Further, if your API calls > are > > executed from the perspective of a member (represented by an access > token), > > you'll have 350 requests per hour/user for supplemental API requests. > > > > If your application requires more API calls than this to continue > > functioning, you may need to explore other implementation options, such > as > > streaming APIs, even more aggressive caching, or more complex request > > queueing systems. Have a user that needs more than 350 requests in an > hour > > to completely process for some operation in your application? Queue the > rest > > of your operations for later. You essentially have 8,400 requests per day > to > > make requests on behalf of a user. > > > > Taylor > > > > > > > > On Mon, Oct 4, 2010 at 9:50 AM, Theswalker > wrote: > > > I was rejected just now and i'm not sure why really. I read the link > > > they sent me and i comply with all of the requests. I have a caching > > > server that updates users latest tweets that puts that information in > > > a database. When someone visits a users profile page, i return the > > > cached results instead of updating on page loads. My site has over 200 > > > users right now and i hit the limit every time my server updates the > > > cache and i dont know what to do now. It's pointless for me to even > > > have twitter as an option on my site if it wont allow my site to grow > > > past 150 users. Can anyone help me or give me any pointers on how to > > > get whitelisted? The link says to do the following: > > > > > 1. Caching - which i do already. > > > > > I update a users stream once every 30 minutes and store that > > > information in my caching server. > > > > > 2. Rate limiting by active user. If your site keeps track of many > > > Twitter users (for example, fetching their current status or > > > statistics about their Twitter usage), please consider only requesting > > > data for users who have recently signed in to your site. > > > > > The point of my site is to allow users to link different social > > > networks on their profile and send it around to friends and not have > > > to login to get it to update. > > > > > Any help will be appreciated. > > > > > Thanks > > > > > -- > > > 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 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] Got rejected to be on Twitter whitelist and i'm not sure why
The one "weak link" in Twitter's current offering is the ability to do "deep" searching into historical tweet data. As far as I know, the only way one can do that at present is via Topsy's (beta) search, and their business model is, shall we say, not clear. ;-) -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb "A mathematician is a device for turning coffee into theorems." - Paul Erdos Quoting Taylor Singletary : There are many options with the Twitter API today. There are a number of streaming-based products, like the core Streaming API, User Streams, and Site Streams. Streaming technologies give developers alternate implementation paths to monitor tweets of certain users, certain keyword searches, and numerous other use cases. By using Streaming in conjunction with the REST API, the vast majority of developers should never require whitelisting. Further, if your API calls are executed from the perspective of a member (represented by an access token), you'll have 350 requests per hour/user for supplemental API requests. If your application requires more API calls than this to continue functioning, you may need to explore other implementation options, such as streaming APIs, even more aggressive caching, or more complex request queueing systems. Have a user that needs more than 350 requests in an hour to completely process for some operation in your application? Queue the rest of your operations for later. You essentially have 8,400 requests per day to make requests on behalf of a user. Taylor On Mon, Oct 4, 2010 at 9:50 AM, Theswalker wrote: I was rejected just now and i'm not sure why really. I read the link they sent me and i comply with all of the requests. I have a caching server that updates users latest tweets that puts that information in a database. When someone visits a users profile page, i return the cached results instead of updating on page loads. My site has over 200 users right now and i hit the limit every time my server updates the cache and i dont know what to do now. It's pointless for me to even have twitter as an option on my site if it wont allow my site to grow past 150 users. Can anyone help me or give me any pointers on how to get whitelisted? The link says to do the following: 1. Caching - which i do already. I update a users stream once every 30 minutes and store that information in my caching server. 2. Rate limiting by active user. If your site keeps track of many Twitter users (for example, fetching their current status or statistics about their Twitter usage), please consider only requesting data for users who have recently signed in to your site. The point of my site is to allow users to link different social networks on their profile and send it around to friends and not have to login to get it to update. Any help will be appreciated. Thanks -- 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 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: Got rejected to be on Twitter whitelist and i'm not sure why
When you say "if your API calls are executed from the perspective of a member (represented by an access token)" Do you mean require the user to pass username and password credentials to get updates? On Oct 4, 1:05 pm, Taylor Singletary wrote: > There are many options with the Twitter API today. There are a number of > streaming-based products, like the core Streaming API, User Streams, and > Site Streams. Streaming technologies give developers alternate > implementation paths to monitor tweets of certain users, certain keyword > searches, and numerous other use cases. > > By using Streaming in conjunction with the REST API, the vast majority of > developers should never require whitelisting. Further, if your API calls are > executed from the perspective of a member (represented by an access token), > you'll have 350 requests per hour/user for supplemental API requests. > > If your application requires more API calls than this to continue > functioning, you may need to explore other implementation options, such as > streaming APIs, even more aggressive caching, or more complex request > queueing systems. Have a user that needs more than 350 requests in an hour > to completely process for some operation in your application? Queue the rest > of your operations for later. You essentially have 8,400 requests per day to > make requests on behalf of a user. > > Taylor > > > > On Mon, Oct 4, 2010 at 9:50 AM, Theswalker wrote: > > I was rejected just now and i'm not sure why really. I read the link > > they sent me and i comply with all of the requests. I have a caching > > server that updates users latest tweets that puts that information in > > a database. When someone visits a users profile page, i return the > > cached results instead of updating on page loads. My site has over 200 > > users right now and i hit the limit every time my server updates the > > cache and i dont know what to do now. It's pointless for me to even > > have twitter as an option on my site if it wont allow my site to grow > > past 150 users. Can anyone help me or give me any pointers on how to > > get whitelisted? The link says to do the following: > > > 1. Caching - which i do already. > > > I update a users stream once every 30 minutes and store that > > information in my caching server. > > > 2. Rate limiting by active user. If your site keeps track of many > > Twitter users (for example, fetching their current status or > > statistics about their Twitter usage), please consider only requesting > > data for users who have recently signed in to your site. > > > The point of my site is to allow users to link different social > > networks on their profile and send it around to friends and not have > > to login to get it to update. > > > Any help will be appreciated. > > > Thanks > > > -- > > 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] Got rejected to be on Twitter whitelist and i'm not sure why
There are many options with the Twitter API today. There are a number of streaming-based products, like the core Streaming API, User Streams, and Site Streams. Streaming technologies give developers alternate implementation paths to monitor tweets of certain users, certain keyword searches, and numerous other use cases. By using Streaming in conjunction with the REST API, the vast majority of developers should never require whitelisting. Further, if your API calls are executed from the perspective of a member (represented by an access token), you'll have 350 requests per hour/user for supplemental API requests. If your application requires more API calls than this to continue functioning, you may need to explore other implementation options, such as streaming APIs, even more aggressive caching, or more complex request queueing systems. Have a user that needs more than 350 requests in an hour to completely process for some operation in your application? Queue the rest of your operations for later. You essentially have 8,400 requests per day to make requests on behalf of a user. Taylor On Mon, Oct 4, 2010 at 9:50 AM, Theswalker wrote: > I was rejected just now and i'm not sure why really. I read the link > they sent me and i comply with all of the requests. I have a caching > server that updates users latest tweets that puts that information in > a database. When someone visits a users profile page, i return the > cached results instead of updating on page loads. My site has over 200 > users right now and i hit the limit every time my server updates the > cache and i dont know what to do now. It's pointless for me to even > have twitter as an option on my site if it wont allow my site to grow > past 150 users. Can anyone help me or give me any pointers on how to > get whitelisted? The link says to do the following: > > 1. Caching - which i do already. > > I update a users stream once every 30 minutes and store that > information in my caching server. > > 2. Rate limiting by active user. If your site keeps track of many > Twitter users (for example, fetching their current status or > statistics about their Twitter usage), please consider only requesting > data for users who have recently signed in to your site. > > The point of my site is to allow users to link different social > networks on their profile and send it around to friends and not have > to login to get it to update. > > Any help will be appreciated. > > Thanks > > -- > 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] Got rejected to be on Twitter whitelist and i'm not sure why
I was rejected just now and i'm not sure why really. I read the link they sent me and i comply with all of the requests. I have a caching server that updates users latest tweets that puts that information in a database. When someone visits a users profile page, i return the cached results instead of updating on page loads. My site has over 200 users right now and i hit the limit every time my server updates the cache and i dont know what to do now. It's pointless for me to even have twitter as an option on my site if it wont allow my site to grow past 150 users. Can anyone help me or give me any pointers on how to get whitelisted? The link says to do the following: 1. Caching - which i do already. I update a users stream once every 30 minutes and store that information in my caching server. 2. Rate limiting by active user. If your site keeps track of many Twitter users (for example, fetching their current status or statistics about their Twitter usage), please consider only requesting data for users who have recently signed in to your site. The point of my site is to allow users to link different social networks on their profile and send it around to friends and not have to login to get it to update. Any help will be appreciated. Thanks -- 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: User_Timeline - include_rts not working
Well, I thought i had this problem solved. I am using a library called twitteroauth and it was stripping off the "&include_rts=true". I finally figured out that include_rts needed to be placed into an arguments array instead of being in the request URL. So once I got the include_rts parm passed to Twitter everything was working fine. Or at least it was in most cases. HOWEVER, I am seeing now that certain requests are NOT returning the full count parameter worth of records. There must be SOME filtering that the Twitter API is doing AFTER it retrieves the count number worth of records. I have this problem regardless of whether I use the home_timeline which is supposed to always include everything or whether I use the friends_timeline with the include_rts parameter. Note that I am trying to request count = 25 records, not the default count = 20 records. I can see that retweets are being included and I'm still getting ust 24 records back in certain cases. On Sep 9, 10:06 am, Matt Harris wrote: > Hey Tim, > > When I run: > curl > "http://api.twitter.com/1/statuses/user_timeline/RWW.xml?count=20&page..."; > > I get the expected result of 20 statuses one retweet (from > @ConanOBrien). When you make the request are you running it like I am > or are you using a library? > > To answer your query about thecountparameter. The behavior is this: > we will try and return up to 'count' statuses in one request, wherecountis > equal to all statuses in the timeline before any filtering of > retweets. So, if you request 20 statuses without retweets, and 1 of > the statuses is a retweet, you will get 19 statuses back. > > Hope that helps explain what is going on, > Matt > > > > > > On Thu, Sep 9, 2010 at 7:30 AM, timrnicholson wrote: > > I'm properly calling api.twitter.com/1/statuses/user_timeline with > > include_rts as true and retweets arenotbeing included. The only > > stream that I can get to return retweets (because it doesn't even > > require the include_rtsparameter) is the home_timeline. > > > For example, the following doesn't work: > >http://api.twitter.com/1/statuses/user_timeline/RWW.xml?count=20&page... > > > The worst part about this isnotjust that the include_rtsparameter > > doesn't work for including retweets, the returned timeline doesn't > > even have 20 records in it when there are retweets. In other words, > > the API isnotonly ignoring the include_rtsparameterbut itsnot > > even returning the right number of requested records when it thinks > > include_rts is false. > > > This totally screws up my pagination methods because I'm getting less > > than the expected number of records back, so my app thinks there's no > > more timeline to be retrieved. I certainly don't want to just always > > include a "next page" link when there really aren't any more records > > left. > > > Also, thecountparameteris being ignored in all of this as well, but > > I've latched on to another thread about that. > > > On Aug 30, 12:50 pm, Taylor Singletary > > wrote: > >> Hi Timmerk, > > >> Make sure you're using api.twitter.com as the host for all of your API > >> requests. The proper API isnotat twitter.com -- it's at api.twitter.com. > >> Include_rts willnotwork against twitter.com (and one day you'll find all > >> of your requests rejected.) > > >> Also, please note that proper API routes include a version component. The > >> call you're making should > >> be:http://api.twitter.com/1/statuses/user_timeline.json?screen_name=NuWa... > > >> Taylor > > >> On Mon, Aug 30, 2010 at 10:43 AM, timmerk wrote: > >> > I'm having the same issue - you can see an example here: > > >> >http://twitter.com/statuses/user_timeline.json?screen_name=NuWaveGOV&;... > > >> > As you can see, there are no retweets included in the JSON. > > >> > Thanks! > > >> > On Aug 25, 2:30 pm, Matt Harris wrote: > >> > > Hey Hen, > > >> > > Are you still finding retweets arenotshowing up for you? > > >> > > Matt > > >> > > On Sat, Aug 21, 2010 at 7:19 AM, henasraf wrote: > >> > > > Matt, > >> > > > Any user I show in my app wouldnotshow retweets, even if they surely > >> > > > exist. You can see for yourself athttp://wosaic.net/twitguin(still > >> > > > early stages, don't mind it being a bit lame), see any user such as > >> > > > myself athttp://wosaic.net/twitguin/user/henasraf;youmay go > >> > > > through pages and see that no retweets ever show; they should be > >> > > > color > >> > > > coded in orange. You can compare tohttp://twitter.com/henasraftosee > >> > > > retweets that should show. > > >> > > > Thanks, > >> > > > Hen > > >> > > > On Aug 19, 11:34 pm, Matt Harris wrote: > >> > > >> Hey, > > >> > > >> Retweets should be included if they exist in the users timeline when > >> > you > >> > > >> request them. For example if you request 20 Tweets of the timeline > >> > > >> and > >> > one > >> > > >> of those last 20 was a retweet - it will be included. If one of the > >> > last 20 > >> > > >> Tweets wasn't a retweet it won't be include
Re: [twitter-dev] Why there isn't 'VERSION' in API URL of OAuth?
Hi Bronco, Authentication ISN'T the API. The API is versioned, but even version 2 of the API might still require our OAuth 1.0a implementation. Think of the REST API as a set of resources. Version 1 of our REST API describes certain resources, responses, and development patterns. How you authenticate for those resources is outside of the concern of the resources themselves. There may be a day in the future where the OAuth end points are versioned, but they would be respective to a different version of OAuth (or other forms of authentication), not necessarily tied to the versioning scheme of the API itself. Taylor On Mon, Oct 4, 2010 at 8:52 AM, Bronco wrote: > Hi,everyone~ > > I've noticed that the API URL of OAuth is something like "http:// > api.twitter.com/oauth/request_token", it didn't contain the "VERSION", > which was different from others. > > Does twitter have any further plan to modify the OAuth API URL of > adding the "VERSION", like "http://api.twitter.com/1/oauth/ > request_token"? > > -- > 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] Why there isn't 'VERSION' in API URL of OAuth?
Hi,everyone~ I've noticed that the API URL of OAuth is something like "http:// api.twitter.com/oauth/request_token", it didn't contain the "VERSION", which was different from others. Does twitter have any further plan to modify the OAuth API URL of adding the "VERSION", like "http://api.twitter.com/1/oauth/ request_token"? -- 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] Re: Install twurl without root access?
The key to getting this to work is making sure that GEM_HOME is set to somewhere you have write access too: Here is it failing: $> gem install twurl ERROR: While executing gem ... (Gem::FilePermissionError) You don't have write permissions into the /usr/lib/ruby/gems/1.8 directory. [1]9286 exit 1 gem install twurl Here is it working: $> export GEM_HOME=$HOME $> gem install twurl Successfully installed oauth-0.4.3 Successfully installed twurl-0.6.2 2 gems installed Installing ri documentation for oauth-0.4.3... Installing ri documentation for twurl-0.6.2... Installing RDoc documentation for oauth-0.4.3... Installing RDoc documentation for twurl-0.6.2... TjL -- 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] Adding twitter message
Thanks. That looks just the job Pam -- 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] ways to authorize users other then oAuth and xAuth?
OAuth will work fine for this. Once a user authorizes your application, you store their access key/secret. Using your client's key/secret and the user's key/secret, you can sign a request to Twitter on behalf of that user. Twitter's OAuth documentation: http://dev.twitter.com/pages/auth sir pelidor wrote: Greeting, I have an app that needs to update its' member's twitter status as well as status for other social-network sites in a scheduled manner. For which I found it very difficult to implement it using oAuth or xAuth, therefore I seek for advise from fellow developers. Detail of the workflow: -End users sign up my service, and will be given to opportunity to store their twitter's access credentials. -End users update status at my service and schedule when it will be deliver -End users are limited to update their status once every 6 days. -To avoid spams, If the end user do not renewal their status after it has been sent by my service, it will not schedule for the next delivery (it does not allow end users to sent the same tweet as the previous one) -In a daily basis, the scheduler of my service will query each members in the system who are qualified to deliver tweet in that given day. Then it will mass update all qualifier's twitter status. Due to how my scheduler works in the background, I believe oAuth or xAuth may not be a proper solution to my problem. Since Twitter API no longer support Basic Auth, what other manners can I utilize so I can send tweet on behave of my members? Thank you. -- Thomas Mango tsma...@gmail.com -- 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] how to login
You should read about Twitter's xAuth support: http://dev.twitter.com/pages/xauth This will let you exchange a username and password for an OAuth access token for that user. qbit systems wrote: Hello There, Currently I develop a web service for iPhone in which i need tweets from twitter, reply that twiiter etc. For this I am using abraham's Twitter OAuth library for this. But when everything is going alright it needs sign in if user not already sign in in twitter but I need a way in which a user can authenticate without browser access because I need to show everything on iPhone so there is no interaction of user and browser. Is this possible? And also i need to pass a parameter with URL so that i cant get Allow and Deny window and i directly jumped on the callback URL. Please reply me ASAP. -- Thomas Mango tsma...@gmail.com -- 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 login
Hello There, Currently I develop a web service for iPhone in which i need tweets from twitter, reply that twiiter etc. For this I am using abraham's Twitter OAuth library for this. But when everything is going alright it needs sign in if user not already sign in in twitter but I need a way in which a user can authenticate without browser access because I need to show everything on iPhone so there is no interaction of user and browser. Is this possible? And also i need to pass a parameter with URL so that i cant get Allow and Deny window and i directly jumped on the callback URL. Please reply me ASAP. -- 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] Adding twitter message
Just incase it helps, here is a work around for older versions of php: http://my.php.net/manual/en/function.json-decode.php#80606 Hope that helps. On 4 October 2010 09:43, Knutsford Software wrote: > I am using PHP Version 5.1.6 and I now get the following > > > Fatal error: Call to undefined function json_decode() in > /var/www/vhosts/pub-rooms.co.uk/httpdocs/updates/company/lib/EpiTwitter.php > on line 41 > > So it looks as though json isn't installed on the server. > > > Thanks I will get the site owner to talk to the Host and see what they say > > > Pam > > > > > > > > > -- > 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] Adding twitter message
Hi Pam,
Like you I've only recently started using the Twitter API, but it
seems pretty straight-forward, and it can be run from a local server.
In my case I'm using the OAuth authentication to send tweets from a
website.
If you are having issues turning on the PHP errors for the entire
server, you could just embed the following in your script:
This will override the default settings for specific script being
tested, so won't affect the rest of the site.
I hope this helps.
Regards,
Ross t
On 4 October 2010 08:42, Knutsford Software
wrote:
> Thanks I will try changing $twitterObj = new EpiTwitter($consumer_key,
> $consumer_secret);
>
> I will also try and turn php errors on. I tried last week but it didn't do
> anything
>
>
>
> Pam
>
> - Original Message - From: "Scott Wilcox"
> To:
> Sent: Sunday, October 03, 2010 9:59 PM
> Subject: Re: [twitter-dev] Adding twitter message
>
>
>> er, off.
>>
>> Also:
>>
>> $twitterObj = new EpiTwitter($consumer_key, $consumer_secret);
>>
>> You are only providing consumer keys, you need to provider user keys too
>> (probably the ones under 'My Access Token').
>>
>> Scott.
>>
>>
>> On 3 Oct 2010, at 08:01, plw wrote:
>>
>>> At the top of my page I have
>>>
>>> include 'lib/EpiCurl.php';
>>> include 'lib/EpiOAuth.php';
>>> include 'lib/EpiTwitter.php';
>>> include 'lib/secret.php';
>>>
>>> further down I have
>>>
>>> $twitter_message = "Offers update - " . date("g:i a:") . "
>>> http://www.pub-rooms.co.uk/ask-rooms.php?bookrooms="; . $intid . " -
>>> " . $ItemName . " " . $CTown;
>>> $twitterObj = new EpiTwitter($consumer_key, $consumer_secret);
>>>
>>> $twitterObj->setToken($oauth_token, $oauth_token_secret);
>>> $update_status = $twitterObj->post_statusesUpdate(array('status' =>
>>> $twitter_message));
>>>
>>>
>>>
>>> My problem that it doesn't send anything to twitter and it doesn't
>>> like
>>>
>>> $tmp=$update_status->response;
>>>
>>> php errors are turned off so I don't know why it doesn't like
>>>
>>> $tmp=$update_status->response;
>>>
>>> What am I doing wrong. At the moment I am totaly stuck. Am I right in
>>> thinking that you can't send a message directly to twiiter anymore
>>> from the admin of a website now that you have to use OAUTH?
>>
>> --
>> 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 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] ways to authorize users other then oAuth and xAuth?
Greeting, I have an app that needs to update its' member's twitter status as well as status for other social-network sites in a scheduled manner. For which I found it very difficult to implement it using oAuth or xAuth, therefore I seek for advise from fellow developers. Detail of the workflow: -End users sign up my service, and will be given to opportunity to store their twitter's access credentials. -End users update status at my service and schedule when it will be deliver -End users are limited to update their status once every 6 days. -To avoid spams, If the end user do not renewal their status after it has been sent by my service, it will not schedule for the next delivery (it does not allow end users to sent the same tweet as the previous one) -In a daily basis, the scheduler of my service will query each members in the system who are qualified to deliver tweet in that given day. Then it will mass update all qualifier's twitter status. Due to how my scheduler works in the background, I believe oAuth or xAuth may not be a proper solution to my problem. Since Twitter API no longer support Basic Auth, what other manners can I utilize so I can send tweet on behave of my members? 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] Re: Streaming API test: Adding new_id field to statuses at 17:00 UTC Sept 29
Hi, John Does Twitter still plan to implement backfill support in streaming API? In an older post from Mark McBride (April, 2010), he said: "To alleviate some of the concerns raised in this thread we thought it would be useful to give more details about how we plan to generate IDs ... ... 4) We will provide a way to backfill from the streaming API. ..." Thanks! On 28 set, 18:34, John Kalucki wrote: > Tomorrow, Wednesday September 29, at 10:00 AM PDT / 17:00 UTC, we will > briefly introduce a field called new_id to statuses delivered over > theStreamingAPI. If this 10 minute test is successful, we will enable > the new_id field continuously on Thursday September 30th at about the > same time. Note that timelines returned by the REST and Search APIs > will not contain this field. This new_id field will allow applications > to preview thenewstatusidgeneration scheme before the primary key > transition scheduled for Tuesday October 12th. > > For more information on our statusidtransition: > > http://groups.google.com/group/twitter-api-announce/browse_thread/thr...http://groups.google.com/group/twitter-api-announce/browse_thread/thr... > > -John Kaluckihttp://twitter.com/jkalucki > Twitter, Inc. -- 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] bidirectional relationship
Ashwin, As far as I know, you can't do this in a single API call. You can, however, call /friends/ids and /followers/ids and use the intersection of the two arrays to find what you're looking for. Relevant API documentation: http://dev.twitter.com/doc/get/friends/ids http://dev.twitter.com/doc/get/followers/ids ashy wrote: Hi All, As we can retrieve friends and followers of the user using the twitter rest api, can we also retrieve users who are both friends and followers of the user at the same time (bidirectional relationship) using the twitter rest api? Any ideas? thanks ashwin -- Thomas Mango tsma...@gmail.com -- 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: add list members
Cool. You could visit the tracker page for this issue, http://code.google.com/p/twitter-api/issues/detail?id=1884 and "star" the issue to help get it fixed sooner. This has got to be one of the easiest Twitter bugs to fix. Ken On Oct 3, 6:08 pm, Damon Clinkscales wrote: > On Sun, Oct 3, 2010 at 9:25 AM, Ken D. wrote: > > Damon, > > > Mea culpa! There's an error in the create_all documentation. I should > > know since I filed the bug... > > > Try:http://api.twitter.com/1/:user/:list/members/create_all.format > > > Afaik,http://api.twitter.com/1/:user/:list/members.xmlis correct for > > adding a single user. > > > Ken > > Hey Ken, > > That was it exactly. The create_all works perfectly now. > > Thanks! > /damon -- 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] bidirectional relationship
Hi All, As we can retrieve friends and followers of the user using the twitter rest api, can we also retrieve users who are both friends and followers of the user at the same time (bidirectional relationship) using the twitter rest api? Any ideas? thanks ashwin -- 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] Adding twitter message
I am using PHP Version 5.1.6 and I now get the following Fatal error: Call to undefined function json_decode() in /var/www/vhosts/pub-rooms.co.uk/httpdocs/updates/company/lib/EpiTwitter.php on line 41 So it looks as though json isn't installed on the server. Thanks I will get the site owner to talk to the Host and see what they say Pam -- 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] Adding twitter message
Thanks I will try changing $twitterObj = new EpiTwitter($consumer_key,
$consumer_secret);
I will also try and turn php errors on. I tried last week but it didn't do
anything
Pam
- Original Message -
From: "Scott Wilcox"
To:
Sent: Sunday, October 03, 2010 9:59 PM
Subject: Re: [twitter-dev] Adding twitter message
er, off.
Also:
$twitterObj = new EpiTwitter($consumer_key, $consumer_secret);
You are only providing consumer keys, you need to provider user keys too
(probably the ones under 'My Access Token').
Scott.
On 3 Oct 2010, at 08:01, plw wrote:
At the top of my page I have
include 'lib/EpiCurl.php';
include 'lib/EpiOAuth.php';
include 'lib/EpiTwitter.php';
include 'lib/secret.php';
further down I have
$twitter_message = "Offers update - " . date("g:i a:") . "
http://www.pub-rooms.co.uk/ask-rooms.php?bookrooms="; . $intid . " -
" . $ItemName . " " . $CTown;
$twitterObj = new EpiTwitter($consumer_key, $consumer_secret);
$twitterObj->setToken($oauth_token, $oauth_token_secret);
$update_status = $twitterObj->post_statusesUpdate(array('status' =>
$twitter_message));
My problem that it doesn't send anything to twitter and it doesn't
like
$tmp=$update_status->response;
php errors are turned off so I don't know why it doesn't like
$tmp=$update_status->response;
What am I doing wrong. At the moment I am totaly stuck. Am I right in
thinking that you can't send a message directly to twiiter anymore
from the admin of a website now that you have to use OAUTH?
--
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] Re: add list members
On Mon, Oct 4, 2010 at 4:40 AM, Ken D. wrote: > Cool. You could visit the tracker page for this issue, > http://code.google.com/p/twitter-api/issues/detail?id=1884 and "star" > the issue to help get it fixed sooner. This has got to be one of the > easiest Twitter bugs to fix. thanks, starred. /damon -- 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
