Kaidan issueshttps://invent.kde.org/network/kaidan/-/issues2020-09-20T15:10:37Zhttps://invent.kde.org/network/kaidan/-/issues/258Public MIX/MUC search2020-09-20T15:10:37ZBhushan ShahPublic MIX/MUC searchThis site contains a list with most of the public MUCs. It were nice if you could search that list in Kaidan:
https://muclumbus.jabbercat.org/
The problem would be that (the JID or IP-Address) and the search requests are sent to a 3rd p...This site contains a list with most of the public MUCs. It were nice if you could search that list in Kaidan:
https://muclumbus.jabbercat.org/
The problem would be that (the JID or IP-Address) and the search requests are sent to a 3rd party service. The solution would be to either sync the whole list or hosting an own instance (but that would still only partially solve the problem).2.0https://invent.kde.org/network/kaidan/-/issues/266Support UBports Push Notification Server2022-09-11T22:54:42ZBhushan ShahSupport UBports Push Notification ServerRumors have it that XMPP servers can be told to send Notifications to a Push Notification Servers, but only using the XMPP protocol. So adding Push Notifications for Kaidan in Ubuntu Touch would need:
* [ ] A XMPP Push Gateway to transl...Rumors have it that XMPP servers can be told to send Notifications to a Push Notification Servers, but only using the XMPP protocol. So adding Push Notifications for Kaidan in Ubuntu Touch would need:
* [ ] A XMPP Push Gateway to translate XMPP to whatever the UBports Push Notification Server accepts (probably on UBports side)
* [ ] Kaidan click package version tells its XMPP server to send Notifications to the new UBports XMPP Push Gateway
* [ ] Kaidan implements a push helper to handle the push notifications (as a reference see [Telegram](https://github.com/ubports/telegram-app/tree/master/telegram/push) or [Fluffy Chat](https://github.com/ChristianPauly/fluffychat/blob/1d968cd7a27cf69f28180bd02d5aea5b95b20fd3/helloHelper))2.0https://invent.kde.org/network/kaidan/-/issues/306System tray icon2022-01-09T15:00:53ZÖyvind SætherSystem tray iconMost communications programs have system tray icon support. This is specially handy for users of multiple virtual desktops. Other similar programs such as Kopete, Spectacle and Pidgin have system tray icon support. Some (just me?) view i...Most communications programs have system tray icon support. This is specially handy for users of multiple virtual desktops. Other similar programs such as Kopete, Spectacle and Pidgin have system tray icon support. Some (just me?) view it as a essential feature for a chat application. Please consider adding system tray icon support. Do be aware that it would have to be optional as that foot desktop environment does not have a system tray. All other desktop environments (KDE/LXQt/Xfce/IceWM/Fluxbox) support a system tray icon.2.0https://invent.kde.org/network/kaidan/-/issues/323XEP-0157: Contact Addresses for XMPP Services2023-12-10T13:02:31ZLinus JahnXEP-0157: Contact Addresses for XMPP Serviceshttps://xmpp.org/extensions/xep-0157.html
The contact addresses should be visible after registering and also in the account settings.
(Suggestion by @borgert)https://xmpp.org/extensions/xep-0157.html
The contact addresses should be visible after registering and also in the account settings.
(Suggestion by @borgert)2.0https://invent.kde.org/network/kaidan/-/issues/326Multi-account support2022-09-30T19:14:56ZAl DeMulti-account supportCurrently you can only use a single account. If you want to use a second one, you either have to use a different app or to log out and log in with another.
However it would be very convenient to use two or more simultaneously, for differ...Currently you can only use a single account. If you want to use a second one, you either have to use a different app or to log out and log in with another.
However it would be very convenient to use two or more simultaneously, for different purposes, like for work and private communication or even testing purposes.2.0Melvin Keskinmelvo@olomono.deMelvin Keskinmelvo@olomono.dehttps://invent.kde.org/network/kaidan/-/issues/334Add possibility to resize the contact's panel in width2020-09-20T14:45:46ZAl DeAdd possibility to resize the contact's panel in widthIf a contact's name is very long or all are very short a fixed width of the panel either makes the name elide or simply wastes spaces.If a contact's name is very long or all are very short a fixed width of the panel either makes the name elide or simply wastes spaces.2.0https://invent.kde.org/network/kaidan/-/issues/362Token-based authentication2023-03-06T13:00:07ZLinus JahnToken-based authentication### The issues with password-based auth
Using a password is not that nice:
* You can't identify your devices -> you can't list logged in devices
* You can't kick/log out other devices
* The user needs to remember the password somehow...### The issues with password-based auth
Using a password is not that nice:
* You can't identify your devices -> you can't list logged in devices
* You can't kick/log out other devices
* The user needs to remember the password somehow or the password needs to be visible in the App.
* Remembering the password isn't always a good option: Many people forget the password and get locked out of their account.
* Making the password visible isn't a good idea either, others getting your phone in their hands can easily look at your password -- This is not very privacy-aware.
* -> You could use randomly generated passwords to avoid privacy-loss. However, you can never be sure that the password of an account is randomly generated.
* When the password is changed, all other devices need to log in again.
### Requirements for such a token-based auth
* Devices using password-based authentication and devices using token-based auth need to work in parallel with one account.
* All currently active tokens need to be visible to clients
* Maybe privileges for tokens
* A client only having access using token-based auth should be able to give access to another device.
* Generating a new temporary token for the device
* Changing the accounts password and transmitting that
* Time limitations
* devices that are offline for more than e.g. 90 days should be kicked
* devices renew or replace their token by logging in or a special command
### Solutions?
To solve this, we probably need changes to the standards / a new XEP. Possible solutions:
* OAUTH2?
* There's already something for OAUTH in XMPP
* Is listing devices/tokens possible? => Do we need a XEP for that?
* There was a proto XEP about tokens?
* Could that be an option?
---
UPDATE: Solution seems to be FAST with SASL 2 (https://xmpp.org/extensions/inbox/xep-fast.html, https://xmpp.org/extensions/xep-0388.html)2.0https://invent.kde.org/network/kaidan/-/issues/364Show avatars in notifications2020-09-20T14:54:06ZRobert MaerkischShow avatars in notifications2.0