Re: [twitter-dev] Re: direct_messages/new

2011-04-07 Thread Abraham Williams 
Chris,

You should also be using 'user_id' instead of 'user' in the request that
succeeds.

Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
 Just launched from Answerly :
InboxQfor Chrome
@abraham  | github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.



On Wed, Apr 6, 2011 at 22:39, Arnaud Meunier  wrote:

> Hey Chris,
>
> Looks like you're missing an "s" to direct_messages in the PHP code you're
> quoting. Would be interested to see your HTTP Response headers. Probably a
> 404 you got there.
>
> Arnaud / @rno 
>
>
>
> On Wed, Apr 6, 2011 at 10:24 PM, Chris Teso  wrote:
>
>> The Full http response is NULL.
>>
>> The request sent is $this->connection->post('direct_message/new',
>> array( 'screen_name' => $username, 'text' => $text ) ) with proper
>> auth headers.
>>
>> Again, the method works if we pass user_id rather than screen_name.
>> $this->connection->post( 'direct_messages/new', array( 'user' =>
>> 19081905, 'text' => $text ) );
>>
>> Using screen_name has been working for 4 months in our app, and
>> stopped working 2 days ago.
>>
>> Thanks
>>
>> On Apr 5, 10:02 pm, Arnaud Meunier  wrote:
>> > Hey Chris,
>> >
>> > The endpoint is working fine with both parameters (just tested it).
>> >
>> > If you're still having this issue, think to provide more details (i.e.
>> > request sent with auth headers + Full HTTP response). Otherwise, people
>> of
>> > this Mailing List won't be able to help you that much!
>> >
>> > Arnaud / @rno On Tue, Apr 5, 2011 at 4:34 PM,
>> Chris Teso  wrote:
>> > > direct_messages/new seems to have stopped working if using
>> > > screen_name.
>> >
>> > > The method works if passing user_id.
>> >
>> > > Can you confirm either way?
>> >
>> > > --
>> > > 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 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: direct_messages/new

2011-04-06 Thread Arnaud Meunier 
Hey Chris,

Looks like you're missing an "s" to direct_messages in the PHP code you're
quoting. Would be interested to see your HTTP Response headers. Probably a
404 you got there.

Arnaud / @rno 



On Wed, Apr 6, 2011 at 10:24 PM, Chris Teso  wrote:

> The Full http response is NULL.
>
> The request sent is $this->connection->post('direct_message/new',
> array( 'screen_name' => $username, 'text' => $text ) ) with proper
> auth headers.
>
> Again, the method works if we pass user_id rather than screen_name.
> $this->connection->post( 'direct_messages/new', array( 'user' =>
> 19081905, 'text' => $text ) );
>
> Using screen_name has been working for 4 months in our app, and
> stopped working 2 days ago.
>
> Thanks
>
> On Apr 5, 10:02 pm, Arnaud Meunier  wrote:
> > Hey Chris,
> >
> > The endpoint is working fine with both parameters (just tested it).
> >
> > If you're still having this issue, think to provide more details (i.e.
> > request sent with auth headers + Full HTTP response). Otherwise, people
> of
> > this Mailing List won't be able to help you that much!
> >
> > Arnaud / @rno On Tue, Apr 5, 2011 at 4:34 PM,
> Chris Teso  wrote:
> > > direct_messages/new seems to have stopped working if using
> > > screen_name.
> >
> > > The method works if passing user_id.
> >
> > > Can you confirm either way?
> >
> > > --
> > > 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: direct_messages/new

2011-04-06 Thread Matt Harris 
I'm not able to reproduce this so could you share the base signature you are
sending. The consumer_secret and user_secret are not included in those two
pieces of data so can be shared here, but if you prefer you can directly
email them to me.

Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris


On Wed, Apr 6, 2011 at 10:24 PM, Chris Teso  wrote:

> The Full http response is NULL.
>
> The request sent is $this->connection->post('direct_message/new',
> array( 'screen_name' => $username, 'text' => $text ) ) with proper
> auth headers.
>
> Again, the method works if we pass user_id rather than screen_name.
> $this->connection->post( 'direct_messages/new', array( 'user' =>
> 19081905, 'text' => $text ) );
>
> Using screen_name has been working for 4 months in our app, and
> stopped working 2 days ago.
>
> Thanks
>
> On Apr 5, 10:02 pm, Arnaud Meunier  wrote:
> > Hey Chris,
> >
> > The endpoint is working fine with both parameters (just tested it).
> >
> > If you're still having this issue, think to provide more details (i.e.
> > request sent with auth headers + Full HTTP response). Otherwise, people
> of
> > this Mailing List won't be able to help you that much!
> >
> > Arnaud / @rno On Tue, Apr 5, 2011 at 4:34 PM,
> Chris Teso  wrote:
> > > direct_messages/new seems to have stopped working if using
> > > screen_name.
> >
> > > The method works if passing user_id.
> >
> > > Can you confirm either way?
> >
> > > --
> > > 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