Gajim - 2024-04-13

ok i give up i tried to google the grammar rule for apostrophes

is is "Encryption not available in private chats" or "Encryption not available in private chat`s"

First

because its not about possesion?

Because of my feeling. Ignore me :D

...

i think also the first

apostrophe s should only used for possessive nouns, and i think chats is here used simply as a plural

lovetox pushed 1 commits to branch gajim/master cfix: MessageActionsBox: Disable encryption in private chats - https://dev.gajim.org/gajim/gajim/-/commit/9ef7c61a9335fea66e2ff6a313893296c4c3fd08

I totally forgot, that I can drag and drop pinned conversations to put them in preferred order. Nice!

> because its not about possesion? far from my field of expertise, but I don't see any need to denote possession, so, 1st option gets my 👍️

> is is > "Encryption not available in private chats" or > "Encryption not available in private chat`s" native speaker here, it's the first

wurstsalat pushed 1 commits to branch gajim/master imprv: Change 'Topic' to 'Subject' in group chat details - https://dev.gajim.org/gajim/gajim/-/commit/c0ead52ce909da16cc93efee71014d0ea453af39

Hi all !!

just want to know when Gajim 1.8.5 will be released ?

The usual amswer is: when it's ready

> just want to know when Gajim 1.8.5 will be released ? you can always build from src ↺

I would like to have a marker that shows me in my chats up to which point I last read. Can this be realised?

donnerwetter, this is planned, but no due date ;)

cal0pteryx, That makes me happy - even if there is no date yet. Do I remember correctly that this function existed in an earlier version?

in group chat, yes, I think so. but then the whole chat display mechanism was redesigned

Then I'll be patient. Patience is not exactly one of my strengths.

Heh. I didn't expect to see !982 merged. Sorry I never got back to the questions on it. After lovetox questioned me on it, I recognized that I actually preferred topic over subject. The XEP mentions both and makes no recommendation for one over the other. I brought it up in XSF chat and didn't get any recommendation.

Maybe I'll do a MR later to switch to topic.

please dont without good arguments why

we have always had subject in most part of Gajim

it needs some serious arguments why we should change that

haha

is this out of a desire to not upset people who are used to seeing subject?

well, we know that either "will work", so I question if any argument, no matter how thorough, could be convincing

I know that when I looked at the etymology and definition senses in wiktionary, topic was my pick

It would also mine, but i think history of having it that way weighs more here

its kind of subjective

one argument that could convince me is, if other clients in the xmpp world also use topic

but as cal0pteryx investigated, they are also not consistent

Looks like someone has to lead the way with settling this indecision for everyone ;)

https://docs.modernxmpp.org/terminology/

I see no mention of topic or subject on that page. It seems to be an unresolved question.

That's where this should go in the end was what I meant

shameless self-advertisement: in case you need a TLSA records updater for your BIND and certbot-based certificates: https://gitea.ksol.io/karolyi/daneupdate

something i'm curious about: when I need to delete OMEMO fingerprints and send a message to reestablish a session between two devices for them to be able to decrypt an OMEO message (this is my memory of what I was told, could be faulty), it's not obvious this will fix it or that it's where the problem is. has there ever been any thought to have some kind of more direct key management in the UI?

(if it's a matter of time or resources that's of course fine, just wondered if it was that or a specific choice that the authors intend to maintain)

this is a workaround, normally Gajim could discover itself that encryption does not work anymore and do the dance with creating a new session

i dont think it makes sense to involve the user more

I almost feel direct control over sessions would be easier because it does directly communicate what's wrong

But fair enough, thank you for the answer

it makes not much sense to me to tell a user to click some buttons, which the application can do itself

a user should only be involved if there is a decision to be made

lovetox pushed 2 commits to branch gajim/master refactor: Chatstate: Split groupchat and chat states - https://dev.gajim.org/gajim/gajim/-/commit/b61df63fb0609a3a5e4db2bd6f57e3c75d557717 ci: Add black config - https://dev.gajim.org/gajim/gajim/-/commit/dd2b7404bc9bc07e07ac8db4a7582957d7e982b2