date:20090421

I updated the library page to reflect your new release. Thanks for giving
back!

Doug Williams
Twitter API Support
http://twitter.com/dougw


On Tue, Apr 21, 2009 at 5:06 PM, Yusuke Yamamoto  wrote:

>
> Hi all,
>
> I'm glad to announce that Twitter4J 2.0.0 is now available.
>
> http://yusuke.homeip.net/blog/2009/04/19/twitter4j_2_0_0_released_now_officially_supports_oauth_authorization_scheme.html
>
> Twitter4J is an open-sourced, mavenized and Google App Engine safe Java
> library for the Twitter API which is released under the BSD license.
>
> This version is already available in the Maven central repository.
> http://repo1.maven.org/maven2/net/homeip/yusuke/twitter4j/
>
> Finally, Twitter4J supports OAuth authorization scheme.
> Projects depending on Twitter4J are encouraged to migrate to the latest
> version to support OAuth.
>
> Best regards,
> --
> Yusuke Yamamoto
> yus...@mac.com
>
>

[twitter-dev] Issues list and transparency

All,
Until today, overwhelming and burgeoning were both adjectives that described
our issue list [1]. Today I am proud to report that it is now consumable,
pleasant, and even helpful. Everything that you find in that list is
currently owned by our team or awaiting verification.

Moving forward this is how we want to continue to use this list. We want
developers to know what we are currently working on so they can plan
accordingly. This list should serve as the definitive guide.

Some of you have already noticed [2] that we have closed or moved many of
the defects or enhancements that used to reside on that list. We have
created a V2 Roadmap document [3] where we will store such longterm goals.
Please note that the introduction indicates we make no promises or
guarantees when or if these items will be delivered. Finally, there were a
few issues that were simply closed to reflect that they were not going to be
fixed in the foreseeable future.

We think that this physical separation of priorities will continue to assist
developers in understanding where our priorities lie. As such we are going
to implement the following policy changes for the issues list:

1) We are going to be more frank with priorities. If something is of value
but not a high priority in the near-term, it will be placed on the Roadmap
[3] document.
2) If a reported issue can be classified as a defect, a high value
enhancement, or as low-hanging fruit it will be assigned accordingly.
3) If a defect is reported without a detailed explanation, it will be
promptly closed. We want to promote good habits where defect reports are
more about helping engineers find problems, and less about discussing proper
bug reporting (as is often the case).

Finally, there is but one change we will be making over the next few weeks
to communicate more effectively with developers. Transparency and
predictability are a common concern so one step at a time, let's fix the
fractured conversation. As always, please forward me any suggestions:
http://twitter.com/twitterapi

1. http://code.google.com/p/twitter-api/issues/list
2. http://twitter.com/h0h0h0/status/1578636888
3. http://apiwiki.twitter.com/V2-Roadmap

Thanks,
Doug Williams
Twitter API Support
http://twitter.com/dougw

[twitter-dev] Twitter4J 2.0.0 released, supports OAuth authorization scheme

2009-04-21 Thread Yusuke Yamamoto



Hi all,

I'm glad to announce that Twitter4J 2.0.0 is now available.
http://yusuke.homeip.net/blog/2009/04/19/twitter4j_2_0_0_released_now_officially_supports_oauth_authorization_scheme.html

Twitter4J is an open-sourced, mavenized and Google App Engine safe  
Java library for the Twitter API which is released under the BSD  
license.


This version is already available in the Maven central repository.
http://repo1.maven.org/maven2/net/homeip/yusuke/twitter4j/

Finally, Twitter4J supports OAuth authorization scheme.
Projects depending on Twitter4J are encouraged to migrate to the  
latest version to support OAuth.


Best regards,
--
Yusuke Yamamoto
yus...@mac.com

[twitter-dev] Replies

2009-04-21 Thread mjx


I am working on a Twitter project in which I need to retrieve the
oldest replies to a specific user from a given status id.

Example:

Status ID: 105
Status ID: 104
Status ID: 103
Status ID: 102
Status ID: 101
Status ID: 100

I want to retrieve the 2 oldest replies since id 100.

If I use the API with the since_id (100) and count (2) parameters it
returns ids 105 and 104. I need 101 and 102.

As I understand the API, in order to achieve this I need to select all
of the replies using the since_id parameter and then using the page
parameter, iterate through the pages until I get to a point where I
have received all of the replies since the specified id as there is no
"number of pages" response.

This is not a problem when the application has a small number of
replies to process. When the application gets to a point where it has
100k replies every 10 minutes, this will be a problem.

Is there a better way to get the oldest replies since a particular id?
It seems that iterating through pages would quickly deplete one's rate
limit (especially when trying to be as friendly to the API as
possible).

Are there any plans to allow for a "get oldest since id" parameter?
Are there any plans for "page count" return result to avoid needless
iterating through results that aren't needed in my application?

Thanks in advance for any help or insight that can be provided.

[twitter-dev] Please add us to your developer list

2009-04-21 Thread twitc.com


We are excited about Twitter and we would like to be listed as a
developer.  We would also like to get in touch with other developers
as we are receiving inquiries from our clients to develop custom
Twittter apps and would like to share the workload.

We develop in Objective C, Perl, PHP, MySQL, Cocoa, Ruby on Rails,
Python, Flex, JS, Java

Our Twitter API beta site:
http://twitc.com
Twitc is a photo and video sharing community.

Main site:
http://lushtech.com (rich media management hosting)

Products:
http://imagefolio.com
http://securedam.com
http://bizsecure.com
http://trustdox.com
http://myslider.com
http://ibulc.com

Thanks!

Rox (@2rkiva)
For more info please contact Kim Stein (@kimwaz)

Regular Email: twit...@lushtech.com


Lush Technologies, Inc.
3888 W Sahara Ave # 81
Las Vegas, NV 89102 USA

1 (877) 927-7387 TOLL FREE
1 (702) 583-7758 TEL
1 (702) 920-7681 FAX

[twitter-dev] Re: twitter4j and unfollowing

2009-04-21 Thread SUZANNE

