slidge.plugins.telegram.gateway
#
Module Contents#
Classes#
Abstract base class to implement gateway commands (chatbot and ad-hoc) |
|
Abstract base class to implement gateway commands (chatbot and ad-hoc) |
|
Must be subclassed by a plugin to set up various aspects of the XMPP |
Functions#
Attributes#
- slidge.plugins.telegram.gateway.REGISTRATION_INSTRUCTIONS = Multiline-String[source]#
Show Value
"""You need to create a telegram account in an official telegram client. Then you can enter your phone number here, and you will receive a confirmation code in the official telegram client. You can uninstall the telegram client after this if you want."""
- class slidge.plugins.telegram.gateway.ListSessions(xmpp)[source]#
Bases:
SessionCommandMixin
,slidge.core.command.Command
Abstract base class to implement gateway commands (chatbot and ad-hoc)
- Parameters:
xmpp (slidge.core.gateway.BaseGateway) –
- class slidge.plugins.telegram.gateway.TerminateSession(xmpp)[source]#
Bases:
SessionCommandMixin
,slidge.core.command.Command
Abstract base class to implement gateway commands (chatbot and ad-hoc)
- Parameters:
xmpp (slidge.core.gateway.BaseGateway) –
- async step2(form_values, session, _ifrom, tg_sessions)[source]#
- Parameters:
tg_sessions (list[aiotdlib.api.Session]) –
- async static finish(session, _ifrom, session_i)[source]#
- Parameters:
session (slidge.plugins.telegram.session.Session) –
session_i (int) –
- class slidge.plugins.telegram.gateway.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
orBaseSession
as the.xmpp
attribute. Since it inherits fromslixmpp.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.
- 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 theBaseGateway.REGISTRATION_FIELDS
iterable
- async validate_two_factor_code(user, code)[source]#
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 needcode (str) – The code they entered, either via “chatbot” message or adhoc command
- async unregister(user)[source]#
Optionally override this if you need to clean additional stuff after a user has been removed from the permanent user_store.
You may need to manually logout the legacy session in here,
Session.logout()
will not be called automatically.- Parameters:
user (slidge.GatewayUser) –