-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Channelname collisions #10
Comments
This commit adds automatic conversion of outgoing messages from irc-style highlighting (e.g. "nick:") to discord's "<@id>" format. New "mention_suffix" option is added. Outgoing mentions currently won't work with names containing spaces, but it should be fine once issue #10 is fixed. Fixes: issue #9.
I'd very much like all my channels prefixed with a Server name to help keep things organized. Though it might be nicer if it just included the first 3 characters of the server, to keep them shortish still |
Another somewhat interesting solution to this problem would be to have the plugin generate dummy channels with the server names to separate server channels instead of making the channel names long. |
That makes perfect sense, I wonder why I never thought of this. 418a7c7 adds the |
When channel names on multiple servers coincide bitlbee will add "_" suffixes to the name until it is unique, which doesn't help to see which one is which.
A possible solution to this is to add an option that will change channel naming convention to #servername.channelname for all channels.
Reported by: @Kays in #5
The text was updated successfully, but these errors were encountered: