Re: [Acme] UX design by standards

[Martin Thomson]

On 19 February 2017 at 05:40, Jacob Hoffman-Andrews  wrote:
> Do you have proposed alternate langauge, given the above?

Simply state the the description is designed for human consumption.
It's not localized, but it might help in more precisely identifying
the issue.  Then, let the clients decide what to do with that.

___
Acme mailing list
Acme@ietf.org
https://www.ietf.org/mailman/listinfo/acme

Re: [Acme] UX design by standards

[Martin Thomson]

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 with you that
attempting to push messages on users is foolish.  Record the details
in a log, sure, but trying to find a user, that's not gonna happen if
you are running acme clients on 1000s of machines.

___
Acme mailing list
Acme@ietf.org
https://www.ietf.org/mailman/listinfo/acme

[Acme] UX design by standards

[Josh Soref]

I'm still working on reviewing the document. I have one large PR which
I haven't finished and haven't published, and I have an entire design
issue (relating to errors) which I want to talk about. (And I need to
file a bug against rfc7807.) But...


> Clients SHOULD display the "detail" field of all errors. [1]

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?).

Browser authors never implemented the thing I'm thinking about (all I
remember is this quirk, I can't remember which thing it was).


[1] 
https://github.com/ietf-wg-acme/acme/blob/68a87b4/draft-ietf-acme-acme.md#errors

___
Acme mailing list
Acme@ietf.org
https://www.ietf.org/mailman/listinfo/acme