messlidger.contact

Module Contents

Classes

Contact	This class centralizes actions in relation to a specific legacy contact.
Roster	Virtual roster of a gateway user, that allows to represent all

Attributes

log

class messlidger.contact.Contact(session, legacy_id, jid_username, participant=None)

Bases: messlidger.util.ChatterMixin, slidge.LegacyContact[int]

This class centralizes actions in relation to a specific legacy contact.

You shouldn’t create instances of contacts manually, but rather rely on LegacyRoster.by_legacy_id() to ensure that contact instances are singletons. The LegacyRoster instance of a session is accessible through the BaseSession.contacts attribute.

Typically, your plugin should have methods hook to the legacy events and call appropriate methods here to transmit the “legacy action” to the xmpp user. This should look like this:

Use carbon=True as a keyword arg for methods to represent an action FROM the user TO the contact, typically when the user uses an official client to do an action such as sending a message or marking as message as read. This will use XEP-0363 to impersonate the XMPP user in order.

Parameters:

• session (messlidger.session.Session) – The session this contact is part of

• legacy_id (int) – The contact’s legacy ID

• jid_username (str) – User part of this contact’s ‘puppet’ JID. NB: case-insensitive, and some special characters are not allowed

• participant (Optional[maufbapi.types.graphql.ParticipantNode])

property fb_id

CORRECTION = False

REACTIONS_SINGLE_EMOJI = True

session: messlidger.session.Session

populate_from_participant(participant, update_avatar=True)

Parameters:

participant (maufbapi.types.graphql.ParticipantNode)

async get_thread(**kwargs)

async update_info(refresh=False)

Fetch information about this contact from the legacy network

This is awaited on Contact instantiation, and should be overridden to update the nickname, avatar, vcard […] of this contact, by making “legacy API calls”.

To take advantage of the slidge avatar cache, you can check the .avatar property to retrieve the “legacy file ID” of the cached avatar. If there is no change, you should not call slidge.core.mixins.avatar.AvatarMixin.set_avatar() or attempt to modify the .avatar property.

class messlidger.contact.Roster(session)

Bases: slidge.LegacyRoster[int, Contact]

Virtual roster of a gateway user, that allows to represent all of their contacts as singleton instances (if used properly and not too bugged).

Every BaseSession instance will have its own LegacyRoster instance accessible via the BaseSession.contacts attribute.

Typically, you will mostly use the LegacyRoster.by_legacy_id() function to retrieve a contact instance.

You might need to override LegacyRoster.legacy_id_to_jid_username() and/or LegacyRoster.jid_username_to_legacy_id() to incorporate some custom logic if you need some characters when translation JID user parts and legacy IDs.

Parameters:

session (slidge.core.session.BaseSession)

session: messlidger.session.Session

async by_legacy_id_if_known(legacy_id)

Parameters:

legacy_id (int)

async by_thread_key(t)

Parameters:

t (maufbapi.types.mqtt.ThreadKey)

async by_thread(t)

Parameters:

t (maufbapi.types.graphql.Thread)

get_friend_participant(nodes)

Parameters:

nodes (list[maufbapi.types.graphql.ParticipantNode])

Return type:

maufbapi.types.graphql.ParticipantNode

messlidger.contact.log