Summary: | wish: ability to set groupchat room-settings and moderator-functionality | ||
---|---|---|---|
Product: | [Unmaintained] kopete | Reporter: | S. Burmeister <sven.burmeister> |
Component: | Jabber Plugin | Assignee: | Kopete Developers <kopete-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
S. Burmeister
2006-09-03 14:18:49 UTC
This is a duplicate of Bug 63944 (Coccinella, Tkabber and JWChat are some other clients that support this) Bug 63944 is titled: Include full multi user chat (MUC) support. Sounds like a meta-bug, so fair enough, any bug that concerns MUC is a duplicate of it. Yet I am not really sure if this matter should be handled by only one bug. Maybe one could mark bug 63944 as a duplicate of: Include full Jabber support in kopete. ;) *** This bug has been marked as a duplicate of 63944 *** The fact is that we are planing to do that in Kopete. It is not required to leave 100 open report. Kopete doesn't implement MUC at all because libiris we use doesn't implement it. It still implement the old GroupChat 1.0 protocol. But new version of iris implement it, so it will be in Kopete for KDE4 As I often got the messsage: One issue, one report, do not blame me! And 63944 is from 2003 and was not found by any search when entering a new bug. I don't blame you. Thanks you for all your wish and interest in Kopete. "One issue, one report" is indeed often the correct rule. But when several issues have the same solution, we group them, otherwhise, we are lost in thousands of issues. (And btw, this is already the case :-p) Ok, I'll try to take that into consideration when reporting bugs. Would you mind if I ping you in IRC in order to avoid these things and ask before I submit issues? |