Re: General Request for Assignment (imap-keywords) (was: [JMAP] SMIME Attachments)
Neil Jhaveri <[email protected]> Wed, 15 Nov 2017 22:13:39 -0700
| Newsgroups | gmane.ietf.imapext |
|---|---|
| Message-ID | <[email protected]> |
--===============8306285798127023534== Content-Type: multipart/alternative; boundary="Apple-Mail=_613F6718-30F4-4096-AEE3-686D87B87FA8" --Apple-Mail=_613F6718-30F4-4096-AEE3-686D87B87FA8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Nov 14, 2017, at 5:17 PM, Bron Gondwana <[email protected]> = wrote: >=20 > I still remain unconvinced that the usecase is common enough that any = client would use it, particularly since the first client still needs to = download the message so it can set the flag. I agree, I just don=E2=80=99t see the value of this being significant = enough, since it only helps the second+ client that comes along. If you are dealing with messages encrypted as a single blob, and want to = have a good user experience, you probably have to venture into = thick-client territory and proactively download/decrypt the message = locally anyways. Otherwise, how can you provide full-text body search, = or a UI with a message preview, as many clients seem to be doing = nowadays? Doesn=E2=80=99t that also diminish the need for this keyword? Have I missed some important use-case?= --Apple-Mail=_613F6718-30F4-4096-AEE3-686D87B87FA8 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" = class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div = class=3D"">On Nov 14, 2017, at 5:17 PM, Bron Gondwana <<a = href=3D"mailto:[email protected]" = class=3D"">[email protected]</a>> wrote:</div><br = class=3D"Apple-interchange-newline"><div class=3D""><span = style=3D"font-family: Arial; font-size: 12px; font-style: normal; = font-variant-caps: normal; font-weight: normal; letter-spacing: normal; = text-align: start; text-indent: 0px; text-transform: none; white-space: = normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; = display: inline !important;" class=3D"">I still remain unconvinced that = the usecase is common enough that any client would use it, particularly = since the first client still needs to download the message so it can set = the flag.</span></div></blockquote></div><br class=3D""><div class=3D"">I = agree, I just don=E2=80=99t see the value of this being significant = enough, since it only helps the second+ client that comes = along.</div><div class=3D""><br class=3D""></div><div class=3D"">If you = are dealing with messages encrypted as a single blob, and want to have a = good user experience, you probably have to venture into thick-client = territory and proactively download/decrypt the message locally anyways. = Otherwise, how can you provide full-text body search, or a UI with a = message preview, as many clients seem to be doing nowadays?</div><div = class=3D""><br class=3D""></div><div class=3D"">Doesn=E2=80=99t that = also diminish the need for this keyword?</div><div class=3D""><br = class=3D""></div><div class=3D"">Have I missed some important = use-case?</div></body></html>= --Apple-Mail=_613F6718-30F4-4096-AEE3-686D87B87FA8-- --===============8306285798127023534== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ imapext mailing list [email protected] https://www.ietf.org/mailman/listinfo/imapext --===============8306285798127023534==--