Difference between revisions of "LizardIRC-JDNet network merge/Finalization"
From LizardWiki, FastLizard4's wiki and website
Jasper Deng (Talk | contribs) (start this document, not final yet) |
Jasper Deng (Talk | contribs) (→Technical: add) |
||
| Line 5: | Line 5: | ||
*There will be only one set of IRC services with a services database merged from both networks. If you had an account on both, your records will be merged into a single account. | *There will be only one set of IRC services with a services database merged from both networks. If you had an account on both, your records will be merged into a single account. | ||
*The IRCd will be basically the same. However, servers will be renamed: | *The IRCd will be basically the same. However, servers will be renamed: | ||
| − | **LizardIRC servers ridley and phazon will be renamed to diamond and emerald, respectively. | + | **LizardIRC servers ridley and phazon will be renamed to diamond and emerald, respectively. As with the JDNet domains, the old ridley and phazon domains will be deprecated but maintained as CNAME's to the new server names. |
**JDNet servers sfo, hwan, and ruby will be renamed to jasper, sapphire, and ruby, respectively (yes, ruby will not be renamed). | **JDNet servers sfo, hwan, and ruby will be renamed to jasper, sapphire, and ruby, respectively (yes, ruby will not be renamed). | ||
**The base second-level domain name for all of the new names will be lizardirc.org. The recommended method of connecting will remain using irc.lizardirc.org. | **The base second-level domain name for all of the new names will be lizardirc.org. The recommended method of connecting will remain using irc.lizardirc.org. | ||
*This may seem obvious but you will no longer need to maintain connections to two networks at once. Modify your client's autoconnect settings accordingly. | *This may seem obvious but you will no longer need to maintain connections to two networks at once. Modify your client's autoconnect settings accordingly. | ||
| + | |||
==Social== | ==Social== | ||
*You will meet new people! Although a significant number of users use both networks, others do not. | *You will meet new people! Although a significant number of users use both networks, others do not. | ||
Revision as of 23:58, 16 July 2015
This subpage describes what network users can expect after the LizardIRC-JDNet network merge. All questions should be directed to the talk page, or #networkmerge on LizardIRC.
Technical
Configure your IRC client appropriately.
- The JDNet domain names will be CNAME'd to the appropriate LizardIRC domain names and will be deprecated; they will be maintained for backwards compatibility only.
- There will be only one set of IRC services with a services database merged from both networks. If you had an account on both, your records will be merged into a single account.
- The IRCd will be basically the same. However, servers will be renamed:
- LizardIRC servers ridley and phazon will be renamed to diamond and emerald, respectively. As with the JDNet domains, the old ridley and phazon domains will be deprecated but maintained as CNAME's to the new server names.
- JDNet servers sfo, hwan, and ruby will be renamed to jasper, sapphire, and ruby, respectively (yes, ruby will not be renamed).
- The base second-level domain name for all of the new names will be lizardirc.org. The recommended method of connecting will remain using irc.lizardirc.org.
- This may seem obvious but you will no longer need to maintain connections to two networks at once. Modify your client's autoconnect settings accordingly.
Social
- You will meet new people! Although a significant number of users use both networks, others do not.
- Everyone will be subject to LizardIRC rules, which are somewhat more restrictive than JDNet rules but still very common sense.
- JDNet users only: if your cloak on JDNet does not comply with LizardIRC's vhost policy, it will be prefixed with JDNet/. For example, if your vhost were example, your new vhost is JDNet/example. You may avoid this prefixing by requesting a LizardIRC-compliant vhost in advance of the merge.
- You will find new channels.
- All current network staff members from both networks will form the new (combined) network's staff team.
- #JDNet will be merged into #lizardirc and redirected there.
