On 04/01/2013 00:03, Mark Rejhon wrote:
This has some interesting applications, such as specialized privileges
for chat participants wearing a "hat".
For example, a set of teacher/lecturers in a MUC room could be granted
a special "hat" in a MUC room.
Specialized privileges could also include real-time text (XEP-0301) or
the ability to present certain types of media that other chatroom
participants aren't allowed to do so to prevent distractions from the
main people of focus in the online MUC classroom.
It appears hats could provide a mechanism to do this without
necessarily granting room administrator privelages which can lead to
security issues, DDoS or disruption (from, say, troublemaking
students). Chat clients would be optimized to recognize specific hats
(labels to be standardized at a future time) as granting permission to
do certain things in in the chat software.
A student "raising a hand" in a MUC (/me raises hand) can be
temporarily given a special hat, that temporarily grants them these
privelages of presenting rich media to the chatroom in a controlled
way.
I agree, specialized privileges would be great, instead of the
inflexible 0045 scheme (which is good for classic MUC, but not
so useful for customized uses). But this would require a
specification of each feature that could be a privilege, plus the
XEPs applicable in a room (e.g. xhtml-im, corrections, chatstates),
and I think this could be quite a lot of work.
Concerning the format, I prefer the first and second proposals rather
than the third, it feels more “natural” to me.
I noticed that the XEP does not contain an example for adding a “type”
of hat, is it because that management is left to the server administrator
in some way?
And finally, I think the type of the field for choosing the hat can be
list-multi instead of list-single.
----
Mathieu Pasquet (mathieui)
