While this makes me happy (from a developers point of view), surely
this is a bug and therefore not to be relied on?
As a user, I agree with the logic that if I authorised Read only, the
application shouldn't be able to turn this into Read/Write without
some subsequent approval.
Tim
On Jan 31,
Actually, since the user needs to re-authorize the application, I do not
think that this is a bug.
Tom
On 1/31/11 10:45 PM, Tim Bull wrote:
While this makes me happy (from a developers point of view), surely
this is a bug and therefore not to be relied on?
As a user, I agree with the logic
The way I read Abraham's note, he's saying that by simply upgrading
the token from read to read/write he was able to write? I didn't take
it to mean he had also sent the user to reauthorise?
T
On Feb 1, 8:46 am, Tom van der Woerdt i...@tvdw.eu wrote:
Actually, since the user needs to
Upgraded by going through the authorization flow.
Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
@abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Mon, Jan 31, 2011 at 15:34, Tim Bull
Apparently there was a bug before (which I now recall), where if the
developer set it to read only, and subsequently changed it to
read-write, it wouldn't really change to read-write. However, per
earlier conversation in this thread, that issue appears to have
finally been fixed.
So, if you, as
OK, that's more or less what I expected.
Just one last confirmation - the API key won't change though right?
So if I add read / write the read users won't suddenly be de-
authenticated?
Cheers,
Tim
On Jan 31, 6:19 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
You'll have to re-ask
