-
Notifications
You must be signed in to change notification settings - Fork 703
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
Changed the hostname of freenode in the default config #13
Conversation
If you are doing that, you should probably change it here, too so we are consistent. |
@YaManicKill I think that default in the code should go away, and the server should just refuse to open a connection if there is no host specified. |
@xPaw Yeah, good point actually. Just need some checks, and just remove the options. |
I do like having Freenode as a default, actually... |
It would stay in the config file, it doesn't need to be in code itself. |
Right, I see, and nothing in the config file if the admin wants no default. Still, I prefer this in a different PR as it needs a bit more testing/checks than what @dubzi offers here. |
Yeah, I agree with @astorije as it's a different issue. |
👍 Keeping freenode in is good, IMO. I've seen a lot of clients start off with their project channel/network in the default settings so new users are immediately directed to where they can get help. |
@dgw That's what the config variable is for. It doesn't need to have a hard fallback in the code. |
@xPaw This PR is about the config variable… |
@dgw I know, keeping freenode in the config default is fine. But here: https://github.com/erming/shout/blob/35587f3c35d0a8ac78a2495934ff9eaa8f1aa71c/src/client.js#L128 it needs to be removed, and the connection must be refused if there is no server specified. |
Alright, I've also fixed the hostname in the client.js file for consistency. |
👍 |
👍 |
Changed the hostname of freenode in the default config
fix lounge commands in PMs
As suggested in erming/shout#647 the default freenode hostname is not correct. Yes, it works, but Freenode suggests to use chat.freenode.net instead.
It's a super easy fix, so why not?