Re: Date followed?

2008-10-30 Thread Ryan Bigg

I am also interested in this feature.


Re: Date followed?

2008-10-30 Thread Ed Finkler
Currently there's nothing available via the API – you'd probably need
to cache your whole followers list and then compare the last version
to the newest. You probably should file an issue in the tracker if one
does not already exist for this feature request:

http://code.google.com/p/twitter-api/issues/list

--
Ed Finkler
http://funkatron.com
AIM: funka7ron
ICQ: 3922133
Skype: funka7ron


On Thu, Oct 30, 2008 at 9:22 AM, Ryan Bigg <[EMAIL PROTECTED]> wrote:
>
> I am also interested in this feature.
>


Facebook

2008-10-30 Thread Adam

I have facebook and I want to put that in my status,   I have two
twitter putting the status in the status,  OK,  The third one I get
nothing in my status.  WHY?

Adam


Re: Facebook

2008-10-30 Thread Ed Finkler

You probably want to direct this to the customer support system,
rather than the developer list.

http://getsatisfaction.com/twitter

--
Ed Finkler
http://funkatron.com
AIM: funka7ron
ICQ: 3922133
Skype: funka7ron


On Thu, Oct 30, 2008 at 10:52 AM, Adam <[EMAIL PROTECTED]> wrote:
>
> I have facebook and I want to put that in my status,   I have two
> twitter putting the status in the status,  OK,  The third one I get
> nothing in my status.  WHY?
>
> Adam
>


Re: Facebook

2008-10-30 Thread Alex Payne

Or http://help.twitter.com or [EMAIL PROTECTED]

On Thu, Oct 30, 2008 at 10:06 AM, Ed Finkler <[EMAIL PROTECTED]> wrote:
>
> You probably want to direct this to the customer support system,
> rather than the developer list.
>
> http://getsatisfaction.com/twitter
>
> --
> Ed Finkler
> http://funkatron.com
> AIM: funka7ron
> ICQ: 3922133
> Skype: funka7ron
>
>
> On Thu, Oct 30, 2008 at 10:52 AM, Adam <[EMAIL PROTECTED]> wrote:
>>
>> I have facebook and I want to put that in my status,   I have two
>> twitter putting the status in the status,  OK,  The third one I get
>> nothing in my status.  WHY?
>>
>> Adam
>>
>



-- 
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x


Re: Rate Limit For Mass POSTs

2008-10-30 Thread Alex Payne

The rate limit on DMs isn't something we share publicly, as it's
subject to change.  Not trying to be secretive, we just don't want
people coding around one particular value only to have it be raised or
lowered as is necessary to combat spam and abusive usage of our
service.

We don't lift the DM rate limit based on IP, but rather on username.
So if we whitelist your account, that account will be able to send
unlimited DMs.

On Wed, Oct 29, 2008 at 7:06 PM, Tony Stubblebine
<[EMAIL PROTECTED]> wrote:
>
> Thanks Alex,
>
> What's the limit on DMs per day and is that something that can be
> whitelisted by IP?
>
> I guess whitelisting by IP wouldn't make much sense in a general case.
> The project I'm working on is going to live on the web and live both
> inside and outside of CrowdVine. For the inside CrowdVine part, it's
> for paying conferences doing things like sending updates when a
> session changes rooms. I can vouch for them. But for general usage, I
> wouldn't want to open up a loophole.
>
> Thx,
> Tony
>
> On Oct 29, 5:17 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote:
>> For one, you'll need to get your account whitelisted.  POST requests
>> aren't rate limited as a rule, but there are some rules around the
>> number updates and direct messages one can send per day that apply
>> whether you're using the API or the web site.  Getting whitelisted
>> lifts those limits.
>>
>> Beyond that, feel free to POST either serially or in parallel.  Five
>> at a time sounds perfectly reasonable.
>>
>> On Wed, Oct 29, 2008 at 4:28 PM, Tony Stubblebine
>>
>>
>>
>> <[EMAIL PROTECTED]> wrote:
>>
>> > I'm building an app for managing large twitter accounts and have two
>> > desires. One, to be able to mass-follow a selection of people who are
>> > following me. Two, to send direct messages to all followers or to
>> > slices of my followers. These may bring up etiquette/user-expectation/
>> > spam issues, but first I want to get a very specific RATE limiting
>> > question answered.
>>
>> > The documentation says that POST requests are not limited. My test
>> > account has 4900 followers and 4600 unfollowed followers. Can I DM
>> > them in parallel? Serially? Five at a time? What's the polite thing to
>> > do here?
>>
>> > Thanks,
>> > Tony
>> >http://www.stubbleblog.com
>> >http://www.crowdvine.com
>>
>> --
>> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
>



-- 
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x


Re: Date followed?

2008-10-30 Thread Alex Payne

