More user discussion here.

I agree about not wanting to have passwords in command line users' history, but I think supporting an optional password flag would be the simplest route. I'm thinking of the mysql client as an example, where you can supply -p without anything else and it'll interactively prompt for a password, or accept a password along with the flag if you want.

Went with ReqLog(), not InfoLog()

Pull request #148: https://github.com/writeas/writefreely/pull/148

Pull request #149: https://github.com/writeas/writefreely/pull/149

We decided on pherephone for the name: https://github.com/writeas/pherephone

Just a heads up @robjloranger: noticed a bug in WriteFreely when testing this, and fixed it in #144. Basically the full collection URL wasn't getting sent back, so after publishing I'd see /matt/new-post instead of https://team.write.as/matt/new-post

Yep, if there's already a default set when running auth it won't be overwritten. And there will be a message displayed either way. The idea with setting it that first time is to make that process more seamless, and save people some typing.

Ah, gotcha. I'll add that in then.

Right now there's no config.ini file being created in my ~/.writefreely... But it's entirely possible I messed something up. I'm looking into it now

@robjloranger How does this work right now? After playing around with wf-cli this is definitely the default behavior I'd like to see, but I'm not seeing it work that way.

Just checking this off the list

We can at least get started on the frontend now.

This requires T550 -- it's not a required part of it.