[Acme] why is the status value "invalid"

> status (required, string): : The status of this order. Possible values are: > "pending", "processing", "valid", and "invalid". > expires (optional, string): : The timestamp after which the server will > consider this order invalid, > encoded in the format specified in RFC 3339 {{!RFC3339}}.

[Acme] Removing public-key echo in account objects

Right now, account objects echo back the public key associated with the account, in the "key" field. However, this is redundant since the only request types that can return an account object are signed by the corresponding private key, so the client necessarily knows what its public key is.

Re: [Acme] UX design by standards

On 18 February 2017 at 00:42, Josh Soref wrote: > > I'm reminded ... there was one specification (i can't remember if it > was Cookie, HTTP, or HTML) which had a UAs must tell users about > something (redirects? cookies?). HTTP did, at one time have such text. I would agree