`slidge.plugins.skype`#

Module Contents#

Classes#

`Gateway`	Must be subclassed by a plugin to set up various aspects of the XMPP
`Contact`	This class centralizes actions in relation to a specific legacy contact.
`ListenThread`	A class that represents a thread of control.
`Roster`	Virtual roster of a gateway user, that allows to represent all
`Session`	Represents a gateway user logged in to the legacy network and performing actions.

Functions#

handle_thread_exception(args)

Attributes#

`Recipient`
`log`

class slidge.plugins.skype.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 skype credentials'[source]#

REGISTRATION_FIELDS[source]#

ROSTER_GROUP = 'Skype'[source]#

COMPONENT_NAME = 'Skype (slidge)'[source]#

COMPONENT_TYPE = 'skype'[source]#

COMPONENT_AVATAR = 'https://logodownload.org/wp-content/uploads/2017/05/skype-logo-1-1-2048x2048.png'[source]#

async validate(user_jid, registration_form)[source]#

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:

user_jid (slixmpp.JID) – JID of the user that has just registered
registration_form (dict[str, Optional[str]]) – A dict where keys are the FormField.var attributes of the BaseGateway.REGISTRATION_FIELDS iterable

class slidge.plugins.skype.Contact(session, legacy_id, jid_username)[source]#

Bases: slidge.LegacyContact[str]

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.core.session.BaseSession) – The session this contact is part of
legacy_id (slidge.util.types.LegacyUserIdType) – 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

session: Session[source]#

update_presence(status)[source]#

Parameters:: status (skpy.SkypeUtils.Status) –

update_mood(mood)[source]#

Parameters:: mood (skpy.SkypeContact.Mood) –

async update_info(contact=None)[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”.

Parameters:: contact (Optional[skpy.SkypeContact]) –

class slidge.plugins.skype.ListenThread(session, *a, **kw)[source]#

Bases: threading.Thread

A class that represents a thread of control.

This class can be safely subclassed in a limited fashion. There are two ways to specify the activity: by passing a callable object to the constructor, or by overriding the run() method in a subclass.

This constructor should always be called with keyword arguments. Arguments are:

group should be None; reserved for future extension when a ThreadGroup class is implemented.

target is the callable object to be invoked by the run() method. Defaults to None, meaning nothing is called.

name is the thread name. By default, a unique name is constructed of the form “Thread-N” where N is a small decimal number.

args is the argument tuple for the target invocation. Defaults to ().

kwargs is a dictionary of keyword arguments for the target invocation. Defaults to {}.

If a subclass overrides the constructor, it must make sure to invoke the base class constructor (Thread.__init__()) before doing anything else to the thread.

Parameters:: session (Session) –

skype_blocking()[source]#

stop()[source]#

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

Bases: slidge.LegacyRoster

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: Session[source]#

async fill()[source]#

Populate slidge’s “virtual roster”.

Override this and in it, await self.by_legacy_id(contact_id) for the every legacy contacts of the user for which you’d like to set an avatar, nickname, vcard…

Await Contact.add_to_roster() in here to add the contact to the user’s XMPP roster.

slidge.plugins.skype.Recipient[source]#

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

Bases: slidge.BaseSession[int, 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.

skype_token_path: pathlib.Path[source]#

sk: skpy.Skype[source]#

shutdown()[source]#

async login()[source]#

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 on_skype_event(event)[source]#

Parameters:: event (skpy.SkypeEvent) –

async send_text(chat, text, **k)[source]#

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

async logout()[source]#

Logout the gateway user from the legacy network.

Called on user unregistration and gateway shutdown.

async send_file(chat, url, http_response, **kwargs)[source]#

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

Parameters:

url (str) – URL of the file
chat (Recipient) – See BaseSession.send_text()
http_response – The HTTP GET response object on the URL
reply_to_msg_id – See BaseSession.send_text()
reply_to_fallback_text – See BaseSession.send_text()
reply_to – See BaseSession.send_text()
thread –

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)[source]#

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)[source]#

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

Parameters:: c (Recipient) –

async composing(c, thread=None)[source]#

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

Parameters:: c (Recipient) –

async paused(c, thread=None)[source]#

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)[source]#

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:

legacy_msg_id (int) – Identifier of the message, passed to slidge.LegacyContact.send_text() or slidge.LegacyContact.send_file()
c (Recipient) –

async correct(c, text, legacy_msg_id, thread=None)[source]#

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 (Any) –
c (Recipient) –

async retract(c, legacy_msg_id, thread=None)[source]#

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

Parameters:

legacy_msg_id (Any) – Legacy ID of the retracted message
c (Recipient) – The contact this retraction refers to

async search(form_values)[source]#

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:

get_msg(legacy_msg_id, contact)[source]#

Parameters:

legacy_msg_id (int) –
contact (Recipient) –

Return type:

skpy.SkypeTextMsg

slidge.plugins.skype.handle_thread_exception(args)[source]#

Parameters:: args (threading.ExceptHookArgs) –

slidge.plugins.skype.log[source]#

slidge.plugins.skype#

Module Contents#

Classes#

Functions#

Attributes#

`slidge.plugins.skype`#