On Donnerstag, 25. Januar 2018 13:42:55 CET Jonas Wielicki wrote: > URL: https://xmpp.org/extensions/xep-0382.html
Yet-another-XEP I came aware of because of Deferral \o/.
The core idea is nice, but I have a few issues with this specific proposal:
- It appears that the XEP advocates non-spoiler use (the holidays.png
example). The large paste use-case should be handled in the UX of clients,
without requiring interaction from the sending client. Mixing the use-cases
will make the decision on a "show spoilers always" preference much harder and
confusing to users.
- Business Rule 1 ("It MUST be clear that a message is in fact a spoiler and
its content MUST only be displayed upon user's request.") does more read like
a requirement than a Business Rule.
- "Clients MAY display spoiler's hint even after showing message's content
(e.g. as a header or title of the message)." This does not seem sensible to
do. It further encourages abuse of the spoiler protocol. A heading could be
conveyed with <subject/> or markup, independent of this protocol.
- "Users SHOULD uncover or hide a spoiler message at will, anytime." Normally,
I don’t think we have business rules for users. This should probably read
"Clients SHOULD allow users to uncover or hide […]".
- It should be made clear whether rules exist for which xml:lang values must
exist on <spoiler/> elements based on whether they exist for <body/>. It might
make sense to put a SHOULD in there ("If there exists a <body/> with a
specific effective xml:lang value and at least one <spoiler/> element is used,
there SHOULD be exactly one <spoiler/> element with the same effective
xml:lang value.").
kind regards,
Jonas
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
