Do you like #bicycles or #cycling? Do you also use an #xmpp compatible chat service? Join our new group chat at [firstname.lastname@example.org](xmpp:email@example.com?join). Hopefully this can become a fun community space to share pictures, post routes, and generally chat about bicycles.
This release fixes RFC 3920 session building ([#3468](https://lab.louiz.org/poezio/slixmpp/-/issues/3468)), improves certificate errors handling, and adds an XEP-0454 (OMEMO Media Sharing) plugin.
The python cryptography package is required to use the XEP-0454 plugin.
There is a fundraiser (money managed by the XSF, the project and developers aren't related though) to add history support to the Matrix/XMPP bridge Bifrost, check it out, and possibly throw them a few bucks if you're frequently bridging to Matrix rooms!
Someone mentioned that they don't have a good place to post releases for a community that's not on this instance. Maybe we should make this default group a more general group? It can still be for discussion about the instance too (or we can have a separate /c/meta if we think people won't want them together). What do others think? (the sidebar already says this is for general discussion, so this is really about whether we should rename it and/or split the group in two)
Over on /r/xmpp they get a lot of questions about how to configure a server and what not, so I decided to make a home for those sorts of questions here when the community isn't on Lemmy over at /c/support.
Would anyone like to design an icon or possibly a header banner for /c/support community? It would be nice to spruce things up a bit!
If someone creates a community for their XMPP project, that should obviously be allowed. But what about tangentially related technologies or XMPP-focused general discussion communities? Eg. would an IETF KITTEN Working Group community be disallowed because it's not specific to XMPP (not that they're likely to create a group, I was just trying to think of something tangentially related)? What about a group to discuss XMPP Security or XMPP UX that's not specifically tied to a project or group? It may be worth us developing a policy on this early on to stop conflicts before they arise and to stop having to grandfather in to many groups if we decide later that they're out of scope.