slidge.plugins.facebook#

Submodules#

Package 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

Gateway

Must be subclassed by a plugin to set up various aspects of the XMPP

Session

Represents a gateway user logged in to the legacy network and performing actions.
class slidge.plugins.facebook.Contact(session, legacy_id, jid_username, participant=None)[source]#

Bases: 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 (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]) –

CORRECTION = False#
REACTIONS_SINGLE_EMOJI = True#
session: slidge.plugins.facebook.session.Session#
AWAY_AFTER#
XA_AFTER#
async _expire(last_seen)#
Parameters:

last_seen (datetime.datetime) –

populate_from_participant(participant, update_avatar=True)#
Parameters:

participant (maufbapi.types.graphql.ParticipantNode) –

async get_thread(**kwargs)#
async send_fb_sticker(sticker_id, legacy_msg_id, **kwargs)#
Parameters:

  • sticker_id (int) –

  • legacy_msg_id (str) –

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”.

async send_fb_message(msg, **kwargs)#
Parameters:

msg (maufbapi.types.mqtt.Message) –

async send_fb_attachment(msg, **kwargs)#
async get_attachment_url(attachment, thread_key, msg_id)#
Parameters:

attachment (maufbapi.types.mqtt.Attachment) –

update_presence(presence)#
Parameters:

presence (maufbapi.types.mqtt.message.PresenceInfo) –

class slidge.plugins.facebook.Roster(session)[source]#

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: slidge.plugins.facebook.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

class slidge.plugins.facebook.Gateway[source]#

Bases: slidge.BaseGateway

Must be subclassed by a plugin to set up various aspects of the XMPP component behaviour, such as its display name or its registration process.

On slidge launch, a singleton is instantiated, and it will be made available to public classes such LegacyContact or BaseSession as the .xmpp attribute. Since it inherits from slixmpp.componentxmpp.ComponentXMPP, this gives you a hand on low-level XMPP interactions via slixmpp plugins, e.g.:

self.send_presence(
    pfrom="somebody@component.example.com",
    pto="someonwelse@anotherexample.com",
)

However, you should not need to do so often since the classes of the plugin API provides higher level abstractions around most commonly needed use-cases, such as sending messages, or displaying a custom status.

REGISTRATION_INSTRUCTIONS = 'Enter facebook credentials'#
REGISTRATION_FIELDS#
REGISTRATION_MULTISTEP = True#
REGISTRATION_TYPE#
ROSTER_GROUP = 'Facebook'#
COMPONENT_NAME = 'Facebook (slidge)'#
COMPONENT_TYPE = 'facebook'#
COMPONENT_AVATAR = 'https://upload.wikimedia.org/wikipedia/commons/thumb/6/6c/Facebook_Messenger_logo_2018.svg/480px-...'#
SEARCH_TITLE = 'Search in your facebook friends'#
SEARCH_INSTRUCTIONS = 'Enter something that can be used to search for one of your friends, eg, a first name'#
SEARCH_FIELDS#
async validate(user_jid, registration_form)#

Validate a registration form from a user.

Since XEP-0077 is pretty limited in terms of validation, it is OK to validate anything that looks good here and continue the legacy auth process via direct messages to the user (using BaseGateway.input() for instance).

Parameters:
async validate_two_factor_code(user, code)#

Called when the user enters their 2FA code.

Should raise the appropriate XMPPError if the login fails

Parameters:

  • user (slidge.GatewayUser) – The gateway user whose registration is pending Use their .bare_jid and/or``.registration_form`` attributes to get what you need

  • code – The code they entered, either via “chatbot” message or adhoc command

class slidge.plugins.facebook.Session(user)[source]#

Bases: slidge.BaseSession[str, Recipient]

Represents a gateway user logged in to the legacy network and performing actions.

Will be instantiated automatically when a user sends an online presence to the gateway component, as per XEP-0100.

Must be subclassed for a functional slidge plugin.

contacts: slidge.plugins.facebook.contact.Roster#
mqtt: slidge.plugins.facebook.client.AndroidMQTT#
api: maufbapi.AndroidAPI#
me: maufbapi.types.graphql.OwnInfo#
my_id: int#
async login()#

