Find all needed information about Pidgin Xep Support. Below you can see links where you can find everything you want to know about Pidgin Xep Support.
https://developer.pidgin.im/wiki/SupportedXEPs
XEP-0092: Software Version : Draft XEP-0095: Stream Initiation : Draft XEP-0096: SI File Transfer : Draft (SOCKS5 bytestreams, IBB) XEP-0100: Gateway Interaction : Active : minimal support in Pidgin/Finch? XEP-0107: User Mood : Draft XEP-0115: Entity Capabilities : Draft : v1.5 since 2.6.0 XEP-0118: User Tune : Draft XEP-0124: Bidirectional ...
https://developer.pidgin.im/ticket/4509
The invisibility support that pidgin will accept (and which I hope to eventually have time to implement) will be that specified by XEP-0186 (unless that is retracted or superseded by the time I get to it). You are free to try the snippets provided by that XEP in the XMPP Console, but realize that your server may not support it.
https://developer.pidgin.im/ticket/16801
support in the client for XEP-0163 (Personal Eventing Protocol), which is already in Pidgin according to the wiki. The main advantage of OMEMO over OTR is that it works in multi-user chats, and between multiple devices/clients when combined with support for XEP-0280 Message Carbons #15508 and XEP-0313 Message Archive Management #15653.
https://developer.pidgin.im/ticket/15653
Pidgin doesn't have any sql storage support and that limits whole xep-0313 idea. MAM support is currently just a basic hack, it load messages from timestamp of last received/sent message on connection to server, don't distinguish between already received messages and new messages, can't request history from conferences, can't load messages on user request (with scrollback for example) and so on.
https://developer.pidgin.im/ticket/15508
The XEP's status is still Experimental, so I don't think Pidgin will add it yet, but it's good to have the code exist, in my opinion. UIs will still need to be updated to support it: I think many of them don't properly handle PURPLE_MESSAGE_SEND.
https://www.pidgin.im/plugins/
This page contains a list of plugins from trusted authors and the community. If you believe a plugin should be on this list, please get in touch with us or open a pull request with the update.
https://developer.pidgin.im/ticket/5811
I'd really need Pidgin to support this. Essentially it means that chat history is (automatically) stored in XMPP server, and is also retrievable from the server. In essence I'd like to have plugin in Pidgin that does this retrieving automatically and shows the information just like the "normal" history plugin (history.so) does...
https://developer.pidgin.im/ticket/9015
Further, how can Pidgin force all the xmpp servers to support XEP-0199? I don't see any other xmpp client except Pidgin forcing this requirement on the server. I feel Pidgin must provide a way to disable these pings in case server doesn't support xep 0199.
It can support many more with plugins. Pidgin supports many features of these chat networks, such as file transfers, away messages, buddy icons, custom smileys, and typing notifications.
https://developer.pidgin.im/wiki/SupportedXEPs
XEP-0092: Software Version : Draft XEP-0095: Stream Initiation : Draft XEP-0096: SI File Transfer : Draft (SOCKS5 bytestreams, IBB) XEP-0100: Gateway Interaction : Active : minimal support in Pidgin/Finch? XEP-0107: User Mood : Draft XEP-0115: Entity Capabilities : Draft : v1.5 since 2.6.0 XEP-0118: User Tune : Draft XEP-0124: Bidirectional ...
https://developer.pidgin.im/ticket/4509
The invisibility support that pidgin will accept (and which I hope to eventually have time to implement) will be that specified by XEP-0186 (unless that is retracted or superseded by the time I get to it). You are free to try the snippets provided by that XEP in the XMPP Console, but realize that your server may not support it.
https://developer.pidgin.im/ticket/16801
support in the client for XEP-0163 (Personal Eventing Protocol), which is already in Pidgin according to the wiki. The main advantage of OMEMO over OTR is that it works in multi-user chats, and between multiple devices/clients when combined with support for XEP-0280 Message Carbons #15508 and XEP-0313 Message Archive Management #15653.
https://developer.pidgin.im/ticket/15653
Pidgin doesn't have any sql storage support and that limits whole xep-0313 idea. MAM support is currently just a basic hack, it load messages from timestamp of last received/sent message on connection to server, don't distinguish between already received messages and new messages, can't request history from conferences, can't load messages on user request (with scrollback for example) and so on.
https://www.pidgin.im/plugins/
This page contains a list of plugins from trusted authors and the community. If you believe a plugin should be on this list, please get in touch with us or open a pull request with the update.
https://developer.pidgin.im/ticket/15508
The XEP's status is still Experimental, so I don't think Pidgin will add it yet, but it's good to have the code exist, in my opinion. UIs will still need to be updated to support it: I think many of them don't properly handle PURPLE_MESSAGE_SEND.
https://developer.pidgin.im/ticket/5811
I'd really need Pidgin to support this. Essentially it means that chat history is (automatically) stored in XMPP server, and is also retrievable from the server. In essence I'd like to have plugin in Pidgin that does this retrieving automatically and shows the information just like the "normal" history plugin (history.so) does...
https://developer.pidgin.im/ticket/9015
Further, how can Pidgin force all the xmpp servers to support XEP-0199? I don't see any other xmpp client except Pidgin forcing this requirement on the server. I feel Pidgin must provide a way to disable these pings in case server doesn't support xep 0199.
https://xmpp.org/extensions/xep-0313.html
XEP-0313: Message Archive Management. ... Support for 'off the record' chats (OTR; not to be confused with the encryption algorithm of the same name). ... Finally, in order for the client or server to limit the number of results transmitted at a time a server MUST support Result Set Management (XEP-0059) and MUST support the paging mechanism ...
Need to find Pidgin Xep Support information?
To find needed information please read the text beloow. If you need to know more you can click on the links to visit sites with more detailed data.
