Yeah, the idea with POST was basically to mirror the way on-site edit
functionality works (with the bonus of being able to co-opt a bunch of the
existing pathways for doing that). I hadn't considered PATCH, though since
writing this initial spec we've swapped to OpenAPI3.0 which is a lot more
flexible about content-type.
Re: /api/v1/journals/{username}/entries/{id}
Yeah, the idea with POST was basically to mirror the way on-site edit functionality works (with the bonus of being able to co-opt a bunch of the existing pathways for doing that). I hadn't considered PATCH, though since writing this initial spec we've swapped to OpenAPI3.0 which is a lot more flexible about content-type.