As Mageia uses matrix protocol for communication the implemented messengers should support these protocols as well. So please import+backport the matrix protocol for pidgin
https://blog.mageia.org/en/2023/10/02/mageia-is-in-matrix-social-network/
If upstream not recommend the use of the plugin why we must import to mageia? Update 2022/04/11 This project is essentially unmaintained. It may still work for you, in which case good luck to you; however, it lacks many important features that are critical to a modern Matrix client (not least of which is end-to-end encryption support).
That quote came from: https://github.com/matrix-org/purple-matrix/#readme "purple-matrix #purple on matrix.org This project is a plugin for libpurple which adds the ability to communicate with matrix.org homeservers to any libpurple-based clients (such as Pidgin). If you want to bridge the other way, using a matrix client to communicate with any backend supported by libpurple, see matrix-bifröst. Update 2022/04/11 This project is essentially unmaintained. It may still work for you, in which case good luck to you; however, it lacks many important features that are critical to a modern Matrix client (not least of which is end-to-end encryption support). Status This project is somewhat alpha, and only basic functionality has been implemented. Sending and receiving simple text messages is supported, as is joining rooms you are invited to by other users." It has to be admitted that with the discouraging upstream comments, this does not look good to import into Mageia. We currently seem to have: pidgin-plugins, pidgin-2.14.12-2.mga9.src.rpm Pidgin plugins shared by the Purple and Finch pidgin-plugin-pack, pidgin-plugin-pack-2.7.1-0.dev20200305.2.mga9.src.rpm Plugin Pack for libpurple and derived IM clients lib64purple0 is in SRPM pidgin. Not up to us to judge, assigning to all packagers.
Source RPM: (none) => pidgin-2.14.12-2.mga9.src.rpm, pidgin-plugin-pack-2.7.1-0.dev20200305.2.mga9.src.rpmAssignee: bugsquad => pkg-bugs
I use pidgin in daily business and it is established as a multiprotocol client. Sometimes there is the need for a migration, but doing this every time a new protocol was designed, is not the way I want to work.
The last standing distribution which ships this unmaintained plugin is Ubuntu 22.04 LTS ... Fedora removed it in their latest release 38. So no distribution except Ubuntu left...there seems to be a reason for it?
(In reply to Marc Krämer from comment #4) > I use pidgin in daily business and it is established as a multiprotocol > client. Sometimes there is the need for a migration, but doing this every > time a new protocol was designed, is not the way I want to work. I also use pidgin is very useful, but we must accept its limitations, I must use web.telegram.org because I can't make some things in the pidgin plugin that I can do in the webpage (I don't want to install the official client), you can use the matrix webclient if you not want to install other application, but I feel more easy use nheko for that