After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 136828 - Support for password protected group chats
Support for password protected group chats
Status: RESOLVED FIXED
Product: gossip
Classification: Deprecated
Component: General
unspecified
Other Linux
: Normal normal
: 0.11
Assigned To: Gossip Maintainers
Gossip Maintainers
: 355929 (view as bug list)
Depends on: 157841
Blocks:
 
 
Reported: 2004-03-11 00:02 UTC by Henrik Engman
Modified: 2007-08-12 22:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Henrik Engman 2004-03-11 00:02:33 UTC
It would be nice with password support for chat rooms.
Comment 1 Martyn Russell 2006-01-18 12:18:11 UTC
Moving from 0.7 to 0.11 target milestone.
Comment 2 Martyn Russell 2006-09-14 09:38:20 UTC
*** Bug 355929 has been marked as a duplicate of this bug. ***
Comment 3 Enver ALTIN 2006-09-14 10:10:58 UTC
If not anyone is working on this, I think I can spend a couple days sometime next week to try to get the feature implemented. Martyn told me that Xavier Claessens said that he's willing to work on this.
Comment 4 Stephen Fromm 2007-03-07 19:06:59 UTC
Are there plans to implement this sometime in the near future?  While I really like gossip, the inability to log into password protected group chats makes it difficult to use in my environment.
Comment 5 Stephen Fromm 2007-03-26 21:54:18 UTC
Minor update:  I edited $HOME/.gnome2/Gossip/chatrooms.xml to add the required password for the chatroom I am unable to join.  It looks like:  <chatrooms><chatroom>...<password>foo</password>...</chatroom></chatrooms>.  After restarting gossip, I am still unable to join.

Please let me know if additional information would be useful.
Comment 6 Martyn Russell 2007-08-12 22:43:38 UTC
I implemented this this weekend.
I also spent a lot of time with the browse feature so it works a lot better and has the option to present more information to make it possible to see things like:
 - is the room locked
 - how many people are in the room
 - the room description

I also updated the Jabber backend code to be more MUC compliant and fixed a few bugs along the way.

According to the spec, chatrooms that are created are only temporary and have to be set up, you are supposed to reply to the server with "give me an instant room with all the defaults" or "give me a reserved room". With the reserved room, the server replies with a form for information to fill out, like should we lock the room, etc. For now we just send that information for the user, we don't ask. To improve this, we could make this more configurable.