Slidge 2022-11-16 XMPP gateway framework in python en Python Linux Nicoco complete 2.11.0 0.1.0 complete 2.5rc3 0.1.0 partial 1.34.5 No creation, admin or invites (yet) complete 1.3.0 0.1.0 complete 1.19.0 0.1.0 Basic PEP support for contact "puppet" JIDs, to provide nicknames, avatars and vcards complete 1.5 0.1.0 To display http uploads inline partial For stickers from XMPP to the legacy network complete 2.4 0.1.0 To comply with XEP-0100, but it's not sufficient for most gateways (2FA for instance) complete 1.1 0.1.1 complete 1.1.4 0.1.0 When available, legacy contacts use XEP-0084 for their avatars. Slidge also supports synchronizing the slidge user's legacy avatar with their XMPP avatar. complete 2.1 0.1.0 planned partial 1.0 0.1.0 Friend request flow not yet implemented, and slidge always acts as a bouncer complete 1.1.1 0.1.0 To map legacy contacts to JID local parts when necessary planned Will implement if it makes sense for one slidge's plugins planned Will implement if it makes sense for one slidge's plugins complete 1.6.0 0.1.0 So that legacy contacts announce their XMPP caps equivalent when appropriate planned Will implement if it makes sense for one slidge's plugins planned Might be useful to improve the registration process planned For MUC#admin forms 1.0.1 0.1.0 planned User list and delete are available via adhoc commands, but will be improved to follow this XEP partial Only for room avatars partial 1.2.2 0.1.0 Basic support so that legacy contacts have avatars, vcards and nicknames complete 1.1 0.1.0 complete 1.4.0 0.1.0 For services that have no equivalent event, receipts are sent when the legacy service accepts the message. planned Will implement if useful for a plugin planned Will implement if useful for a plugin complete 2.0.1 0.1.0 planned Will implement if useful for a plugin complete 2.0 0.1.0 For group MAM partial 0.1.0 To embed QR codes in data forms during registration via adhoc command planned Will implement if useful for a plugin. MSN nudges (or wizzes) anyone? partial For stickers from XMPP to the legacy network partial 0.1.0 Slidge can send MUC invitations. In the future, it might support incoming-from-xmpp invitations. Compatible with carbons if the server supports it. Even for messages sent from official clients if the component is a privileged entity. complete complete 1.0 0.1.0 Required for XEP-0356. complete 1.2.1 0.1.0 complete 1.0.1 0.1.0 For MUCs partial 0.2.0 0.1.0 complete 1.0.2 0.1.0 complete 0.4 0.1.0 complete 0.3.0 0.1.0 complete 0.4 0.1.0 Used to sync legacy/XMPP rosters and to reflect messages sent from official legacy clients by users. complete 0.6.1 0.1.0 In MUCs. complete 1.1.0 0.1.0 Slidge recognize messages sent from XMPP with HTTP Upload and send them as attachments on the legacy network. For legacy to XMPP attachments, HTTP upload is used by default, but serving attachments from an arbitrary dir is also possible. planned Will implement if useful for a plugin. complete partial Legacy service to XMPP attachments have SIMS metadata when possible. From XMPP to legacy service: basic support (only the source HTTP URI is used, no caption or metadata). 0.3.0alpha0 partial 0.1.0 1.1.3 Plugins can automatically add MUC bookmarks for the user if the component has proper IQ privileges (XEP-0356) complete 0.1.0 1.1.0 complete complete 0.4.1 0.1.0 0.3.0 complete complete 0.1.1 1.6.0 For message replies. planned complete 0.2.0 0.1.0 partial Legacy service to XMPP attachments have SFS metadata when possible. Not supported from XMPP to legacy service complete 0.2.0 complete 0.1.0 Relies on being a privileged entity (XEP-0356), to edit bookmark entries. complete 0.1.0 0.1.0 complete 0.1.0 0.1.0 Slidge supports listening to MDS events and triggering "legacy MDS" events, if added to the PEP MDS node, which is done automatically if XEP-0356 IQ privileges are set. Slidge also support updating MDS node in reaction to "legacy MDS" events. partial 0.1.0 Per client-type setting is not supported. complete 0.1.0