Difference between revisions of "Roster"

Jump to navigation Jump to search
Add mailing list discussion notes: https://mail.jabber.org/hyperkitty/list/standards@xmpp.org/thread/O52EPUXS3UEBTONKEYSI4U66OR5MDDZW/
(Move from Usability/Roster)
 
(Add mailing list discussion notes: https://mail.jabber.org/hyperkitty/list/standards@xmpp.org/thread/O52EPUXS3UEBTONKEYSI4U66OR5MDDZW/)
 
Line 1: Line 1:
The '''roster''' or '''contact list''' is the entry point for the user to their contacts. It is thus a key part in the user experience of any XMPP clients. [[ModernXMPP]] suggests using '''Contact list''' instead of "Roster".
The '''roster''' or '''contact list''' is the entry point for the user to their contacts. It is thus a key part in the user experience of any XMPP clients. [[ModernXMPP]] suggests using  
'''Contact list''' instead of "Roster".
 
== Features ==
* Multiple JIDs may belong to the same user. [https://xmpp.org/extensions/xep-0209.html XEP-0209] makes it possible to combine these within one contact.
* [https://xmpp.org/extensions/xep-0145.html XEP-0145] lets you add a personal note about a contact, similar to Discord and Slack.
* vCard4 support: [https://xmpp.org/extensions/xep-0292.html XEP-0292]
* Invitation system: in case a contact email or phone number is available without a JID, user might invite that contact via [https://xmpp.org/extensions/xep-0401.html XEP-0401].


== Roster groups ==
== Roster groups ==


Roster entries are organized in groups. There are two fundamentally different ways to model roster groups in a user interface.
Roster entries are organized in groups ([https://xmpp.org/extensions/xep-0144.html XEP-0144]). There are two fundamentally different ways to model roster groups in a user interface.


=== Hierarchical model ===
=== Hierarchical model ===
23

edits

Navigation menu