CINXE.COM
OFTC - WebChat
<!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=utf-8"> <meta name="robots" content="index,follow"> <title>OFTC - WebChat</title> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <link href="/img/oftc-16.png" rel="shortcut icon" type="image/png" /> <link href="/css/bootstrap.min.css" rel="stylesheet" media="screen"> <link href="/css/main.css" rel="stylesheet"> <script src="/js/jquery.min.js"></script> <script src="/js/bootstrap.min.js"></script> <script src="/js/main.js"></script> </head> <body> <div class="navbar navbar-fixed-top"> <div class="navbar-inner"> <div class="container"> <form class="navbar-form pull-right" action="//webchat.oftc.net" method="get" target="_blank"> <input name="nick" type="text" data-toggle="tooltip" title="Enter your IRC nickname" class="span2" placeholder="Nickname"> <input name="channels" type="text" data-toggle="tooltip" title="Enter comma seperated list of channels to join" class="span2" placeholder="#oftc, #moocows"> <input type="hidden" name="uio" value="d4"> <button type="submit" class="btn">Chat!</button> </form> <button type="button" class="btn btn-navbar" data-toggle="collapse" data-target=".nav-collapse"> <span class="icon-bar"></span> <span class="icon-bar"></span> <span class="icon-bar"></span> </button> <a class="brand" href="/">OFTC</a> <div class="nav-collapse collapse"> <ul class="nav"> <li><a href="/">Home</a></li> <li><a href="/staff/">Staff</a></li> <li><a href="/documentation/">Documentation</a></li> <li><a href="/FAQ/">FAQ</a></li> </ul> </div><!--/.nav-collapse --> </div> </div> </div> <article> <div class="container"> <div class="row-fluid"> <div class="span12"> <h2 id="webchat">WebChat</h2> <p>We provide a web interface for chatting on our network at <strong><a href="https://webchat.oftc.net">https://webchat.oftc.net</a></strong>.</p> <p><em>webchat.oftc.net</em> is a slightly modified version of <a href="http://qwebirc.org">qwebirc</a>. It only serves static files. Your browser will use javascript and <a href="http://socket.io">socket.io</a> to directly connect to the API at <strong><a href="https://webirc.oftc.net:8443">https://webirc.oftc.net:8443</a></strong>.</p> <h2 id="webirc">WebIRC</h2> <p><em>webirc.oftc.net</em> is a thin proxy run directly on our servers that acts as a https<->IRC gateway:</p> <ul> <li>No unnecessary third parties between you and OFTC.</li> <li>Your communication with OFTC is always encrypted. <ul> <li>Soon you’ll be able to identify with services by installing a client certificate in your browser (see <a href="/NickServ/CertFP">NickServ/CertFP</a>)</li> </ul> </li> <li>Speaks raw IRC to your browser (negotiated by socket.io) so you’re free to write your own client.</li> <li>Your IP will appear on the network, and not the IP of the web server that hosts the client software. <ul> <li>Allows OFTC and channels to better manage themselves.</li> <li>Keeps you from being stuck into strict connection limits.</li> </ul> </li> </ul> <h2 id="alternate-clients">Alternate Clients</h2> <p>Users are free to implement their own web client that connects to <em>webirc.oftc.net</em> with socket.io to port 8443. Alternate clients do not need to be hosted on <em>oftc.net</em> to allow connections, our usage of socket.io means that if the client supports websockets or jsonp they can use cross domain communication.</p> <p><em>Note:</em> There may come a time when OFTC needs to implement some form of “human detection”, if that time comes alternative clients will need to make sure their clients support that mechanism.</p> <ul> <li>There are no known alternate clients at this time.</li> </ul> </div> </div> </div> <!-- /container --> </article> </body> </html>