Gajim - 2024-08-13

No devices found to encrypt this message. Searching for devices… ???

what's the problem?

omemo

how to solve?

gajim will not encrypt a message to yourself, so if no one else is in the chat, gajim says this when you try to send a message

it *will* send the message if you have another client using the same account

like while there is no interlocutor online I can't write to him? before I could just update everything gajim and here's the story

i dont know if this is an issue with gajim specifically but i think MAM has ceased to function entirely for me

in all of my MUCs there are huge holes in message history

mcneb10: Gajim has a sync threshold setting (in days) for public channels. But AFAIK it syncs all the messages it can get from private groups and 1-to-1 chats

its not syncing at all for me

assuming im not misunderstanding how it works, it should sync all messages within the last day on startup if its set to "1 day"

it does not sync any new messages at all

> assuming im not misunderstanding how it works, it should sync all messages within the last day on startup if its set to "1 day" Yes

mcneb10: See accounts -> account -> Server Info -> Features and make sure that XEP-313: Message Archive Management has a green tick next to it.

https://share.themcgovern.net:5281/file_share/LXKDQF9iqimydaSgUx1klyKf/0bb89e33-06fe-4456-aee1-0a1b03bcb6e0.png

i self host my own prosody

it was working fine before

does it work with other clients?

seemingly movim only?

probably not a gajim issue

> seemingly movim only? Are there other clients that you tested that didn't work? ↺

dino

monal

Then the issue may indeed be with your server.

Check that you have some free storage

perhaps run `sudo prosodyctl check` and / or try restarting prosody.

how do i test if its working

Join a new channel e.g. xmpp:prosody@conference.prosody.im?join and see if you get history Though I'm not sure if mam for MUCs is handled by your server or the MUC component hosting the channel.

But since your issue is with mam for MUCs, try it anyway.

> Though I'm not sure if mam for MUCs is handled by your server or the MUC component hosting the channel. It's probably the latter BTW, ~so your issue may have been in s2s connections.~ ✏

> fjklp: I wanted to ask if you would be interested in learning how to checkout merge requests via git and test things before they are merged. This involves some preparation though ;) cal0pteryx: I guess this would go like 1. `git clone https://dev.gajim.org/wurstsalat/gajim.git` 3. `git checkout contact-details-name-modified` ✏ ↺

> fjklp: I wanted to ask if you would be interested in learning how to checkout merge requests via git and test things before they are merged. This involves some preparation though ;) cal0pteryx: I guess this would go like 1. `git clone https://dev.gajim.org/wurstsalat/gajim.git` 2. `./scripts/dev_env.sh` 3. `git checkout contact-details-name-modified` ✏ ↺

> fjklp: I wanted to ask if you would be interested in learning how to checkout merge requests via git and test things before they are merged. This involves some preparation though ;) cal0pteryx: I guess this would go like 1. `git clone https://dev.gajim.org/wurstsalat/gajim.git` 2. `./scripts/dev_env.sh` 3. `git checkout contact-details-name-modified` 4. `./launch.py` ✏ ↺

I don't know this venv stuff

fjklp: dev_env.sh automatically creates a venv for you. Generally I would clone the main repo and then add forks as additional remotes, in order to checkout branches of forks. What's missing is creating an additional profile for testing purposes, so you don't break your main database for example

With `./launch.py -p test` for example

This is a good start https://dev.gajim.org/gajim/gajim/-/wikis/development/IWantToStartHacking

venv is great.