Users should be able to log in and publish to their Write.as account from the Linux desktop app.
With T603: Publish to account / collections finished in the Write.as CLI, we should let users:
TODO
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T638 Publish to Write.as account from Linux app | ||
| Resolved | robjloranger | T603 Publish to account / collections | ||
| Resolved | robjloranger | T602 List collections | ||
| Resolved | robjloranger | T604 Fetch user posts if authenticated | ||
| Invalid | robjloranger | T605 get authentication working | ||
| Invalid | robjloranger | T606 Delete account post | ||
| Resolved | robjloranger | T610 Send title when publishing | ||
| Resolved | robjloranger | T630 v1 -> v2 compatability | ||
| Resolved | robjloranger | T632 update docs | ||
| Invalid | robjloranger | T633 post to specific collection | ||
| Resolved | christopherdavis | T692 Add password flag to CLI |
One prerequisite I see for this is changing the authentication process. Currently the write.as cli asks for input in the form of the password, after you feed it a username. I'm not sure
if there's a way to provide that input from a GTK app. So, there are two options I can think of:
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.
For us, the current behavior could remain unchanged, and if someone provides a non-empty -p flag, we could skip the interactive prompt and just use the given value.