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!

Massive update!

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...

the short version was that it was an up-and-coming federated protocol, with people working on clients and stuff, and trying to attract users. then everyone got really excited when Google decided to start using XMPP in their Google Talk product, because it would mean instant adoption by a ton of people! except now everyone just used Google Talk as their client, because it was ahead of the existing XMPP clients in terms of usability/UX, and UX work on other clients kinda died. but over time, Google being Google, they got distracted and started neglecting Google Talk, failing to enable TLS support while the rest of the XMPP ecosystem started making it mandatory, essentially cutting off all Google Talk users from the rest of the XMPP network. so now you had a Google Talk network that everyone was using with a decent-ish client, and an XMPP network that a bunch of people were using with clients that sucked, and they couldn't talk, and all the momentum in developing a strong stand-alone network was lost due to people letting Google control the whole thing Over the years, open-source has kinda turned from "let's build a public commons" into "let's do free work for big corporations" and it's... not a good change, to say the least

Just got a bigger update, starting to look really quite nice! Edit: got it to work on my server. Not quite there yet in terms of functionality, but promising.

Changes: - Support OMEMO in private MUCs - Minimum iOS version is now 14.0 - Communication Notifications on iOS 15 - New improved and simplified notification appex - Switched to new newer libsignal-protocol-c version - Fixing some memory leaks - Fixes muc invites - Improve OMEMO e2ee - Reduce avatar image size to ~60kb to make ejabberd throttling happy - Support muc muting again and implement "mention only" notification mode for mucs - Fix voice messages from conversations - Allow deletion of history for one contact - Add autodeletion of messages after 3 days (default: off) - Update timeouts to make Monal work even under very bad/slow network conditions - Add support for xmpp: invites (https://docs.modernxmpp.org/client/invites/) - Use bigger iq timeouts to account for throttling by xmpp servers (like ejabberd) - Remove all old VoIP code (was not working anymore) - Prevent spurious "could not sync" errors in multi account setups - Use less memory on incoming stanza flood (only parse ~100 stanzas at once) - Fix error in message deduplication (some messages could be received twice)

Crossgeposted von: https://lemmy.ml/post/233120 > Replaces the Zhabogram one.

Some of the ranking is a bit questionable, but it is mainly meant for in-app selection.

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

Basically allows you to receive emails on your XMPP address. Seems quite useful for notification and sign-up emails etc.