- class slidge.plugins.facebook.contact.Contact(session, legacy_id, jid_username, participant=None)[source]#
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
LegacyRosterinstance of a session is accessible through the
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:
carbon=Trueas 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.
session (slidge.plugins.facebook.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]) –
- async _expire(last_seen)[source]#
last_seen (datetime.datetime) –
- populate_from_participant(participant, update_avatar=True)[source]#
participant (maufbapi.types.graphql.ParticipantNode) –
- async send_fb_sticker(sticker_id, legacy_msg_id, **kwargs)[source]#
- async update_info(refresh=False)[source]#
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”.
- async get_attachment_url(attachment, thread_key, msg_id)[source]#
attachment (maufbapi.types.mqtt.Attachment) –
- class slidge.plugins.facebook.contact.Roster(session)[source]#
Virtual roster of a gateway user, that allows to represent all of their contacts as singleton instances (if used properly and not too bugged).
BaseSessioninstance will have its own
LegacyRosterinstance accessible via the
Typically, you will mostly use the
LegacyRoster.by_legacy_id()function to retrieve a contact instance.
You might need to override
LegacyRoster.jid_username_to_legacy_id()to incorporate some custom logic if you need some characters when translation JID user parts and legacy IDs.
session (slidge.core.session.BaseSession) –