Skip to content
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

Merged
merged 2 commits into from Feb 14, 2016
Merged

Changed the hostname of freenode in the default config #13

merged 2 commits into from Feb 14, 2016

Conversation

ghost
Copy link

@ghost ghost commented Feb 12, 2016

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?

@AlMcKinlay
Copy link
Member

If you are doing that, you should probably change it here, too so we are consistent.

@xPaw
Copy link
Member

xPaw commented Feb 12, 2016

@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.

@AlMcKinlay
Copy link
Member

@xPaw Yeah, good point actually. Just need some checks, and just remove the options.

@astorije
Copy link
Member

I do like having Freenode as a default, actually...
Counter proposal: can we make the change this @YaManicKill suggested and then see in a different issue/PR for what @xPaw is proposing? That would avoid delaying this trivial and needed PR :-)

@xPaw
Copy link
Member

xPaw commented Feb 12, 2016

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.

@astorije
Copy link
Member

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.

@AlMcKinlay
Copy link
Member

Yeah, I agree with @astorije as it's a different issue.

@astorije astorije self-assigned this Feb 13, 2016
@astorije astorije added Type: Bug Issues that report and PRs that solve any defects that cause unexpected behaviors. Type: Feature Tickets that describe a desired feature or PRs that add them to the project. and removed Type: Bug Issues that report and PRs that solve any defects that cause unexpected behaviors. labels Feb 13, 2016
@dgw
Copy link
Contributor

dgw commented Feb 13, 2016

👍 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.

@xPaw
Copy link
Member

xPaw commented Feb 13, 2016

@dgw That's what the config variable is for. It doesn't need to have a hard fallback in the code.

@dgw
Copy link
Contributor

dgw commented Feb 13, 2016

@xPaw This PR is about the config variable…

@xPaw
Copy link
Member

xPaw commented Feb 13, 2016

@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.

@astorije
Copy link
Member

Yes, we all agree @xPaw, but this is really a different issue that deserves a different PR :-)
Let's ship this quickly when @dubzi makes the change, and also consider your proposition after that.

@ghost
Copy link
Author

ghost commented Feb 13, 2016

Alright, I've also fixed the hostname in the client.js file for consistency.

@astorije
Copy link
Member

👍

@xPaw
Copy link
Member

xPaw commented Feb 14, 2016

👍

astorije added a commit that referenced this pull request Feb 14, 2016
Changed the hostname of freenode in the default config
@astorije astorije merged commit 7746629 into thelounge:master Feb 14, 2016
@ghost ghost deleted the fixed_freenode_url branch February 15, 2016 08:17
@astorije astorije added this to the 1.0.2 milestone Apr 1, 2017
brunnre8 pushed a commit to brunnre8/thelounge that referenced this pull request Apr 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature Tickets that describe a desired feature or PRs that add them to the project.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants