| Summary: | [icq/ui] ICQ request authorization is never available | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Thomas Zander <zander> |
| Component: | ICQ and AIM Plugins | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | wstephenson |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Thomas Zander
2005-07-21 14:14:59 UTC
Are you sure that this contact really requires authorization? There are three options to check: 1. Use your icq account's context menu item "Properties"->"Account Preferences" then uncheck "Respect others contacts' wish to require authorization". If that does not help it will not be an auth bug. 2. If you have configured kopete with --enable-debug you would see lines like kopete (oscar - raw protocol): [void Oscar::SSI::checkTLVs()] Need auth for contact xxxxxxxx in the stderr output with xxxxxxxx as your problematic contact's icq number. If not, it will not be an auth bug. 3. Log in via go.icq.com. Make sure that the contact is on your server side contact list at all. If not, it will not be an auth bug but a "contacts are sometimes not added to server side contacts list by kopete" bug. If so, check wether the contact has a grey flower icon. If not, it will not be an auth bug. Using go.icq.com you will see that it is not possibly to request authorization from contacts that do not require it. There is no reason for kopete to enable this menu entry at all times. After investigating your leads I found out its a: "contacts are sometimes not added to server side contacts list by kopete" bug After removing and re-adding the contact I now can request authorization. But I hope you will agree that giving such an explanation to all users is not wanted therefor I suggest to give feedback on why the menu option is not available; as this is far from intuitive IF the contact is not currently shown online. I suggest to show a dialog when no auth can be asked, but user is not showing online where the dialog checks the reason for the off-line-ness. A (re-)add to the server-side-contact-list on "request authorization" would be a nice option in that dialog. Naturally; this implies that the req-auth menu option is available more often then it is now. no offense, but if even simple things like making sure all your contacts are on your server side list don't work, I don't even want to begin to talk about usability or why menu options that users think should be enabled aren't, etc. Contacts requiring authorization will never show as online because we never know what their status is until the contact has authorized us. If contacts are successfully added to the user's contact list on the server, they are then displayed with a red X over the ICQ flower with a tooltip that indicates that they require authorization. Contacts that have given you their authorization don't usually need to be authorized again, unless you move them between groups after they've been authorized, in which case they'll get the flower with the red X (in order to move contacts between groups, they have to be removed from the list and then added in the new group. I'm a bit limited by the protocol here in this scenario). I'm really having a hard time understanding where the problem is. Obviously, if things work correctly when adding contacts, I don't see a problem. Further suggestions/discussion welcome. Moving to wishlist for the moment. I notice when I add a contact, they don't receive an auth request until I manually Request Auth. Is that by design or should the server generate an auth request on add? This should be fixed probably already in Kopete from KDE 4.1, we automatically popup authorization request dialog for user if added contact requires authorization. |