Started by DJ Omnimaga, September 18, 2017, 06:52:59 pm
0 Members and 1 Guest are viewing this topic.
QuoteUPDATED on September 18th 2017#CodeWalrus IRC channel is available on the EFnet IRC network. EFnet is where most TI-related IRC channels (most notably, #Cemetech, #Omnimaga and Ticalc.org's channel #TI) are located, and a list of available servers is available at http://www.efnet.org/?module=servers . The IRC channel is +s (secret) right now, so it won't show up when regular IRC users type /list in their client, but you should be able to join with no problem using your favorite IRC client, IRCCloud or Mibbit. If a server doesn't work for you, try another from the list.You can also chat from WalrusIRC directly above the forums if you have 5 posts and higher, or from our Discord server at https://discord.gg/0PDECJFM043A0FdD . Regardless of where you chat from, your messages will be automatically relayed between the IRC channel and the site shoutbox.#CodeWalrus shall be a place to hang out for CodeWalrus forum members. We recommend that people who need calculator, programming or other kind of technical help use the forum, though, in case their query gets missed. More people will benefit that way, since it won't get lost in the logs.In addition to #CodeWalrus, there are other CW IRC channels, also on EFnet and Discord:#cw-anime: While our main channel allows anime discussion, it's recommended to use this smaller channel instead when #CodeWalrus is busy with programming discussion.#cw-craft: CW Minecraft server IRC channel. You can chat with people in-game there or vice-versa.#cw-spam: Bot-testing channel. This is *not* a flooding channel.#texttospeech-discord-only: Moonbase alpha style trolling. Use /tts command for text to speech. This channel is only on Discord.#safe-haven: Discord-only channel for real-time private matters discussion#staff: Discord-only channel that is only available to CodeWalrus staff.A voice chat is also available on Discord.
CodeWalr.us 2.0 © 2019, DJ Omnimaga & Juju
Page created in 0.043 seconds with 37 queries.