Linking to vbirc network
this information is for network administrators
- Introduction
- We are always looking to grown our network by adding additional servers to the pool.
- We are looking for experienced with irc admins who want to support our network.
- This can be a leaf or alternative hub ircd.
- You have to be serious about linking, we're looking for long term commitment.
- Exception: Your own domain is possible, if you have a popular and active channel.
- Adding a LEAF IRCD
- - Dedicated IP, preferably reverse resolve (no dynamic host).
- - 24/7/365 online server (no home hosting solutions).
- - 10/100/1000Mbit connection up/down.
- - 512 or 1024 connections (or more, but not less).
- - Will be <something>.vbirc.com|net|org (can't be your domain).
- - Crontab
- - Unlimited Bandwidth.
- - Local Operator
- - Paying Server 3,6,12 months ahead.
- - No slots for additional Opers.
- Adding a HUB IRCD
- - VPS/Dedicated solution only.
- - Reverse Resolve required.
- - 24/7/365 online server (no home hosting solutions).
- - 100/1000Mbit connection up/down.
- - 1024 connections (or more, but not less).
- - Share Shell with Network Owners (Floris|Chroder) for Management.
- - Will be <something>.vbirc.com|net|org (can't be your domain).
- - Crontab.
- - Unlimited Bandwidth.
- - Global Operator.
- - Paying Server 6 or 12 months ahead.
- - 1 slot for additional Oper.
Merging with vbirc network
this information is for network administrators
- Introduction
- We are always looking to expand our network by adding additional networks to the pool.
- We are looking for experienced with irc admins who want to support our network.
- This can be one or more hubs with leafs connected to them.
- You have to be serious about linking, we're looking for long term commitment.
- Exception: Your own domain is possible, if you have an already well established popular and active network.
- Merging an existing network
- - Hubs and Leafs have to 75% be eligible as per above info.
- - Hubs will become alt hubs that connect to our hubs.
- - Leafs will remain leafs below their hubs.
- - Hubs and Leafs can keep their existing name structure.
- - But preferred to be renamed to *.vbirc.* name structure. (optional)
- - Hub owners will be Global Operators. Leaf owners will be Local Operators.
- - Realize that Your network merges with Ours, and adapt network name: vbirc
- - Name structure showing under /map (not hiding)
- - Your services (anope/denora/neostats) will be merged with ours and discontinued
- - Your network will adapt to our network rules. Specific rules can be merged.
- - If nicknames and/or channels are duplicate, biggest network gets priority.
- - Any web site and service, will be merged under vbirc.com (with appropiate access) and discontinued (forwarded)