Opened 11 years ago

Last modified 11 years ago

#6267 new enhancement

Menu item for changing chat topics

Reported by: foxmajik Owned by: deryni
Milestone: Component: pidgin (gtk)
Version: 2.4.3 Keywords: xmpp, chat, topic
Cc:

Description

When using xmpp chat there doesn't seem to be any way to set the topic. Or, maybe the servers I'm using don't support setting the topic. Either way, there's no option for it in the menu and there's nothing about it in the documentation even though version version 0.11.0-pre13 release notes (06/06/2001) indicate "Can view/set chat topic in Jabber (thanks faceprint)." If it's server dependent the feature should be there but indicate to the user that it's not supported because the server doesn't support it. If it's not server dependent the the option is just missing from the menus in the xmpp chat window.

Change History (9)

comment:1 Changed 11 years ago by ffdragon2

Have you tried just double clicking on the topic at the top of the chat?

That being said, maybe there should be a link like (change topic) at the end of the topic so more people can find it?

comment:2 follow-up: Changed 11 years ago by foxmajik

I don't understand why there can't be a menu option for it (ie Conversation --> Set Topic)..?

Also, I can't imagine anyone intuitively figuring out that double-clicking on the topic would make one able to change it, especially if there is no topic already set.

comment:3 in reply to: ↑ 2 Changed 11 years ago by chemistrydioxide

Replying to foxmajik:

Also, I can't imagine anyone intuitively figuring out that double-clicking on the topic would make one able to change it, especially if there is no topic already set.

I agree with you.

If someone knows about this, it's no problem. But if someone doesn't it's really not intuitive.

comment:4 Changed 11 years ago by rekkanoryo

  • Component changed from XMPP to pidgin (gtk)
  • Owner nwalp deleted
  • Summary changed from No intuitive way to change chat topic to Menu item for changing chat topics

There is also the /topic command that can be used in the chat (/help will show you all the commands that apply to the conversation you use it in).

I'm changing the component on this from XMPP to Pidgin because we don't have a menu item for this for any protocol that I'm aware of, and if we were to add one, we'd want to add it on all protocols where chats support topics.

comment:5 Changed 11 years ago by foxmajik

Additionally there's no feedback when changing the topic isn't supported. You can double-click and type text and press enter, but nothing happens. It should tell you "setting topic not supported by server" at least and ideally not offer the option in the first place if it's not supported.

comment:6 Changed 11 years ago by foxmajik

...or if you can't set the topic because you're not authorized it should tell you that.

comment:7 Changed 11 years ago by deryni

The problem, as far as I see it, with adding a Conversation->Set Topic menu item is that it opens the door to a flood of "I need a menu item for this chat room feature" requests, some of which are guaranteed to be protocol specific, permission specific, etc. which is going to cause some general annoyance. I do think we need a better way to do chatroom specific stuff but I think a better place than the Conversation menu is needed (even just a dedicated menu would be fine).

Depending on the protocol there may or may not be a way to tell that setting the topic isn't supported for a given chatroom before you try to set it (or query for that specifically). I am surprised that we don't display an error when you try to set the topic and cannot successfully do so. What protocol did you try that on?

comment:8 Changed 11 years ago by foxmajik

The problem, as far as I see it, with adding a Conversation->Set Topic

menu item is that it opens the door to a flood of "I need a menu item for this chat room feature" requests, some of which are guaranteed to be protocol specific, permission specific, etc. which is going to cause some general annoyance.

If you're able to predict that these features will be in demand why not address all of the feature requests with one code change? Denying acknowledgment of the issue only propagates the bug in future versions.

If there's no way to tell whether or not a feature is supported the interface should indicate this to the user by attempting to implement it when requested and then displaying some feedback if the attempt fails, rather than providing the feature but having it silently fail, or omitting it altogether because it might not work -- this would be easy to do with the topic by simply trying to set it, then seeing if it exists. If the topic doesn't exist after you try to set it, tell the user they can't do that (Error: The feature is not supported by the server you're using for chat), then disable the feature.

comment:9 Changed 11 years ago by deryni

  • Owner set to deryni

I can't predict which features will be in specific demand, I'm likely not even aware of what all the possible features are (except for 'standard' IRC rooms and XMPP non-extended rooms). My issue was not a desire not to implement the change but a desire not to implement a single option and pretend that we covered all the bases. Because while nothing is implemented we can say "that class of things isn't supported at the moment" whereas we lose the ability to say that when some of the class of things are supported.

Again the issue is knowing what features are even theoretically possible for a given protocol let alone what is reasonably possible or administratively allowed. And yes, as I said before silently failing is not acceptable. Which is why I expressed surprise at that claim and asked you to indicate which protocol you saw that happen for. (Something I will note you failed to do.)

No, setting the topic and then attempting to read it is not the solution. Any protocol worth a damn will return success or failure for a topic change request and it is that to which we should be responding (and again I profess surprise to learn that this is not the case).

I just tested this in an xmpp chat room and we do indeed simply drop the error response on the floor, I believe the fix for that is simple and will attempt to fix it when I next sit down to work on pidgin. Thank you for the report.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!