search

hoop33 / wry

App.net command-line client for Mac OS X
http://grailbox.com/wry
MIT License
43 stars 6 forks source link

Support multiple users #24

Closed timpritlove closed 11 years ago

timpritlove commented 11 years ago

It would be nice if wry could support multiple users by allowing multiple authorizations to exist in parallel. The authorization to be used on each individual call could be set by a -u option and there should be another option to set the default user (which is by default the first authorized user).

timpritlove commented 11 years ago

\o/

hoop33 commented 11 years ago

:-) let me know what you think. I'm putting together a homebrew formula now.

timpritlove commented 11 years ago

Hm, when I call "wry authorize" a second time, the authorization replaces the first one. "wry users" only lists the last authorization. Also, "--user myauthoruzedusername" does not work, only "--user default" which is strange.

hoop33 commented 11 years ago

When you call wry authorize the second time, do you pass a different user?

wry authorize -u foo

Tim Pritlove wrote:

Hm, when I call "wry authorize" a second time, the authorization replaces the first one. "wry users" only lists the last authorization. Also, "--user myauthoruzedusername" does not work, only "--user default" which is strange.

— Reply to this email directly or view it on GitHub https://github.com/hoop33/wry/issues/24#issuecomment-17161549.

timpritlove commented 11 years ago

No I didn't, now it works. That isn't really documented with "wry help authorize". But I must say I find it awkward to give another nickname to an account that already has a nickname. I would suggest getting rid of those extra nicks and just to use the real account name. Another command just sets whatever the current default should be.

hoop33 commented 11 years ago

Yeah, I've been going back and forth with that. When you call wry authorize, I have no idea who the user is--I just get back a token. I would have to call back to app.net to get the actual user ID before storing in the keychain.

It sounds like that's what I ought to do, though. Agreed? Give me a day or two.

Thanks for your feedback--that really helps!

On Monday, April 29, 2013, Tim Pritlove wrote:

No I didn't, now it works. That isn't really documented with "wry help authorize". But I must say I find it awkward to give another nickname to an account that already has a nickname. I would suggest getting rid of those extra nicks and just to use the real account name. Another command just sets whatever the current default should be.

— Reply to this email directly or view it on GitHubhttps://github.com/hoop33/wry/issues/24#issuecomment-17163530 .

Rob Warner rwarner@grailbox.com

timpritlove commented 11 years ago

I agree. Just look it up with ADN and you're set. But the current way is just going to cause a lot of confusion.

hoop33 commented 11 years ago

I've pushed changes in Issue #27 to: 1) After authorize, get the actual user ID from App.net and use that as the key into the keychain 2) If you have no authorized user, make the first authorized user the default 3) Add 'delete' and 'default' to the 'users' command (see 'wry help users' for more info)

It's in the develop branch--do you want to give this a spin and see if that makes sense? I'd like to get this right before getting this into homebrew. Thanks for your feedback!

timpritlove commented 11 years ago

Excellent changes. I think you nailed it this time.

hoop33 commented 11 years ago

Thanks!

On Thursday, May 2, 2013, Tim Pritlove wrote:

Excellent changes. I think you nailed it this time.

— Reply to this email directly or view it on GitHubhttps://github.com/hoop33/wry/issues/24#issuecomment-17341592 .

Rob Warner rwarner@grailbox.com