ACTUALLY YOU CAN JUST REMOVE THEM MANUALLY FROM YOUR ACCOUNT ITS A PAIN BUT IF 
THAT DOESN'T WORK JUST CONTACT TWITTER?AND HAVE THEM IT FOR YOU.. TTYL SUZANNE

?SUZANNE FLEMING O'LEARY

-Original Message-
From: ytbryan 
To: Twitter Development Talk 
Sent: Tues, 21 Apr 2009 6:00 PM
Subject: [twitter-dev] twitter4j and un following

hi all,

i am using twitter4j for the twitter REST service.

when i want to follow somebody , i used twitter.create() and
twitter.follow()..

but i am not sure about unfollowing? do i just do twitter.destroy()?
can somebody advise me? thanks!

[twitter-dev] Re: Send status update with OAuth/PHP/cURL


On Tue, Apr 21, 2009 at 5:59 PM, John Kristian  wrote:
>
> There's a more general-purpose OAuth library at 
> http://code.google.com/p/oauth/
> but I don't know whether it's high quality.

That's the exact library that Abraham used, and extended it to make it
"twitter compatible."

-Chad

[twitter-dev] Re: Send status update with OAuth/PHP/cURL

Check out the docs [1]. There is half a line change to switch from
authorizing to updating.

[1]
https://docs.google.com/View?docID=dcf2dzzs_2339fzbfsf4#Process_4555055271827706_12118

On Tue, Apr 21, 2009 at 16:54, Doug D  wrote:

>
> Thanks Chad!
>
> I've checked out Abraham's OAuth lib, but I don't see how to update a
> twitter status. His example seems to only authenticate and return data
> on the person who's authenticated.
>
> doug
>
>
> On Apr 21, 5:00 pm, Chad Etzel  wrote:
> > Take a look at Abraham Williams' excellent Twitter PHP Oauth lib:
> >
> > http://twitter.abrah.am/
> >
> > -Chad
> >
> > On Tue, Apr 21, 2009 at 4:36 PM, Doug D  wrote:
> >
> > > I've been digging in to the Twitter OAuth stuff and am able to sign
> > > into my site with the Twitter authentication, but I'm wondering if
> > > there is a way to use the OAuth credentails to send a status update
> > > using PHP and cURL. The code below sends an update, but only when a
> > > static username:password is filled in.
> >
> > > My goal it to update (your) Twitter status from my site once you are
> > > authenticated by Twitter. Any thoughts or tutorials? Thanks!
> >
> > > // Set username and password
> > > $username = 'name';
> > > $password = 'password';
> >
> > > // The message you want to send
> > > $message = 'My status update';
> >
> > > // The twitter API address
> > > $url = 'http://twitter.com/statuses/update.xml';
> >
> > > // Alternative JSON version
> > > // $url = 'http://twitter.com/statuses/update.json';
> >
> > > // Set up and execute the curl process
> > > $curl_handle = curl_init();
> >
> > > curl_setopt($curl_handle, CURLOPT_URL, "$url");
> > > curl_setopt($curl_handle, CURLOPT_CONNECTTIMEOUT, 2);
> > > curl_setopt($curl_handle, CURLOPT_RETURNTRANSFER, 1);
> > > curl_setopt($curl_handle, CURLOPT_POST, 1);
> > > curl_setopt($curl_handle, CURLOPT_POSTFIELDS, "status=$message");
> > > curl_setopt($curl_handle, CURLOPT_USERPWD, "$username:$password");
> > > $buffer = curl_exec($curl_handle);
> > > curl_close($curl_handle);
> >
> > > // check for success or failure
> > > if (empty($buffer)) {
> > >echo 'message';
> > > } else {
> > >echo 'success';
> > > }
> >
> >
>



-- 
Abraham Williams | http://the.hackerconundrum.com
Hacker | http://abrah.am | http://twitter.com/abraham
Web608 | Community Evangelist | http://web608.org
This email is: [ ] blogable [x] ask first [ ] private.
Sent from Madison, Wisconsin, United States

[twitter-dev] Re: Send status update with OAuth/PHP/cURL

2009-04-21 Thread John Kristian


There's a more general-purpose OAuth library at http://code.google.com/p/oauth/
but I don't know whether it's high quality.

On Apr 21, 2:00 pm, Chad Etzel  wrote:
> Take a look at Abraham Williams' excellent Twitter PHP Oauth lib:
>
> http://twitter.abrah.am/

[twitter-dev] twitter4j and unfollowing

2009-04-21 Thread ytbryan


hi all,

i am using twitter4j for the twitter REST service.

when i want to follow somebody , i used twitter.create() and
twitter.follow()..

but i am not sure about unfollowing? do i just do twitter.destroy()?
can somebody advise me? thanks!

[twitter-dev] Re: Send status update with OAuth/PHP/cURL

2009-04-21 Thread Doug D


Thanks Chad!

I've checked out Abraham's OAuth lib, but I don't see how to update a
twitter status. His example seems to only authenticate and return data
on the person who's authenticated.

doug


On Apr 21, 5:00 pm, Chad Etzel  wrote:
> Take a look at Abraham Williams' excellent Twitter PHP Oauth lib:
>
> http://twitter.abrah.am/
>
> -Chad
>
> On Tue, Apr 21, 2009 at 4:36 PM, Doug D  wrote:
>
> > I've been digging in to the Twitter OAuth stuff and am able to sign
> > into my site with the Twitter authentication, but I'm wondering if
> > there is a way to use the OAuth credentails to send a status update
> > using PHP and cURL. The code below sends an update, but only when a
> > static username:password is filled in.
>
> > My goal it to update (your) Twitter status from my site once you are
> > authenticated by Twitter. Any thoughts or tutorials? Thanks!
>
> > // Set username and password
> > $username = 'name';
> > $password = 'password';
>
> > // The message you want to send
> > $message = 'My status update';
>
> > // The twitter API address
> > $url = 'http://twitter.com/statuses/update.xml';
>
> > // Alternative JSON version
> > // $url = 'http://twitter.com/statuses/update.json';
>
> > // Set up and execute the curl process
> > $curl_handle = curl_init();
>
> > curl_setopt($curl_handle, CURLOPT_URL, "$url");
> > curl_setopt($curl_handle, CURLOPT_CONNECTTIMEOUT, 2);
> > curl_setopt($curl_handle, CURLOPT_RETURNTRANSFER, 1);
> > curl_setopt($curl_handle, CURLOPT_POST, 1);
> > curl_setopt($curl_handle, CURLOPT_POSTFIELDS, "status=$message");
> > curl_setopt($curl_handle, CURLOPT_USERPWD, "$username:$password");
> > $buffer = curl_exec($curl_handle);
> > curl_close($curl_handle);
>
> > // check for success or failure
> > if (empty($buffer)) {
> >    echo 'message';
> > } else {
> >    echo 'success';
> > }
>
>

