Hi all, It's been over a year and the folks hosting the XMPP Lemmy experiment at community.xmpp.net have asked us to start transitioning it to our own hosting. I'm writing to see what the community would like to do, or if anyone wants to take over hosting? The instance was never very widely used, so I think we can probably shut it down safely as well without too much loss. What do you think?

Slidge is a xmpp server bridge to many closed networks, e.g WhatsApp signal Telegram. It is in a very early stage and very actively developed. Progress is getting better and better, for me currently one of the most important XMPP projects

But a module for Prosody is also in the works.

Still early days, but slowly it is getting somewhere.

Still early days, but this client shows much promise.

cross-posted from: https://slrpnk.net/post/116191 > Finally a good Matrix home server 😅

cross-posted from: https://slrpnk.net/post/116464 > Unlike the electron version it uses the system browser and it thus quite lightweight. It also includes a proxy to use via normal 5222 port instead of direct websockets.

Do you like #bicycles or #cycling? Do you also use an #xmpp compatible chat service? Join our new group chat at [bicycles@conference.samwhited.com](xmpp:bicycles@conference.samwhited.com?join). Hopefully this can become a fun community space to share pictures, post routes, and generally chat about bicycles. [Join us!](xmpp:bicycles@conference.samwhited.com?join)

A new initiative from the folks at jmp.chat creates a fediverse compatible hosting solution that eventually aims to integrate with XMPP!

The OMEMO dev's push to get many clients to drop OTR support has seriously fragmented the XMPP world :( It seems like there *must* be a modern client that supports both OTR and OMEMO, but, I haven't found one.

Hello guys!\ Thank you very much for having accepted my request here.\ I am a Lawyer (you can find some information about me here https://notes.nicfab.it/en/pages/about/), passionate about XMPP and something else 😀\ I approached XMPP by using Snikket.\ Ah, btw, I am the one who translates in Italian the XMPP newsletter 😀

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.

cross-posted from: https://lemmy.ml/post/241674 > Just switched from using Matrix to XMPP (for several reasons). I'm using the Conversations app ATM, but was curious as to what apps you guys use/prefer as well! > > (I'm gonna miss Fluffychat, but ditching Matrix seems like the best move from what I've recently read.)

What are your thoughts on Lemmy so far? I'd love to know how people feel about it; what could be improved; etc.

Join us in a new community space dedicated to accessibility concerns in clients and the network more broadly! We hope to see you there.

Hi all, there was a wave of spam this evening so I’ve temporarily required moderator approval to create a new account or community. If this causes any issues, please let me know. Thanks!

Oops, hi again all; I am just learning to administer a Lemmy instance and accidentally deleted all my posts. Not to worry though, feel free to re-introduce yourself here, and welcome to lemmy!

Everyone go upvote!

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!

Each community can appoint its own moderators and make its own separate decisions about what sort of content is allowed, but we should also likely think about an instance wide way of determining what sorts of content are and are not allowed and how moderation decisions are made. It's not a problem yet, but I figure it can't hurt to go ahead and get feedback from the community about what sorts of communities have good or bad moderation practices that we can emulate. What do others think?

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.