UX: Join channel requires `#` symbol
oxr463 opened this issue · comments
Steps:
- Create Server, e.g., OFTC.
- Join channel
- Enter
openwrt
Actual:
I was expecting to be added to the #openwrt
channel. It created a new tab under the server, but I wasn't actually connected to a real channel.
Desired:
Either automatically prepend the #
for each channel, or parse and verify that one has been added so that the user can successfully join a channel.
Screenshots:
First attempt openwrt
.
Second attempt #openwrt
Great app, by the way!
I would instead prefer that /join
nick
opens a chat window with that user, without needing to specify any initial message.
I know there's a technical difference in the background: joining a channel requires sending a message to the server, but opening a private message tab does not. However it should be simple enough to check whether a nick or channel is given, and to proceed accordingly.
If this needs to have a different name, please don't hard-code it as /query
; that has to be the most hateful contortion of the English language among the many bizarre malapropisms that litter the entire history of IRC. I love IRC as an community, but its terminology is just plain broken, to the point of being really very annoying.
Indeed, I would like to see all the various /
commands moved into user-editable table, by expanding the "command aliases" and adding the various specialized methods (such as QUIT
, PART
, & JOIN
) as options alongside Message
, Client command
and Raw
. And have the ability to remove the default ones.
I'm already used to /query
for that, contortion or not :( It probably helps that I'm not a native English speaker.
Another option for that would be to use /msg nick
without arguments; I think that would make sense since /msg
opens private chats.
I think binding /join foo
to opening a conversation with nick foo
instead of joining channel #foo
might be confusing, specially since some desktop IRC clients already do the latter (what @oxr463 expected).
Having /msg #chan
open the window but not send an empty message would be acceptable. I think /msg
would also be a good candidate for "switch to existing window" for both privmsgs and channels.
However I'd really like to see all the command names be configurable, not just message aliases, because otherwise some users will complain that /query
doesn't work. I don't mind if it exists, I just don't want to be forced to use it.