# Ircnow

## Server locations

| Location          | Hostname             |
| ----------------- | -------------------- |
| Las Vegas, USA    | irc.lecturify.net    |
| Las Vegas, USA    | irc.inspirenet.org   |
| Las Vegas, USA    | irc.shelltalk.net    |
|                   |                      |
| New York, USA     | irc.ircforever.org   |
| New York, USA     | irc.bsdforall.org    |
| New York, USA     | irc.nastycode.com    |
| New York, USA     | irc.planetofnix.com  |
|                   |                      |
| Roost, Luxembourg | irc.oddprotocol.org  |
| Roost, Luxembourg | irc.thunderirc.net   |
| Roost, Luxembourg | irc.freeirc.org      |
|                   |                      |
| Miami, USA        | cloud9p.org          |
| Miami, USA        | irc.ircnow.org       |
| Miami, USA        | irc.rpblc.net        |


## Yonles' plan

[plan](https://yonle.lecturify.net/ircnow_ngircd_links_plan.txt)  
[diagram](https://yonle.lecturify.net/ircnow_ngircd_links_plan_2.png)


## IanJs' plan

Everyone, except for irc.ircnow.org, irc.bsdforall.org,
irc.planetofnix.com and irc.lecturify.net, create a group containing:

 - irc.bsdforall.org
 - irc.planetofnix.com
 - irc.lecturify.net

Talk to the admins of those systems to create peerings with them, if
you don't have them already.

To create a peer you need to add a section like the following to your
ngircd.conf:

	[Server]
		Name = irc.planetofnix.com
		Host = irc.planetofnix.com
		Bind = <your_ip_address> 
		Port = 16697
		MyPassword = <shared_token> 
		PeerPassword = <shared_token> 
		Group = 001
		;Passive = no 
		SSLConnect = true
		;ServiceMask = *Serv,Global

I wasn't sure how to best to suggest irc.ircnow.org,
irc.bsdforall.org, irc.planetofnix.com and irc.lecturify.net arrange
their peerings between themselves.  However, this arrangement means
noone is more than 2 hops from irc.ircnow.org.


## IRC discussion

    #team 2023-05-19
    10:47 < Yonle> https://yonle.lecturify.net/ircnow_ngircd_links_plan.txt
    11:47 < IanJ> Well, I had a plan but Yonle has decided he has an alternative plan...
    11:48 < IanJ> So now I'm waiting on feedback from the ngircd developer to see what he thinks of
                  Yonles' plan.
    12:11 <@izzyb> I posted this on the wiki earlier
    12:11 <@izzyb> https://wiki.ircnow.org/index.php?n=Ngircd.Ircnow
    12:13 <@izzyb> was thinking it makes sense for each team to be in a local group with its neighbors in the same region
    12:13 <@izzyb> and for each region to be in a group
    12:14 <@izzyb> so then we'd have 4 groups of 3
    12:15 <@izzyb> I'll add Yonle's link to the wiki page
    12:15 <@izzyb> IanJ: I didn't see your plan. did you post it someplace?
    12:17 < Error> lol
    12:17 < Error> IanJ
    12:18 < Error> what you wanted to do!
    12:18 < Error> not that i would understand it all!
    12:20 < IanJ> I was going to ask some folks to change their peerings to try and flatten the ircnow irc network a bit.
    12:21 < IanJ> Try to reduce the effects of the netsplits when a server goes down or has a problem.
    12:21 <@izzyb> yeah I agree, question is what the best configuration
    12:21 < IanJ> At the moment some servers are connected in a big long chain, several hops from ircnow.org and if any server in that chain goes down, any of them stacked up behind it are split too.
    12:22 <@izzyb> https://wiki.ircnow.org/index.php?n=Ngircd.Ircnow
    12:22 < IanJ> Lets see what the ngircd guys say, if Yonle's design is a go then I'm willing to give it a try. It's got to be better than what's happening at the moment.
    12:26 <@izzyb> Yonle: how did you choose the groupings in your plan?
    12:28 <@izzyb> IanJ: how about your plan? what groupings did you use?
    12:29 <@izzyb> Perhaps we should start with a list of the groupings we currenly have?
    12:29 <@izzyb> I'll publish my current configuration on the wiki page
    

## Current Configurations

### planetofnix.com

Group 003 - Active  - irc.ircnow.org, irc.rpblc.net, irc.freeirc.org  
Group 004 - Passive - irc.shell.oddprotocol.org, irc.inspirenet.org,
irc.nastycode.com, irc.ircforever.org, irc.oddprotocol.org


### nastycode.com

Group 001 - Active  - irc.bsdforall.org, irc.lecturify.net,
irc.planetofnix.com   
Group 004 - Passive - irc.oddprotocol.org, irc.ircforever.org, 
irc.shelltalk.net, irc.ircnow.org, irc.inspirenet.org


### ircnow.org

Group 127 - Active  - irc.bsdforall.org   
Group   1 - Passive - irc.inspirenet.org   
Group   9 - Passive - irc.rpblc.net   
Group 127 - Passive - irc.planetofnix.com   
Group   ? - Passive - services.irc.ircnow.org, irc.thunderirc.net, 
irc.lecturify.net, irc.NaStYcOdE.com


### lecturify.net

Group 001 - Active  - irc.ircnow.org, irc.inspirenet.org  
Group 001 - Passive - irc.shell.oddprotocol.org, irc.nastycode.com  
Group   ? - Passive - lbot.host.lecturify.net  


### thunderirc.net

Group 003 - Active  - irc.ircnow.org, irc.jujube.ircnow.org  
Group   ? - Active  - irc.shelltalk.net  
Group   5 - Active  - irc.staff.thunderirc.net  
Group   ? - Passive - irc.cherry.ircnow.org  
Group   ? - Passive - irc.orange.ircnow.org


### bsdforall.org

Group 002 - Active  - irc.ircnow.org, irc.rpblc.net  
Group   1 - Active  - irc.freeirc.org, irc.NaStYcOdE.com,
irc.shelltalk.net  
Group   1 - Passive - irc.shell.oddprotocol.org,
irc.oddprotocol.org  


### oddprotocol.org

Group 001 - Active  - irc.inspirenet.org, irc.bsdforall.org,
irc.rpblc.net   
Group 003 - Passive - irc.ircforever.org, irc.nastycode.com, 
irc.lecturify.net, irc.shell.oddprotocol.org, irc.planetofnix.com 


## jujube.rpblc.net

Group 001 - Active  - irc.inspirenet.org, irc.freeirc.org,
irc.thunderirc.net, irc.shelltalk.net, irc.shell.oddprotocol.org,
irc.oddprotocol.org, irc.rpblc.net


**NOTE:** Passive peerings allow the peer to connect to you but you
will not initiate a connection to them.