In progress as there is no writefreely CLI yet on that branch

in go-writeas PostParams tells JSON to ignore the Collection field

In T586#10141, @robjloranger wrote:

I've got a weird issue, maybe it is by design.

I can not create a new anonymous post against my single user instance using wf. Which would be writeas in the other. The default Post command.

I've got a weird issue, maybe it is by design.

I reverted the change for now, maybe we can revisit in the future but it might be a limitation of the library.

weird, it doesn't work without the flags all being listed as global. Which feels wrong as we never access global flags directly and the cli library docs do not mention anything about that working this way.

removed parent as this should not be a hard requirement but a nice to have feature

via GH#32

second iteration for structure and hierarchy

Another question, do we want to have write.as as the default? as above. Or as a host like others, so we would require writefreely CLI users to either specify a host or set a default. I'm leaning towards this myself.

I've been thinking about this one this morning.

any CLI flags provided should override the stored preferences

This task will include the full new directory structure.

I don't think we should store the posts.json and use it for subsequent requests. For example, when would it expire? There may be more posts on the remote or something may have changed.

or re: fetch text, could just add a description text for clarification.

already working