[twitter-dev] Re: Site bug regarding newly setup Device Updates

2009-04-21 Thread lgladdy


Thanks guys,

Reported to the correct place!

On Apr 21, 8:52 pm, Matt Sanford  wrote:
> Hi there,
>
>      The best way to report system issues like this is by having the  
> user file an issue athttp://twitter.zendesk.com/requests/portal/new.  
> It's tied to the logged in user so have the individual reports fill it  
> out. You can also contact supp...@twitter.com but email is quite a bit  
> slower.
>
> Thanks;
>    — Matt Sanford / @mzsanford
>
> On Apr 21, 2009, at 11:18 AM, lgladdy wrote:
>
>
>
>
>
> > Hey Guys,
>
> > Posting this on behalf of two friends (@therg and @natcatty) who have
> > tried to setup Device Updates over the weekend/this week.
>
> > First is in the UK on Vodafone (supported) and second is on AT&T in
> > Indiana, US, both have the same issue:
>
> > They've been able to setup the device, and done the text confirmation,
> > but despite having everything enabled, they aren't receiving any
> > updates to their mobile phones, and are unable to set up device
> > updates per follower, as the checkboxes which appear on my profile
> > don't appear on theirs.
>
> > Here is a screenshot of the lack of options from 
> > @therg:http://twitpic.com/3q49f
>
> > This appears like a bug to me!

[twitter-dev] Re: Send status update with OAuth/PHP/cURL


Take a look at Abraham Williams' excellent Twitter PHP Oauth lib:

http://twitter.abrah.am/

-Chad

On Tue, Apr 21, 2009 at 4:36 PM, Doug D  wrote:
>
> I've been digging in to the Twitter OAuth stuff and am able to sign
> into my site with the Twitter authentication, but I'm wondering if
> there is a way to use the OAuth credentails to send a status update
> using PHP and cURL. The code below sends an update, but only when a
> static username:password is filled in.
>
> My goal it to update (your) Twitter status from my site once you are
> authenticated by Twitter. Any thoughts or tutorials? Thanks!
>
> // Set username and password
> $username = 'name';
> $password = 'password';
>
> // The message you want to send
> $message = 'My status update';
>
> // The twitter API address
> $url = 'http://twitter.com/statuses/update.xml';
>
> // Alternative JSON version
> // $url = 'http://twitter.com/statuses/update.json';
>
> // Set up and execute the curl process
> $curl_handle = curl_init();
>
> curl_setopt($curl_handle, CURLOPT_URL, "$url");
> curl_setopt($curl_handle, CURLOPT_CONNECTTIMEOUT, 2);
> curl_setopt($curl_handle, CURLOPT_RETURNTRANSFER, 1);
> curl_setopt($curl_handle, CURLOPT_POST, 1);
> curl_setopt($curl_handle, CURLOPT_POSTFIELDS, "status=$message");
> curl_setopt($curl_handle, CURLOPT_USERPWD, "$username:$password");
> $buffer = curl_exec($curl_handle);
> curl_close($curl_handle);
>
>
> // check for success or failure
> if (empty($buffer)) {
>echo 'message';
> } else {
>echo 'success';
> }
>

[twitter-dev] Send status update with OAuth/PHP/cURL

2009-04-21 Thread Doug D


I've been digging in to the Twitter OAuth stuff and am able to sign
into my site with the Twitter authentication, but I'm wondering if
there is a way to use the OAuth credentails to send a status update
using PHP and cURL. The code below sends an update, but only when a
static username:password is filled in.

My goal it to update (your) Twitter status from my site once you are
authenticated by Twitter. Any thoughts or tutorials? Thanks!

// Set username and password
$username = 'name';
$password = 'password';

// The message you want to send
$message = 'My status update';

// The twitter API address
$url = 'http://twitter.com/statuses/update.xml';

// Alternative JSON version
// $url = 'http://twitter.com/statuses/update.json';

// Set up and execute the curl process
$curl_handle = curl_init();