Login the gateway user to the legacy network.

Triggered when the gateway start and on user registration. It is recommended that this function returns once the user is logged in, so if you need to await forever (for instance to listen to incoming events), it’s a good idea to wrap your listener in an asyncio.Task.

Returns:

Optionally, a text to use as the gateway status, e.g., “Connected as ‘dude@legacy.network’”

async add_friends()#
async logout()#

Logout the gateway user from the legacy network.

Called on user unregistration and gateway shutdown.

async send_text(chat, text, *, reply_to_msg_id=None, **kwargs)#

Triggered when the user sends a text message from XMPP to a bridged entity, e.g. to translated_user_name@slidge.example.com, or translated_group_name@slidge.example.com

Override this and implement sending a message to the legacy network in this method.

Parameters:

  • text (str) – Content of the message

  • chat (Recipient) – RecipientType of the message. LegacyContact instance for 1:1 chat, MUC instance for groups.

  • reply_to_msg_id – A legacy message ID if the message references (quotes) another message (XEP-0461)

  • reply_to_fallback_text – Content of the quoted text. Not necessarily set by XMPP clients

  • reply_to – Author of the quoted message. LegacyContact instance for 1:1 chat, LegacyParticipant instance for groups. If None, should be interpreted as a self-reply if reply_to_msg_id is not None.

  • thread –

Returns:

An ID of some sort that can be used later to ack and mark the message as read by the user

Return type:

str

async send_file(chat, url, http_response, reply_to_msg_id=None, **_)#

Triggered when the user has sends a file using HTTP Upload (XEP-0363)

Parameters:
Returns:

An ID of some sort that can be used later to ack and mark the message as read by the user

async active(c, thread=None)#

Triggered when the user sends an ‘active’ chat state to the legacy network (XEP-0085)

Parameters:

c (Recipient) – RecipientType of the active chat state

async inactive(c, thread=None)#

Triggered when the user sends an ‘inactive’ chat state to the legacy network (XEP-0085)

Parameters:

c (Recipient) –

async composing(c, thread=None)#

Triggered when the user starts typing in the window of a legacy contact (XEP-0085)

Parameters:

c (Recipient) –

async paused(c, thread=None)#

Triggered when the user pauses typing in the window of a legacy contact (XEP-0085)

Parameters:

c (Recipient) –

async displayed(c, legacy_msg_id, thread=None)#

Triggered when the user reads a message sent by a legacy contact. (XEP-0333)

This is only possible if a valid legacy_msg_id was passed when transmitting a message from a contact to the user in LegacyContact.sent_text() or slidge.LegacyContact.send_file().

Parameters:
async correct(c, text, legacy_msg_id, thread=None)#

Triggered when the user corrected a message using XEP-0308

This is only possible if a valid legacy_msg_id was passed when transmitting a message from a contact to the user in LegacyContact.send_text() or slidge.LegacyContact.send_file().

Parameters:

  • text (str) –

  • legacy_msg_id (str) –

  • c (Recipient) –

async react(c, legacy_msg_id, emojis, thread=None)#

Triggered when the user sends message reactions (XEP-0444).

Parameters:

  • legacy_msg_id (str) – ID of the message the user reacts to

  • emojis (list[str]) – Unicode characters representing reactions to the message legacy_msg_id. An empty string means “no reaction”, ie, remove all reactions if any were present before

  • c (Recipient) – Contact or MUC the reaction refers to

async retract(c, legacy_msg_id, thread=None)#

Triggered when the user retracts (XEP-0424) a message.

Parameters:

  • legacy_msg_id (str) – Legacy ID of the retracted message

  • c (Recipient) – The contact this retraction refers to

async search(form_values)#

Triggered when the user uses Jabber Search (XEP-0055) on the component

Form values is a dict in which keys are defined in BaseGateway.SEARCH_FIELDS

Parameters:

form_values (dict[str, str]) – search query, defined for a specific plugin by overriding in BaseGateway.SEARCH_FIELDS

Returns:

Return type:

slidge.SearchResult