Some nice smaller bug fixes.

cross-posted from: https://slrpnk.net/post/208832 > But a module for Prosody is also in the works.

Hopefully the Tauri based desktop version gets updated soon.

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.

A nice TUI client for XMPP.

cross-posted from: https://community.xmpp.net/post/49428 > 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)

cross-posted from: https://community.xmpp.net/post/34677 > For the last few years we've accepted patches on both GitHub and Sourcehut and used Sourcehut for our CI system. We have tried to move entirely to Sourcehut in the past but it ended up [not meeting our needs](https://codeberg.org/mellium/xmpp/issues/51), and we've tried starting our own co-op code hosting, but were not able to find many cooperators who wanted to help (if you'd like to join us and cooperatively host a Gitea instance, [reach out](https://blog.samwhited.com/about/)!). We have been experimenting with mirroring a few of the main repos on Codeberg and using their experimental CI feature, and this has been going much smoother and has been much simpler than the current SourceHut integration. > > With all this in mind, we've decided that the time is right to move to [Codeberg](https://codeberg.org/). > > For the time being we will continue to accept pull requests for the main project and a few of the support libraries over on GitHub, and we will keep the main projects CI running on Sourcehut as well as on the new Codeberg CI so that both Codeberg and GitHub based PRs can show the status. However, smaller support libraries that do not receive contributions often will be moved entirely to Codeberg and PRs on GitHub will be automatically closed. > > Eventually, once we are certain everything is working smoothly, the old GitHub repos will be retired and become mirrors on which we do not accept contributions and all Sourcehut repos will be deleted. There is no timeline for this currently. If you would like to keep track of the timeline once we have one, or submit comments or suggestions you can track the issue https://mellium.im/issue/304 > > Some repos are still being moved, but the main project is now on Codeberg and ready to accept contributions. To track the overall migration, see https://mellium.im/issue/301 > > Thanks for your continued support and contributions!

Context: I'm using a 1GB server to run all my apps; Email server, Peertube, Pleroma. I feel like a psychopath but it's all running well with a swap file to keep things from killing itself with OOM. Basically it has to be lightweight. It doesn't have to be easy to set up, just the software has to be future proof and runs on low resources. Thanks in advance...

Releases for poezio 0.14, slixmpp 1.8.2, poezio-omemo 0.6.0 and slixmpp-omemo 0.7.0!

cross-posted from: https://community.xmpp.net/post/25 > As a user, what kind of protection do you expect? Who/What are you trying to protect against? > > What implementation (client/server/something else?) allows you to do this? What would be missing?

cross-posted from: https://community.xmpp.net/post/227 > The [budget to implement OMEMO](https://opencollective.com/mellium/projects/omemo) has just reached $100 USD! If you'd like to work on OMEMO encryption in Mellium, you can reach out on our [chat](https://mellium.chat/). We should decide as a community if we want to allocate this as a bounty, or provide other resources like servers to test with and the like!

conversations.im 

Looks like they're funding the service through custom domain xmpp hosting: > We have decided to make conversations.im accounts free of charge. We think this will help the adoption of XMPP in general and Conversations in particular. Our domain hosting will continue to act as a source of revenue for our service. > > We hope you continue to enjoy conversations.im.

I heard in dino you could do that https://fosstodon.org/@dino/107787204408646020 I don't have anyone to test it, but I'm guessing it'll work as said. how about between apps like conversations, gajim and dino? on each app pages the features aren't clear whether it does these things. --- also, for security reasons i'm thinking of when xmpp will implement something like totp.

This website is gathering protocol and UI recommendations for developing XMPP clients that have user experiences that chat users expect in 2022. The source code for the website is on GitHub

Quoting from the article: --- The [openEngiadina project](https://openengiadina.net) is developing a platform for open local knowledge. With regard to technology, this has so far consisted of: - Research into a suitable data model: - How to use RDF for various types of data (including ActivityStreams for social interactions) - How to make RDF content-addressable - A scheme for robust content-addressing - How to cryptographically sign content-addressed content - How to use CRDTs for mutability (this work has been continued as part of the DREAM project) - Development of a client for creating and curating content: GeoPub - Development of a server capable of handling of such diverse types of content: CPub [..] Over the last couple of months we have been exploring XMPP as an alternative to ActivityPub and are happy to announce an initial proof-of-concept version of GeoPub - the openEngiadina client - using XMPP. You can try it [here](https://geopub.openengiadina.net/) (an XMPP account is required). The source code is available on [Codeberg](https://codeberg.org/openengiadina/geopub/).

I believe that XMPP is one of the best protocols for chat communications there is, and I stand up for it. However, the clients that there are, are not comfortable for most people out there used to apps like Telegram, Whatsapp or whatever. One can defend current XMPP clients saying that quoting with "> " is the traditional way, or that swiping to quote a message is not worth developing; I have plenty more examples like this. Well, if you think so, OK, use those clients for yourself, but become aware that many people won't use XMPP for just this reason. After saying all this, I want to tell that **I am willing to develop a new, modern looking and _comfortable_ client for XMPP**. I think of a client for Android in first instance, but I would have no problem on going further. However, I don't know programming, so **I'm searching programmers** who would like to get involved in this. Although I'm not programmer, I have experience developing software projects, from internationalization to documentation, including ideas about features, testing and all other work there can be. > Will you help me spreading the word? :)

I explored the settings for conversations, since I was looking to prevent media, like pictures, videos and such, from being placed under gallery, since that's what conversations is doing. Unfortunately I didn't find any setting for that, not even under the expert settings, :(

A site to help newcomers more easily onboard to XMPP.. Along the lines of joinmastodon or joinpeertube