Summary: | Can't subscribe to services on many Jabber servers | ||
---|---|---|---|
Product: | [Unmaintained] kopete | Reporter: | Stefan Borggraefe <Stefan.Borggraefe> |
Component: | Jabber Plugin | Assignee: | Kopete Developers <kopete-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Stefan Borggraefe
2006-05-22 10:56:29 UTC
I guess it is because many serices do not support registering and browsing. For service to browse, you need it to have sub-items (or capability to have sub-items). If it does not have that capability, how can you browse it? Similary with register. There are other things that can be done with a service: join (if it is MUC service) or search. But there are also services which do not support any user interaction, an example can be proxy.netlab.cz. This one can be picked up by client and help with file transfer, so it must be listed there, but it makes no sense to register there or something. It is not 'incompatible with Kopete', it means they can not be registered. I would be against greying the services out myself, since it could lead to thinking they are turned off. However, proxy service may not be dead and not react to any usual way of interaction. Shouldn't most of the services listed on jabber.ccc.de and amessage.de support registering (e.g. the transports to other IM networks)? I can register to the ICQ transport on jabber.ccc.de with Psi, but not with Kopete (I'm using an SVN build updated and compiled today).
> I would be against greying the services out myself, since it could lead to
> thinking they are turned off. However, proxy service may not be dead and not
> react to any usual way of interaction.
If there are different reasons why the buttons are greyed out, maybe it would be better not to grey out the list items and to add an explanatory sentence below the list that changes depending on which service is currently selected. Tooltips for the list items would be another (less discoverable) option.
The current UI leaves the user clueless as to why he can't do anything with some of the listed services. Something should be done here to improve the UI.
If they are transports and you can register them with psi, then yes, it is probably a bug and they should not be greyd out in the first place. I can confirm that this is a bug, I use polish server (chrome.pl and jabber.autocom.pl) and I can register using PSI but not using latest SVN Kopete. Speaking about transpotrs for me they never appear online (I mean transports and conntacts using transports), in PSI they are online and I can talk to them, using kopete it works but all contacts are shown offline, don't know if it is a bug. Marking NEW (see comment 4) and changing summary to reflect the findings. To me, each service that have the register button grayed doesn't tell me this is possible. Also, i have updated the svn to use the new disco protocol before the old service protocol. Have a try. (Note: neither jabber.ccc.de nor jabber.autocom.pl does even reply to the <iq/>) Olivier: I just tested this again with the current 0.12 SVN and there is no change regarding this bug. :-( jabber.ccc.de, jabber.autocom.pl and amessage.de still have the "Register" button greyed out for most services. I did't try more Jabber servers. Service that are not enabled probably does not allow to register, or there is a problem in the server. * amessage.de : works fine here, the register button works for both icq and users. (it is not possible to register to a conference service, you must use join groupchat for that) * jabber.ccc.de : some services doesn't reply to discovery#info, that mean there is a problem on the server, or that the admin intentionally blocked them. but gg and aspsms have the register button. * jabber.autocom.pl : each services that allow registration are not grayed. Which service is not working exactly, which is working in psi ? I recompiled today to pick up the patches from bug 129059. With this build it is possible to subscribe to far more services again. I couldn't find a service where the button behaviour in the Service dialog was wrong anymore. Perhaps MUC services shouldn't be displayed in this dialog when there is a specific UI for this kind of service. But this has nothing to do with this bug. Seems to me like this bug can be marked fixed (or marked as aduplicate of bug 129059). :-) The bug 129059 has nothing to do with that. My guess is it is with my previous commit (revision 550982) I asked you to test in my comment #6 Probably your svn was not uptodate when you tested. |