This is something we're happy to provide, but probably won't get to in
the current version of the API.

On Thu, Oct 30, 2008 at 7:10 AM, Ed Finkler <[EMAIL PROTECTED]> wrote:
> Currently there's nothing available via the API – you'd probably need
> to cache your whole followers list and then compare the last version
> to the newest. You probably should file an issue in the tracker if one
> does not already exist for this feature request:
>
> http://code.google.com/p/twitter-api/issues/list
>
> --
> Ed Finkler
> http://funkatron.com
> AIM: funka7ron
> ICQ: 3922133
> Skype: funka7ron
>
>
> On Thu, Oct 30, 2008 at 9:22 AM, Ryan Bigg <[EMAIL PROTECTED]> wrote:
>>
>> I am also interested in this feature.
>>
>



-- 
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x


Re: Does direct_messages (Twitter API) support RFC 1123/RFC 822 date time format

2008-10-30 Thread Alex Payne

The date in the examples in the documentation was taking from a
working test, but is now outdated (you can only use since and
If-Modified-Since with dates within the last 24 hours).

On Wed, Oct 29, 2008 at 7:23 PM, krishnan chakravarthi
<[EMAIL PROTECTED]> wrote:
>
> Alex,
>
> Would it be possible to share an example date that works in your
> environment (perhaps a test case)?
> I have tried a bunch of things at my end without much success. Any
> help is appreciated.
>
> Thanks
> Kris
>
> On Wed, Oct 29, 2008 at 8:32 PM, Alex Payne <[EMAIL PROTECTED]> wrote:
>>
>> We're pretty sure this isn't a bug on our end.  It's come up before,
>> and it's usually some client-side date formatting issue.  We've got
>> solid test coverage for it, too.
>>
>> On Wed, Oct 29, 2008 at 8:42 AM, krishnan chakravarthi
>> <[EMAIL PROTECTED]> wrote:
>>>
>>> Thanks for the replies.
>>> I played around with Ruby 1.8.6 and date sent to Date.parse is now in
>>> the correct format:
>>>
>>> URL string:
>>> http://twitter.com/direct_messages.xml?since=Mon27Oct2008
>>>
>>> (No Urlencoding is needed as there are no special characters or spaces)
>>>
>>> Ruby Check:
>>> irb(main):037:0> d8 = Date.parse("Mon27Oct2008")
>>> => #
>>> irb(main):038:0> d8.ctime()
>>> => "Mon Oct 27 00:00:00 2008"
>>>
>>> Note: It is useless providing a time (hr:min:sec) as Date class
>>> ignores this and outputs date in the above format. Perhaps Twitter
>>> documentation could be updated to mention this or the API can switch
>>> to using Ruby DateTime class.
>>>
>>> I see a http code 302 (page redirect) returned from twitter. The
>>> expected results should be all direct messages sent to the
>>> authenticating user after Mon Oct 27.
>>> It looks like Ruby is generating the correct date but the API does not
>>> recognize the format?perhaps an API bug.
>>>
>>>
>>> On 10/28/08, Alex Payne <[EMAIL PROTECTED]> wrote:

 Any format that Ruby 1.8.6's Date.parse method can comprehend will be 
 processed.

 On Tue, Oct 28, 2008 at 11:42 AM, krishnan chakravarthi
 <[EMAIL PROTECTED]> wrote:
 >
 > I changed the date format and it made no difference. I am using PHP
 > urlencode method as shown below:
 > "direct_messages.xml?since=". urlencode(stripslashes(urldecode("Mon,
 > 27 Oct 13:00:00 EST 2008")));
 > The date/time format is as specified in RFC822.
 >
 > The urlencoded string is output as: Mon%2C+27+Oct+13%3A00%3A00+EST+2008
 >
 > Note: %3A is encoding format for : (colon) symbol.
 > Twitter returns a 302 return code.
 >
 > Not sure why Date.parse(CGI.unescape()) mangles the date string as
 > urldecode/encode and cgi.escape/unescape work the same way and
 > Date.parse should accept RFC822 compliant dates. What Ruby version is
 > installed in development environment? Is there a specific format in
 > which API expects date/time, to work with Date.parse method.
 >
 >
 >
 >
 > On 10/27/08, Alex Payne <[EMAIL PROTECTED]> wrote:
 >>
 >> Your date does not appear to be properly CGI-encoded:
 >>
 >> >> Date.parse(CGI.unescape("Sun%2C+26+Oct+22%3:55%3:48+000+2008"))
 >> => Mon, 26 Oct 0022
 >>
 >> That's what Ruby in our development environment thinks your date is.
 >> Those "%3"s might be the culprit.
 >>
 >> On Mon, Oct 27, 2008 at 2:01 PM, Kris <[EMAIL PROTECTED]> wrote:
 >> >
 >> > I am aware of the example in the documentation.
 >> > Thanks for pointing it out and I apologize for not mentioning before
 >> > that I had tried the format listed in the documentation.
 >> >
 >> > For example:
 >> > $this->twitterHost .= "direct_messages.xml?since=Sun%2C+26+Oct
 >> > +22%3:55%3:48+000+2008";
 >> > results in error number 502 (server busy) and "Twitter is over
 >> > capacity" message.
 >> > Not sure why the API does not throw a format error?
 >> >
 >> > I saw a post (http://groups.google.com/group/twitter-development-talk/
 >> > browse_thread/thread/e97f02c8b8012fb5) which mentions that the API
 >> > conforms to RFC1123 but that does not work either.
 >> >
 >> > Any thoughts?
 >> >
 >> > Thanks
 >> >
 >> > On Oct 27, 4:35 pm, "Damon Clinkscales" <[EMAIL PROTECTED]> wrote:
 >> >> On Mon, Oct 27, 2008 at 1:48 PM, Kris <[EMAIL PROTECTED]> wrote:
 >> >>
 >> >> > The API documentation does not clearly list the date format for
 >> >> > obtaining direct_messages sent to a user (within the specified 
 >> >> > date/
 >> >> > time window).
 >> >> > I am using RFC 1123/822 format but do not get any messages sent 
 >> >> > with
 >> >> > in the specified date/time window:
 >> >>
 >> >> > For Example:
 >> >>
 >> >> > direct_messages.xml?since=".urlencode("Sun, 26 Oct 2008 22:00:00 
 >> >> > EST")
 >> >>
 >> >> > (does not return any messages or errors.)
 >> >>
 >> >> > What is the correct d

Return user information in verify_credentials instead of just string representing authorized?

2008-10-30 Thread Lien Tran

Return user information in verify_credentials instead of just string
representing authorized? Useful if we could get the user id at this
time instead of having to make a separate call to get the data.


Return user information in verify_credentials instead of just string representing authorized?

2008-10-30 Thread Lien Tran

Return user information in verify_credentials instead of just string
representing authorized? Useful if we could get the user id at this
time instead of having to make a separate call to get the data.


Re: Facebook

2008-10-30 Thread t0ny

http://apps.facebook.com/twitter/ did you try this app ?


Re: Return user information in verify_credentials instead of just string representing authorized?

2008-10-30 Thread Alex Payne

Sure, that's a thing we could do.  Please request it:
http://code.google.com/p/twitter-api/issues/entry

On Thu, Oct 30, 2008 at 11:56 AM, Lien Tran <[EMAIL PROTECTED]> wrote:
>
> Return user information in verify_credentials instead of just string
> representing authorized? Useful if we could get the user id at this
> time instead of having to make a separate call to get the data.
>



-- 
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x


Re: Date followed?

2008-10-30 Thread Jesse Stay


Thanks Alex.  Has there been any communication as to what we should be  
planning for in the new version of the API?  What is being changed?   
How is progress on it, and when can we expect to see something we can  
play with?  Will we be able to test it out any before you release?


Thanks,

Jesse

On Oct 30, 2008, at 11:22 AM, Alex Payne wrote:



This is something we're happy to provide, but probably won't get to in
the current version of the API.

On Thu, Oct 30, 2008 at 7:10 AM, Ed Finkler <[EMAIL PROTECTED]>  
wrote:

Currently there's nothing available via the API – you'd probably need
to cache your whole followers list and then compare the last version
to the newest. You probably should file an issue in the tracker if  
one

does not already exist for this feature request:

http://code.google.com/p/twitter-api/issues/list

--
Ed Finkler
http://funkatron.com
AIM: funka7ron
ICQ: 3922133
Skype: funka7ron


On Thu, Oct 30, 2008 at 9:22 AM, Ryan Bigg  
<[EMAIL PROTECTED]> wrote:


I am also interested in this feature.







--
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x




Uploading profile picture via API

2008-10-30 Thread samgrover

Hi,

Is there a mechanism to upload a user's profile picture via the API or
some other undocumented means?

Thanks,
Sam


Re: Uploading profile picture via API

2008-10-30 Thread Abraham Williams
http://apiwiki.twitter.com/REST%20API%20Documentation#AccountMethods

On Thu, Oct 30, 2008 at 21:00, samgrover <[EMAIL PROTECTED]> wrote:

>
> Hi,
>
> Is there a mechanism to upload a user's profile picture via the API or
> some other undocumented means?
>
> Thanks,
> Sam
>



-- 
| Abraham Williams | Web Developer | http://abrah.am
| PoseurTech LLC | Mashup Ambassador | http://poseurte.ch
| Web608 | Community Evangelist | http://web608.org
| This email is: [] blogable [x] ask first [] private