curl_setopt($curl_handle, CURLOPT_URL, "$url");
curl_setopt($curl_handle, CURLOPT_CONNECTTIMEOUT, 2);
curl_setopt($curl_handle, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($curl_handle, CURLOPT_POST, 1);
curl_setopt($curl_handle, CURLOPT_POSTFIELDS, "status=$message");
curl_setopt($curl_handle, CURLOPT_USERPWD, "$username:$password");
$buffer = curl_exec($curl_handle);
curl_close($curl_handle);


// check for success or failure
if (empty($buffer)) {
echo 'message';
} else {
echo 'success';
}

[twitter-dev] Re: Only 1 of Several Twits are Sent as Device Updates

Are the updates exactly the same?

Doug Williams
Twitter API Support
http://twitter.com/dougw


On Tue, Apr 21, 2009 at 10:17 AM, Gilbert wrote:

>
> Hi,
>
> I notice that if I post updates in succession (within a very short
> time), only the first one gets sent to my followers' device.
>
> Is this to avoid  spam?
>
> What's the exact policy on this?
>

[twitter-dev] Re: Site bug regarding newly setup Device Updates


Hi there,

The best way to report system issues like this is by having the  
user file an issue at http://twitter.zendesk.com/requests/portal/new.  
It's tied to the logged in user so have the individual reports fill it  
out. You can also contact supp...@twitter.com but email is quite a bit  
slower.


Thanks;
  — Matt Sanford / @mzsanford

On Apr 21, 2009, at 11:18 AM, lgladdy wrote:



Hey Guys,

Posting this on behalf of two friends (@therg and @natcatty) who have
tried to setup Device Updates over the weekend/this week.

First is in the UK on Vodafone (supported) and second is on AT&T in
Indiana, US, both have the same issue:

They've been able to setup the device, and done the text confirmation,
but despite having everything enabled, they aren't receiving any
updates to their mobile phones, and are unable to set up device
updates per follower, as the checkboxes which appear on my profile
don't appear on theirs.

Here is a screenshot of the lack of options from @therg: 
http://twitpic.com/3q49f

This appears like a bug to me!

[twitter-dev] Re: Site bug regarding newly setup Device Updates

You will probably have better luck on http://help.twitter.com/portal since
this is list is full of API developers.

On Tue, Apr 21, 2009 at 13:18, lgladdy  wrote:

>
> Hey Guys,
>
> Posting this on behalf of two friends (@therg and @natcatty) who have
> tried to setup Device Updates over the weekend/this week.
>
> First is in the UK on Vodafone (supported) and second is on AT&T in
> Indiana, US, both have the same issue:
>
> They've been able to setup the device, and done the text confirmation,
> but despite having everything enabled, they aren't receiving any
> updates to their mobile phones, and are unable to set up device
> updates per follower, as the checkboxes which appear on my profile
> don't appear on theirs.
>
> Here is a screenshot of the lack of options from @therg:
> http://twitpic.com/3q49f
>
> This appears like a bug to me!
>



-- 
Abraham Williams | http://the.hackerconundrum.com
Hacker | http://abrah.am | http://twitter.com/abraham
Web608 | Community Evangelist | http://web608.org
This email is: [ ] blogable [x] ask first [ ] private.
Sent from Madison, Wisconsin, United States

[twitter-dev] Re: Search API returns HTTP 406 Not Acceptable

2009-04-21 Thread Ho John Lee


Never mind. I figured out the problems was I switched queries to
".xml" instead of ".json", and XML isn't one of the choices for the
search API.

On Apr 21, 12:43 pm, hjl  wrote:
> I'm doing some testing this morning with the search API, which was
> working for a while but now is returning HTTP 406 Not Acceptable. Is
> this a symptom of the search API rate limiting? I ran a few queries
> with curl by hand, then ran a loop to see how far back the results
> pages go.
>
> The search API docs says rate limited requests should see 503 Service
> Unavailable, was wondering if it changed.
>
> I'll try it again in an hour or so and see if the search API starts
> responding again. But would still like to know if the response code
> for search rate limiting has changed.

[twitter-dev] Search API returns HTTP 406 Not Acceptable

2009-04-21 Thread hjl


I'm doing some testing this morning with the search API, which was
working for a while but now is returning HTTP 406 Not Acceptable. Is
this a symptom of the search API rate limiting? I ran a few queries
with curl by hand, then ran a loop to see how far back the results
pages go.

The search API docs says rate limited requests should see 503 Service
Unavailable, was wondering if it changed.

I'll try it again in an hour or so and see if the search API starts
responding again. But would still like to know if the response code
for search rate limiting has changed.

[twitter-dev] Site bug regarding newly setup Device Updates

2009-04-21 Thread lgladdy


Hey Guys,

Posting this on behalf of two friends (@therg and @natcatty) who have
tried to setup Device Updates over the weekend/this week.

First is in the UK on Vodafone (supported) and second is on AT&T in
Indiana, US, both have the same issue:

They've been able to setup the device, and done the text confirmation,
but despite having everything enabled, they aren't receiving any
updates to their mobile phones, and are unable to set up device
updates per follower, as the checkboxes which appear on my profile
don't appear on theirs.

Here is a screenshot of the lack of options from @therg: 
http://twitpic.com/3q49f

This appears like a bug to me!

[twitter-dev] sender's avatar in email headers

2009-04-21 Thread dang


Is it possible to have the sender's avatar url appear in the email
headers? Example:

X-Twittersenderavatar: 
http://s3.amazonaws.com/twitter_production/profile_images/59648642/avatar_normal.png


Thanks

[twitter-dev] Re: rpp and page

Give example of what you are calling and what you expect to get back.

On Tue, Apr 21, 2009 at 12:19, Joseph  wrote:

>
> Thank you, but like I said in my earlier post, I am following these
> directions in my API calls, but it's not returning what I expect to
> see when setting rpp and page to the proper values.
>
> On Apr 21, 10:04 am, Abraham Williams <4bra...@gmail.com> wrote:
> > Here are the docs:
> http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search
> >
> > On Tue, Apr 21, 2009 at 10:41, Joseph  wrote:
> >
> > > This is for a search: there are two parameters that do not seem to be
> > > working (or I can't figure out where the correct documentation is):
> > > rpp (for number of entries per page returned, and page (number of
> > > pages returned per search). And it seems as if no matter what I enter
> > > for "since" and "to" (since a date, to a date), these values seem to
> > > be ignored.
> >
> > --
> > Abraham Williams |http://the.hackerconundrum.com
> > Hacker |http://abrah.am|http://twitter.com/abraham
> > Web608 | Community Evangelist |http://web608.org
> > This email is: [ ] blogable [x] ask first [ ] private.
> > Sent from Madison, Wisconsin, United States
>



-- 
Abraham Williams | http://the.hackerconundrum.com
Hacker | http://abrah.am | http://twitter.com/abraham
Web608 | Community Evangelist | http://web608.org
This email is: [ ] blogable [x] ask first [ ] private.
Sent from Madison, Wisconsin, United States

[twitter-dev] Re: rpp and page

2009-04-21 Thread Joseph


Thank you, but like I said in my earlier post, I am following these
directions in my API calls, but it's not returning what I expect to
see when setting rpp and page to the proper values.

On Apr 21, 10:04 am, Abraham Williams <4bra...@gmail.com> wrote:
> Here are the 
> docs:http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search
>
> On Tue, Apr 21, 2009 at 10:41, Joseph  wrote:
>
> > This is for a search: there are two parameters that do not seem to be
> > working (or I can't figure out where the correct documentation is):
> > rpp (for number of entries per page returned, and page (number of
> > pages returned per search). And it seems as if no matter what I enter
> > for "since" and "to" (since a date, to a date), these values seem to
> > be ignored.
>
> --
> Abraham Williams |http://the.hackerconundrum.com
> Hacker |http://abrah.am|http://twitter.com/abraham
> Web608 | Community Evangelist |http://web608.org
> This email is: [ ] blogable [x] ask first [ ] private.
> Sent from Madison, Wisconsin, United States

[twitter-dev] Re: rpp and page

2009-04-21 Thread Joseph

Yes, I understand that the page # is the page # and that I have access
to about 150 of those, and I am processing the json file properly. I
will double check the data types I'm using. Looking through a json
response, the twitter api thinks I am entering negative dates (for
since) (not the case).

On Apr 21, 10:34 am, Nick Arnett  wrote:
> On Tue, Apr 21, 2009 at 8:41 AM, Joseph  wrote:
>
> >  page (number of
> > pages returned per search).
>
> I'm not sure if you meant what you wrote here, but page is the page number
> of the search results for one query, not the number of pages returned per
> search.  In other words, you'd iterate through the available pages to get
> all of the available results.
>
> However, the search API also returns a URL for the next result page
> ("next_page"), so you don't have to make your own iterator unless you wish
> to skip some results pages for some reason.
>
> Nick

[twitter-dev] Only 1 of Several Twits are Sent as Device Updates

2009-04-21 Thread Gilbert


Hi,

I notice that if I post updates in succession (within a very short
time), only the first one gets sent to my followers' device.

Is this to avoid  spam?

What's the exact policy on this?

[twitter-dev] Tipjoy allows API access via OAuth

2009-04-21 Thread Ivan


Hi,

We just updated the Tipjoy Twitter Payments API to let 3rd parties use
OAuth for authorization. To our knowledge, this is the first twitter
app mashup based on OAuth.

Read more about it:
http://tipjoy.com/api/#authentication
http://tipjoys2cents.blogspot.com/2009/04/twitter-applications-can-now-use-tipjoy.html

And try it out!

We did it by asking for a pre-signed Authentication header to the
verify_credentials Twitter REST API endpoint. We ping that endpoint,
and if it works, the call is authenticated.

Again, try it out and let me know what you think. If you haven't
heard, we're holding an API contest too :-D
http://tipjoy.com/apicontest/

Ivan
http://tipjoy.com

[twitter-dev] Re: Combining search operators: possible? Limitations!

Hi there,

For use in the API I don't really suggest using the separate URL
parameters like the advanced search pages does. The best bet is to put
it all in the q= parameter using the operator syntax. Check out http://search.twitter.com/operators
for some examples, and I have included some below:

On Apr 21, 2009, at 10:23 AM, Jeffrey Greenberg wrote:

I'm not clear on what is possible with search. I've played with the
advanced search page, and with the api directly, but I could still use
some explanation...

There are the usual "and" "or" "not" operators but it does not appear
to me that these can be combined in anything but the most simple ways.
Is that right? There seems to be a lack of a 'grouping' operator to
combine these expressions. Instead, the api seems to list these
operators together so that they can all be present at once... If so,
then how are the operators taken together when they are all supplied?

There is no grouping but it has been requested (http://code.google.com/p/twitter-api/issues/detail?id=321
). You can still use OR and - (not) with other queries. Things like
this work:

[hot OR sunny -bono] (square brackets added to delimit the query, OR
must be capital).

That would fine entries with "hot" or "sunny" but without "bono".

How are "quoted strings" handled with these? I'm not clear

[foo bar] finds and tweet that contains both "foo" and "bar" anywhere
in the tweet.
["foo bar"] finds only those tweets where "foo" and "bar" are next to
each other (only a space or punctuation in between).

Then there is "phrase" which implies a word ordering, but how can a
phrase be combined with the above operators? And does a "quoted
string" differ from a phrase? And what if a quoted string is suppled
in the "word" field, and something else in the "phrase" field

Quoted string and phrase are really just two words for the same thing.
Sorry for the confusion.

The operators such as "tude" and "tags" are also confusing, since one
can supply these character sequences in the other fields. How are
these combined with the above operators?

The tude is the ":)" or ":(" operator. It's silly really. Things like
[dumped :(] will find tweets that contain both "dumped" and some
variation on the sad face.

Tags are just like other query terms but begin with #, like [#earthday]

The date operators seem clear enough.

Then there is the total count of what is matched which is mostly
missing with the exception that it unreliably appears at the end of a
series of pages.

We do not provide a reslt count in the API for performance reasons.
You can find out more about that my searching the list archives.

I'd appreciate your clarifying wisdom,
signed 'Confused Seeker in SF'

[twitter-dev] Re: rpp and page

2009-04-21 Thread Nick Arnett

On Tue, Apr 21, 2009 at 8:41 AM, Joseph  wrote:

>
>  page (number of
> pages returned per search).

I'm not sure if you meant what you wrote here, but page is the page number
of the search results for one query, not the number of pages returned per
search.  In other words, you'd iterate through the available pages to get
all of the available results.

However, the search API also returns a URL for the next result page
("next_page"), so you don't have to make your own iterator unless you wish
to skip some results pages for some reason.

Nick

[twitter-dev] Re: Search friends timeline

Integrating search into your friends_timeline is something we want to do in
the future. With the separation of the Search and REST APIs, it isn't a
trivial feature. For now, you have to parse out results from timelines
client side.

Doug Williams
Twitter API Support
http://twitter.com/dougw


On Tue, Apr 21, 2009 at 9:44 AM, mikejablonski  wrote:

>
> That was my plan for now. It just makes it harder to get the next X
> friend status messages that have "XYZ" in them. I'm surprised this
> isn't a more requested feature. Thanks!
>
> On Apr 21, 8:28 am, Chad Etzel  wrote:
> > You can't.
> >
> > Just get the friends timeline and filter it client-side.  You'll have
> > more granular control over the filtering that way anyway.
> >
> > -Chad
> >
> > On Tue, Apr 21, 2009 at 11:16 AM, mikejablonski 
> wrote:
> >
> > > I've looked at the docs and searched the group, but I can't find any
> > > way to search your friends timeline. How can I get a filtered set of
> > > friend status messages based on a query? Is this possible? I know I
> > > could use the search API and throw away all my non-friends, but that
> > > won't work well for a lot of reasons. Thanks!
>

[twitter-dev] Combining search operators: possible? Limitations!

2009-04-21 Thread Jeffrey Greenberg


I'm not clear on what is possible with search. I've played with the
advanced search page, and with the api directly, but I could still use
some explanation...

There are the usual "and" "or" "not" operators but it does not appear
to me that these can be combined in anything but the most simple ways.
Is that right? There seems to be a lack of a 'grouping' operator to
combine these expressions.   Instead, the api seems to list these
operators together so that they can all be present at once... If so,
then how are the operators taken together when they are all supplied?

How are "quoted strings" handled with these? I'm not clear

Then there is "phrase" which implies a word ordering, but how can a
phrase be combined with the above operators?  And does a "quoted
string" differ from a phrase?  And what if a quoted string is suppled
in the "word" field, and something else in the "phrase" field

The operators such as "tude" and "tags" are also confusing, since one
can supply these character sequences in the other fields.  How are
these combined with the above operators?

The date operators seem clear enough.

Then there is the total count of what is matched which is mostly
missing with the exception that it unreliably appears at the end of a
series of pages.

I'd appreciate your clarifying wisdom,
signed 'Confused Seeker in SF'

[twitter-dev] Re: rpp and page

Here are the docs:
http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search

On Tue, Apr 21, 2009 at 10:41, Joseph  wrote:

>
> This is for a search: there are two parameters that do not seem to be
> working (or I can't figure out where the correct documentation is):
> rpp (for number of entries per page returned, and page (number of
> pages returned per search). And it seems as if no matter what I enter
> for "since" and "to" (since a date, to a date), these values seem to
> be ignored.
>



-- 
Abraham Williams | http://the.hackerconundrum.com
Hacker | http://abrah.am | http://twitter.com/abraham
Web608 | Community Evangelist | http://web608.org
This email is: [ ] blogable [x] ask first [ ] private.
Sent from Madison, Wisconsin, United States

[twitter-dev] Re: Search friends timeline

2009-04-21 Thread mikejablonski


That was my plan for now. It just makes it harder to get the next X
friend status messages that have "XYZ" in them. I'm surprised this
isn't a more requested feature. Thanks!

On Apr 21, 8:28 am, Chad Etzel  wrote:
> You can't.
>
> Just get the friends timeline and filter it client-side.  You'll have
> more granular control over the filtering that way anyway.
>
> -Chad
>
> On Tue, Apr 21, 2009 at 11:16 AM, mikejablonski  wrote:
>
> > I've looked at the docs and searched the group, but I can't find any
> > way to search your friends timeline. How can I get a filtered set of
> > friend status messages based on a query? Is this possible? I know I
> > could use the search API and throw away all my non-friends, but that
> > won't work well for a lot of reasons. Thanks!

[twitter-dev] rpp and page

2009-04-21 Thread Joseph


This is for a search: there are two parameters that do not seem to be
working (or I can't figure out where the correct documentation is):
rpp (for number of entries per page returned, and page (number of
pages returned per search). And it seems as if no matter what I enter
for "since" and "to" (since a date, to a date), these values seem to
be ignored.

[twitter-dev] Re: twiiter functionality help


On Tue, Apr 21, 2009 at 12:08 PM, Dossy Shiobara  wrote:
>
> Sounds like yet another rent-a-coder trying to create a Twitter Karma
> knock-off.
>
> Imitation is the sincerest form of flattery, right?  :-)
>

"Competition is the greatest driver of innovation," is more like it.

[twitter-dev] Re: twiiter functionality help

2009-04-21 Thread Dossy Shiobara



Sounds like yet another rent-a-coder trying to create a Twitter Karma 
knock-off.


Imitation is the sincerest form of flattery, right?  :-)


On 4/21/09 1:58 AM, mraj...@gmail.com wrote:

i am developing a twitter application in php. My application unfollows
the tweets, who are not following back.
and i want functionality which allow the user to use the site once
every 24 hours. Is there any way of doing this function ?? please help
me asap on this functionaly.



--
Dossy Shiobara  | do...@panoptic.com | http://dossy.org/
Panoptic Computer Network   | http://panoptic.com/
  "He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)

[twitter-dev] Re: OAuth and Perl



Hi Jesse,

The best debugging information is:

1. The error message from your 401.
   » Example: "Failed to validate oauth signature or token"

2. The signature base string. In other words, the string you used to  
create the signature.

  » Example: See [1] for an example.

3. What oauth application is this for?
  » Example: http://twitter.com/oauth_clients/details/104

Thanks;
  — Matt Sanford


[1] Example signature base string:

POST&http%3A%2F
%2F192.168.1.123%3A3000%2Fstatuses%2Fupdate.json&
oauth_consumer_key%3Dwritekey%26oauth_nonce 
%3DOzn8q5kDW7rPkFME1P2cN33nlr9i9ESNJmZEmGLUVU

%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
%3D1239638732%26oauth_token%3D3- 
xzFwdowMs3Rqxv8fKW4zxItwIlsoSN6Vqrnd736r8%26oauth_version%3D1.0
%26status%3Dchecking%2520out%2520matts%2520app 
%2520%2540%25201239638732%2520test%253A%2525C3%2525A6


On Apr 20, 2009, at 07:59 PM, Jesse Stay wrote:

I'm getting 401 Unauthorized when trying to use Net::OAuth in Perl  
to access Twitter - it's happening in trying to swap the request  
token for the access token (in the second block below, from the $ua- 
>post()).  I was just wondering what the best method for debugging  
this would be.  Here's my code (it's in Catalyst, so the $c's are  
from the Framework environment):


sub authenticate_twitter : Local {
my ($self, $c) = @_;

unless ($c->user_session->{'request_token'} && $c->user_session- 
>{'request_token_secret'}) {

my $request = Net::OAuth->request("request token")->new(
consumer_key => $c->config->{'twitter_consumer_key'},
consumer_secret => $c->config- 
>{'twitter_consumer_secret'},

request_url => $c->config->{'twitter_request_url'},
request_method => 'GET',
signature_method => 'HMAC-SHA1',
timestamp => time,
nonce => join('', rand_chars(size=>16,  
set=>'alphanumeric')),

);
$request->sign();

$c->log->debug("URL: ".$request->to_url);

my $ua = LWP::UserAgent->new;
my $res = $ua->get($request->to_url); # post request to  
Twitter


if ($res->is_success) {
my $response = Net::OAuth->response('request token')- 
>from_post_body($res->content);

$c->user_session->{'request_token'} = $response->token;
$c->user_session->{'request_token_secret'} = $response- 
>token_secret;


if (defined $c->user_session->{'request_token'}) {
my $auth_url = $c->config- 
>{'twitter_authorize_token_url'}."?oauth_token=" . $c->user_session- 
>{'request_token'} . "&redirect_url=".uri_escape($c->req->param("redi

rect_url"));;
$c->res->redirect($auth_url);
$c->detach;
return;
}
}
else {
$c->log->fatal("Something went wrong.");
}
}
else {
$c->log->debug("request_token: ".$c->user_session- 
>{'request_token'});
$c->log->debug("request_token_secret: ".$c->user_session- 
>{'request_token_secret'});

my $request = Net::OAuth->request("access token")->new(
consumer_key=> $c->config- 
>{'twitter_consumer_key'},
consumer_secret => $c->config- 
>{'twitter_consumer_secret'},
token   => $c->user_session- 
>{'request_token'},
token_secret=> $c->user_session- 
>{'request_token_secret'},
request_url => $c->config- 
>{'twitter_access_token_url'},

request_method  => 'POST',
signature_method=> 'HMAC-SHA1',
timestamp   => time,
nonce   => join('', rand_chars(size=>16,  
set=>'alphanumeric')),

);
$request->sign();

$c->log->debug("URL: ".$request->to_url);

my $ua = LWP::UserAgent->new;
my $res = $ua->post($request->to_url); # post request to  
Twitter


if ($res->is_success) {
my $response = Net::OAuth->response('access token')- 
>from_post_body($res->content);

$c->user_session->{'access_token'} = $response->token;
$c->user_session->{'access_token_secret'} = $response- 
>token_secret;


$c->res->redirect(uri_unescape($c->req- 
>param('redirect_url')));

}
else {
$c->log->fatal("Could not get an Access Token: " . $res- 
>status_line . " " . $res->content);

}

}

}

-...@jesse

[twitter-dev] Re: Reading the public time-line

The data mining feed is your best bet:
http://apiwiki.twitter.com/FAQ#WhatstheDataMiningFeedandcanInbsphaveaccesstoit

On Tue, Apr 21, 2009 at 09:35, Tim  wrote:

>
> Hi Guys
>
> Sorry I'm sure that this question has been asked before - but I can't
> seem to find it :(
> How can my app read the entire (or as entire as possible) public time-
> line
>
> I'm aware of: http://twitter.com/statuses/public_timeline.xml (etc..)
> but the API specs state that this returns just 20 results and that it
> is cached every 60 seconds
>
> How is it possible to read all the "other" tweets?
>
> Yours
> Tim
>



-- 
Abraham Williams | http://the.hackerconundrum.com
Hacker | http://abrah.am | http://twitter.com/abraham
Web608 | Community Evangelist | http://web608.org
This email is: [ ] blogable [x] ask first [ ] private.

[twitter-dev] Re: Read and store Twitter responses

2009-04-21 Thread Nick Arnett

On Mon, Apr 20, 2009 at 5:59 PM, Joseph  wrote:

>
> This may not be the best thing to do in the case of statuses.
> Optimization implies that you have two tables (minimum), one for the
> user info, and one for the tweets. Doing a batch update, means that
> you're skipping the step of checking to see if the user is already in
> the database, so for every tweet, you will add the same user again.
> That will you will slow you down much more than the batch advantage,
> and will create confusion (unless you store all in one table, and
> that's even more burdensome).

There are a couple of ways to deal with this. Given sufficient memory, keep
a hash of userIDs in memory and only insert the new ones.  If memory
consumption is a problem, assuming that the userID as the primary key in the
user table,  do an INSERT IGNORE for all of the users.  With userID indexed,
that will be quite fast.

It won't be that simple if you have foreign key constraints, but I can't
imagine referential integrity is critical for this sort of application.

My system is far more constrained by things other than the insert speeds.

Nick

[twitter-dev] Re: Search friends timeline


You can't.

Just get the friends timeline and filter it client-side.  You'll have
more granular control over the filtering that way anyway.

-Chad

On Tue, Apr 21, 2009 at 11:16 AM, mikejablonski  wrote:
>
> I've looked at the docs and searched the group, but I can't find any
> way to search your friends timeline. How can I get a filtered set of
> friend status messages based on a query? Is this possible? I know I
> could use the search API and throw away all my non-friends, but that
> won't work well for a lot of reasons. Thanks!
>

[twitter-dev] Search friends timeline

2009-04-21 Thread mikejablonski


I've looked at the docs and searched the group, but I can't find any
way to search your friends timeline. How can I get a filtered set of
friend status messages based on a query? Is this possible? I know I
could use the search API and throw away all my non-friends, but that
won't work well for a lot of reasons. Thanks!

[twitter-dev] Reading the public time-line

2009-04-21 Thread Tim


Hi Guys

Sorry I'm sure that this question has been asked before - but I can't
seem to find it :(
How can my app read the entire (or as entire as possible) public time-
line

I'm aware of: http://twitter.com/statuses/public_timeline.xml (etc..)
but the API specs state that this returns just 20 results and that it
is cached every 60 seconds

How is it possible to read all the "other" tweets?

Yours
Tim

[twitter-dev] Re: API Changes for April 1, 2009

2009-04-21 Thread Marco Kaiser

Thanks, Matt!

I've added the information from my mail as a comment to that issue.

Marco

2009/4/21 Matt Sanford 

> Hi there,
>
>   This sounds like it is related to Google Code issue 474 [1]. Please visit
> Google Code and click on the little star next to the title to get updates
> when that issue is updated.
> Thanks;
>   — Matt Sanford
>
> [1] - http://code.google.com/p/twitter-api/issues/detail?id=474
>
> On Apr 21, 2009, at 04:22 AM, Marco Kaiser wrote:
>
> Doug? Anyone?
>
> Thanks,
> Marco
>
> 2009/4/9 Marco Kaiser 
>
>> I recognize an odd behavior for the "following" property of embedded user
>> object in the friends timeline (XML format). As I understand from the API
>> docs, "following" should indicate whether the authenticating user is
>> following the returned user.
>>
>> Obviously, all tweets returned on the /statuses/friends_timeline.xml
>> endpoint should come from users I am following (and I manually verified that
>> for some samples), but still some of them have false
>> set. It seems to be at least consistant in a way that the same user always
>> has the same value set for following in a result set - it just is either
>> always wrong or always right.
>>
>> Is that a known issue?
>>
>> Thanks,
>> Marco
>>
>> 2009/4/5 Martin Dufort 
>>
>>
>>> I'm seeing inconsitent user attributes within the *same* request for
>>> the *same* user. One result has full attributes disclosure, and the
>>> other one has not.
>>>
>>> I've updated Issue 409 with my results.
>>> Martin
>>>
>>> On Apr 2, 8:36 pm, Doug Williams  wrote:
>>> > Jeffery,
>>> > This is valid criticism. This bug came as a surprise to us as well. We
>>> > otherwise would have given developers fair warning. Unfortunately there
>>> is
>>> > no easy fix, and like a bad heart-break, time may be the only answer.
>>> >
>>> > In short, the problem is with the user data cache. To get the extended
>>> > information into that cache, the user object must either expire or be
>>> > invalidated through some user initiated update. The expiry on the cache
>>> is
>>> > rather long and you will find that inactive accounts will have
>>> abbreviated
>>> > data for up to 2 weeks.
>>> >
>>> > This is obviously sub-optimal, as Matt would say.
>>> >
>>> > Doug Williams
>>> > Twitter API Supporthttp://twitter.com/dougw
>>> >
>>> > On Thu, Apr 2, 2009 at 12:27 PM, Jeffrey Greenberg <
>>> >
>>> >
>>> >
>>> > jeffreygreenb...@gmail.com> wrote:
>>> >
>>> > > Doug,
>>> > > Grumble: just to say it, this wasn't handled well at all.  The fact
>>> > > that this field disappears whether due to caching or through a coding
>>> > > error has the same result of completely breaking my app.
>>> >
>>> > > How long will it take for this issue to clear up? Days? How many
>>> > > exactly?  and after X days will further requests be populated
>>> > > correctly?
>>> >
>>> > > thx,
>>> > > jeffrey
>>> > >http://www.tweettronics.com
>>>
>>
>>
>
>

[twitter-dev] Re: API Changes for April 1, 2009

Hi there,

  This sounds like it is related to Google Code issue 474 [1]. Please  
visit Google Code and click on the little star next to the title to  
get updates when that issue is updated.

Thanks;
  — Matt Sanford

[1] - http://code.google.com/p/twitter-api/issues/detail?id=474

On Apr 21, 2009, at 04:22 AM, Marco Kaiser wrote:

Doug? Anyone?

Thanks,
Marco

2009/4/9 Marco Kaiser 
I recognize an odd behavior for the "following" property of embedded  
user object in the friends timeline (XML format). As I understand  
from the API docs, "following" should indicate whether the  
authenticating user is following the returned user.

Obviously, all tweets returned on the /statuses/friends_timeline.xml  
endpoint should come from users I am following (and I manually  
verified that for some samples), but still some of them have  
false set. It seems to be at least consistant  
in a way that the same user always has the same value set for  
following in a result set - it just is either always wrong or always  
right.

Is that a known issue?

Thanks,
Marco

2009/4/5 Martin Dufort 

I'm seeing inconsitent user attributes within the *same* request for
the *same* user. One result has full attributes disclosure, and the
other one has not.

I've updated Issue 409 with my results.
Martin

On Apr 2, 8:36 pm, Doug Williams  wrote:
> Jeffery,
> This is valid criticism. This bug came as a surprise to us as  
well. We
> otherwise would have given developers fair warning. Unfortunately  
there is
> no easy fix, and like a bad heart-break, time may be the only  
answer.

>
> In short, the problem is with the user data cache. To get the  
extended
> information into that cache, the user object must either expire or  
be
> invalidated through some user initiated update. The expiry on the  
cache is
> rather long and you will find that inactive accounts will have  
abbreviated

> data for up to 2 weeks.
>
> This is obviously sub-optimal, as Matt would say.
>
> Doug Williams
> Twitter API Supporthttp://twitter.com/dougw
>
> On Thu, Apr 2, 2009 at 12:27 PM, Jeffrey Greenberg <
>
>
>
> jeffreygreenb...@gmail.com> wrote:
>
> > Doug,
> > Grumble: just to say it, this wasn't handled well at all.  The  
fact
> > that this field disappears whether due to caching or through a  
coding

> > error has the same result of completely breaking my app.
>
> > How long will it take for this issue to clear up? Days? How many
> > exactly?  and after X days will further requests be populated
> > correctly?
>
> > thx,
> > jeffrey
> >http://www.tweettronics.com

[twitter-dev] Re: Inconsistent results from /statuses/friends.json