[Bug 70626] Provide access to the user and host parts of RPL_WHOISUSER

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=70626

--- Comment #3 from Simon McVittie <simon.mcvittie at collabora.co.uk> ---
I'd like to see a patch for telepathy-spec (more specifically
spec/Connection_Interface_Contact_Info.xml) which adds these pseudo-fields to
the <tp:docstring> of VCard_Field, perhaps something like this in a <dl> (but
please note that I'm reverse-engineering these descriptions from telepathy-idle
source code, so I might be wrong):

    In addition to standardized vCard fields, Telepathy defines several
    non-standard fields:

        x-irc-server
            A sequence of up to two strings, in which the first is
            the name of a specific server within the IRC network (e.g.
            irc1.eu.example.net) and the second, if present, is human-readable
            information about that server

        x-presence-type
            The ASCII decimal value of a Connection_Presence_Type, used
            on protocols such as IRC where presence information is
            not necessarily "pushed" to contacts, but must be polled
            infrequently

            <tp:rationale>
              IRC's "away messages" don't fit the SimplePresence
              interface well, because that interface assumes an XMPP-like
              "push" model.
            </tp:rationale>

        x-presence-status-identifier
            The well-known string identifier of a presence status, such
            as "away", on protocols where x-presence-type is used.
            This corresponds to the second element of a Simple_Presence.

        x-presence-status-message
            The human-readable part of a presence status, such
            as "Gone to lunch", on protocols where x-presence-type is used.
            This corresponds to the third element of a Simple_Presence.

        x-irc-operator
            The literal string "true" if the contact is an IRC operator
            as described in RFC 2812 §1.2.1.1, or the literal string
            "false" if they are not.

            Note that channel operators ("ops"), typically denoted by
            the @ prefix in IRC clients, are not usually IRC operators.

        x-irc-registered-nick
            The literal string "true" if the contact's nickname is
            registered with the IRC network's services (e.g. NickServ)
            or the literal string "false" if not.

        x-irc-secure-connection
            The literal string "true" if the contact is connected
            to their server via a secure connection (SSL/TLS), or the
            literal string "false" if not.

        x-irc-channel
            An channel in which this contact is present. This field
            takes an optional type-parameter "role" whose value is
            a prefix used to denote the contact's role in the channel.
            This field may be repeated.

            For instance, a contact who is a channel operator ("op")
            in #telepathy, a moderator ("voice") in #farstream
            and an ordinary user in #dbus and #chat might have this
            contact info:

            ("x-irc-channel", ["role=@"], ["#telepathy"]),
            ("x-irc-channel", ["role=+"], ["#farstream"]),
            ("x-irc-channel", [], ["#dbus"])
            ("x-irc-channel", [], ["#chat"])

        x-host
            [I'm not sure what this means, please fill it in]

        x-idle-time
            The ASCII decimal number of seconds for which this
            user has been idle.

To put HTML in a <tp:docstring> you have to use <tp:docstring
xmlns="http://www.w3.org/1999/xhtml"> - see VCard_Field_Address_Map for an
example of that.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.