Bump.
We'd love to be verified at http://sellsimp.ly as we have core
functionality that relys on DMs. If users could Dm without us
following it would be of great assistance.
Thanks,
Chris
On Jul 5, 8:39 am, Ryan craft.r...@gmail.com wrote:
Searched this forum and found nothing, but apparently
,
The new permission model applies to all access tokens, including the
application owner's one. You have to reauthorize your existing access_token
through the OAuth Flow, just like any other user.
Arnaud / @rno http://twitter.com/rno
On Thu, Jun 30, 2011 at 11:56 AM, Chris Teso christ
downer.
On Jun 30, 12:27 pm, Chris Teso christ...@gmail.com wrote:
Arnaud Taylor,
Thanks for the response. I must say that I'm confused as to why the
decision was made to block ones own app from reading their own DMs?
Can you elaborate on the logic behind this decision?
It seems logical
questions on this.
Thanks,
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
On Thu, Jun 30, 2011 at 12:27 PM, Chris Teso christ...@gmail.com wrote:
Arnaud Taylor,
Thanks for the response. I must say that I'm confused as to why the
decision was made
approach for separating concerns in an app.
Let me know if you have any questions on this.
Thanks,
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
On Thu, Jun 30, 2011 at 12:27 PM, Chris Teso christ...@gmail.com wrote:
Arnaud Taylor,
Thanks
The documentation at http://dev.twitter.com/doc/get/statuses/retweets/:id
states it will return up to 100 of the first retweets of a given
tweet.
However, in practice the method seems to only return the recent
Retweets for a given Tweet.
Take these two urls: http://www.flickfolia.com/free shows
Ah, ok. Seems you need to specify count param to be accurate.
On Jun 26, 10:22 pm, Chris Teso christ...@gmail.com wrote:
The documentation athttp://dev.twitter.com/doc/get/statuses/retweets/:id
states it will return up to 100 of the first retweets of a given
tweet.
However, in practice
@anywhere currently does not support https. As a work around you could
download http://platform.twitter.com/anywhere.js locally and pull it
off your server via https.
This comes with it's own challenges, as you'll need to manually update
when Twitter decides to update their codebase, but it will
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 http://twitter.com/rnoOn Tue, Apr 5, 2011 at 4:34 PM, Chris
Teso christ...@gmail.com 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
10 matches
Mail list logo
