Gajim - 2024-01-23

> This is disappointing because only Movim supports calling on Windows. I know there is an unofficial version of Dino for Windows, but Gajim is a fully featured client so this is really disappointing. im sure the devs would accept PRs to fix calling

there is a merge request with a fix but it's waiting on upstream fixes being merged

it kind of seems like nothing will come of it

> Why do you use FreeBSD? Have been using it since ~2000. It was more complete (the documentation was stella), than the two Linux distros I tried (I think it was Red Hat and Slackaware, I preferred the latter), and installed in seconds compared to the two Linux distros. I also tried SCO Unix. But I stuck with FreeBSD, I also had a book that the install CDs came with. I also liked the self-management structure of FreeBSD over Linux, however there a still problems, like a lack of transparency, in-group behaviour, silent treatments, and just the out-right enabling of weaponising open-source to kill children in Asia and Africa. The Ports system is also just amazing, and easy to add new Ports too. ✏ ↺

cal0pteryx, lovetox, I want to restore XEP-0174: Link-Local Messaging for Gajim.

Would you kindly guide or help me in doing so? ✏

No sorry

Would you accept patches from me, to restore XEP 0174? ✏

Would you accept patches from me, to restore XEP-0174? ✏

sch While link-local messaging is a cool feature, I wonder, if it still fits in nowadays Jabber landscape. Gajim cannot (yet) provide PEP and without PEP things such as OMEMO (or OX) do not work. I'm not saying, that there are no use-cases for it, but it is certainly less useful than it was ten+ years ago.

debacle, I think that it is very useful, and it would be even more useful when more client would support it.

lovetox The user with the python3-sentry-sdk problem just told me, that the problem exists with older versions, too. If there are no objections from your side, I will patch out the use of python3-sentry-sdk in the Debian package to avoid similar problems in the future.

debacle: that would significantly reduce bug reports for gajim. Lets investigate first

cal0pteryx See https://bugs.debian.org/1061281

cal0pteryx Unfortunately, the user sent their newer messages only to me, not to the bug report. But it boils down to: If python3-sentry-sdk is installed (no matter if old version 1.9.x or new version 1.39.y), Gajim crashes. I did not yet check myself. ✏

debacle, if, for instance, Croc, LocalSend and Sharik will support XEP-0174 and XEP-0234 (was XEP-0096), that would make Link-Local more useful. It would also make XMPP more relevant. It would also give to people who use XMPP more confidence in XMPP. https://github.com/schollz/croc/issues/556 https://github.com/localsend/localsend/issues/344 https://github.com/marchellodev/sharik/issues/183

Croc, LocalSend and Sharik are software that intend to share files via LAN, and it appears that non adopts a standard to do so, which, as you might know better than myself, is like having GaduGadu, ICQ, MSN all over again, and this is another reason for the importance of adopting Link-Local in Gajim, Psi etc. ✏

I also love to have Avahi-powered telecom in a private and closed network, without the need for an XMPP server. It is private, simple and fun!

sch: you underestimate the work and overestimate the user benefit regarding gajim

How so? Please elaborate.

Gajim's link local implementation has been removed since it was way too much effort to maintain it. It broke gajim in various ways. Just "patching it in" won't work

What would make it to work then?

By work, do you mean it would increase effort in an unproportionate manner, or wont actually work?

I'm willing to attempt to re-implement it, in accord with your terms.

Yes, this would increase maintenance effort. Also, guiding others to implement features costs time (a lot). And I personally think this feature would no be beneficial for Gajim.

So I won't invest time

Is it *possible* to implement a plugin?

a plugin would be interesting

Is it at all feasible to restore this functionality with the Gajim plugin system? ✏

As an idea,what about enabling xmpp developers in general by standard xmpp libs that any client can just import?

There could even be a reference lib in language X ported to Y,Z,W

debacle, seems it is a problem with a dependency of sentry-sdk

the error happens in the trio package

debacle, here is the bug report https://github.com/python-trio/trio/issues/2848

lovetox Thanks. Somehow the description of the potential fix sounds scary: "Just delay select.epoll to fix import after gevent monkey patching"

yeah reads all bad, it seems gevent monkey patches something at run time

and trio fails because of that

not sure why only one user is seeing that it seems the user has some lib installed which is optional and this triggers the problem

i dont think this is a general problem for all users

lovetox No, for sure! I know a lot of people using Gajim directly from Debian in all variants, and they would complain about a crash.

i guess you have to decide for yourself as package maintainer what to do here, as the bug is not in Gajim.

lovetox Yes. First thing is, to reassign the Debian bug to the python-trio package. Second, as long as there is no other way, I need to patch out the import of sentry until the trio bug is fixed.

could you not simply *not* recommend sentry?

or is not recommended?

instead of patching Gajim ..

its a optional dependency .. simply remove it from the package until fixed?

ah .. but users have it still installed ..

lovetox ATM, it is recommended and I will remove the Recommends. But it can still crash, if the user has the package for other reasons.

meh

Maybe I add a wild hack with a environment variable: "GAJIM_LOAD_SENTRY_CRASH_RISK" — if it set, it loads the library, if not, it is not imported.

Let's see. So far, only one user complained and he could just remove sentry and is happy now.

If no other users are affected, I can just wait for trio to be fixed.

And I can downgrade sentry from Recommends to Suggests, which means, it will not installed automatically any longer.

nah wait

i have a better fix

i push a fix, so it will not fail visibly for the user anymore

then you dont need to change anything with packages, and once trio is fixed, it will resolve itself

I think that menu item `Add contact...` should be under menu `Gajim` instead of menu `Account`.

I think that a new menu item (available as a button inside Account dialog) `Add Account...` may be added to menu `Accounts`.

press the big + button in the chat list

to add a contact

no need for menu

lovetox, there *is* a menu, under menu Accounts.

I disagree. A menu is useful for those of us who prefer keyboard over cursor, and Gajim is an XMPP clients that is used by many types of people. ✏

Just made a ticket to support calling on Windows: https://dev.gajim.org/gajim/gajim/-/issues/11746

speedygonzales99: There is a merge request to get calls to work at https://dev.gajim.org/gajim/gajim/-/merge_requests/995 . It's had a recent update so let's hope this gets merged eventually.

lovetox If you have a fix, just send me the commit (hash) — or make a new release ;-)

debacle ^ https://dev.gajim.org/gajim/gajim/-/commit/c4bf2a689c2fb2e6d5f5ac4f7b22a5c4ac9e3dd5

lovetox, Thanks!

fjklp: hopefully, that PR gets merged and can add support for Windows 🤞️

read markers/receipts' "has read up to this point" message is supposed to contain a nickname right?

nope

we only show that in single chat, so i see no use in displaying the nick