Re: [twitter-dev] Re: Update on Twifficiency

2010-08-19 Thread Aman deep
its not my reply dear i want the complete api and code to share my website images to my twitter account thanking you On Thu, Aug 19, 2010 at 3:16 AM, Daniel Ribeiro dan...@gmail.com wrote: It would be nice to have something that make things clearer to the user that the requesting app is

[twitter-dev] Re: Update on Twifficiency

2010-08-18 Thread Daniel Ribeiro
It would be nice to have something that make things clearer to the user that the requesting app is requesting write rights. Like a big red warning on the Deny/allow page. On Aug 18, 6:17 pm, Tom van der Woerdt i...@tvdw.eu wrote: +1 On 8/18/10 10:55 PM, Eric Marden - API Hacker wrote: On

Re: [twitter-dev] Re: Update on Twifficiency

2010-08-18 Thread M. Edward (Ed) Borasky
+1 ... see previous email ... although I don't think Twitter necessarily needs to do that - it's really the app developer's responsibility to document what it's supposed to do and how to tell when it's misbehaving. -- M. Edward (Ed) Borasky http://borasky-research.net

[twitter-dev] Re: Update on Twifficiency

2010-08-18 Thread Ben Metcalfe
What I'd actually like to see is some granularity in the oAuth permissions that go beyond binary has complete access: DENY|ALLOW, and this would also solve this problem. Surprising users when an app auto-tweets is one thing, but I'm more concerned about a given app reading my DM's, for example

Re: [twitter-dev] Re: Update on Twifficiency

2010-08-18 Thread Peter Denton
My opinion is that twitter is trying to keep it intentionally simple for the benefit of apps. for Joe Regular, more options than allow / deny is going to create confusion and apps will suffer. Its pretty clear that if you tweet on behalf of users without consent there will be confusion/anger and