XMPP/Jabber
Any guide on how to backup encrypted chats (OMEMO) and keys on android (Conversations) and how to use multiple devices (my phone and linux pc).
codeberg.org
I'm having fun coding [Poxtit](https://codeberg.org/spla/poxtit), a Python code that, thanks to [slixmpp](https://slixmpp.readthedocs.io/en/latest/index.html) Python library, allow post xmpp room messages to Mastodon account, follow fediverse's users and replicate their public posts to any room.
I'm looking for something like FluffyChat, but for XMPP. Modern style, cross platform. Any suggestions?
I'm looking into any linux clients that can also decrypt messages sent and received through cheogram on android. For cross-platform use purpose.
New server list portal for Movim.
Encrypted applications [@session](https://mastodon.social/@session) SESSION [@threemaapp](https://mastodon.social/@threemaapp) THREEMA (paid) [@signalapp](https://mastodon.world/@signalapp) SIGNAL MANYVERSE [@manyver\_se](https://fosstodon.org/@manyver_se) WIRE SAFESWISS (salsa20) TELEGUARD ELEMENT [#matrix](https://mastodon.social/tags/matrix) [@matrix](https://mastodon.matrix.org/@matrix) SPEEK! (p2p) UTOPIA (p2) CONVERSATIONS (xmpp) [@xmpp](https://lemmy.ml/c/xmpp) DELTA CHAT [@delta](https://chaos.social/@delta) PEER'EM MESSENGER (p2p) JAMI BCHAT BRIAR (p2p) [@briar](https://fosstodon.org/@briar) xxMESSENGER (q) STEALTH TALK MESSENGER (paid; tetra-sdnp) TOX SIMPLE X CHAT [@simplex](https://mastodon.social/@simplex) BERTY (p2) STATUS (p2) NOSTR For now just a brief mention, I will talk about it again soon.
FOSDEM video recording now available.
github.com
Some nice smaller bug fixes.
codeberg.org
cross-posted from: https://slrpnk.net/post/208832 > But a module for Prosody is also in the works.
github.com
Hopefully the Tauri based desktop version gets updated soon.
github.com
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.
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)
codeberg.org
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...
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
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?
opencollective.com
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!
mastodon.social
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
XMPP/Jabber
!xmpp@lemmy.mlSince this community was partially inaccessible due to a long standing bug in Lemmy, we moved to a new XMPP community here instead: !xmpp@slrpnk.net
XMPP/Jabber is the community-owned standard for real-time federated messaging.