Skip to content
Stephen E. Baker edited this page May 15, 2017 · 51 revisions

CIRC is an IRC client in the form of a packaged Chrome app. That means it acts like a native application and has access to low level APIs such as chrome.socket. Here are some of the key features of CIRC:

  • Connect directly to any IRC server (no proxy server needed!)
  • Remember your nick and what channels you were last in on any device
  • Use the same IRC connection simultaneously on multiple devices (similar to Google Hangouts)
  • Scripting support
  • Desktop notifications
  • SSL support

Get it on the Chrome Web Store.

Need help?

Check out the tips & tricks page.

Issues

If you find a bug or have an idea for a new feature, please file an issue.

Development

Development on CIRC has only just begun! Take a look at the changelog to see what we've been working on with each version.

If you're interested in the exciting features we have in store, check out our development timeline.

Interested in contributing to CIRC? Send over a pull request with your changes. You can also check out the class diagram to get an idea of how things work. Information on the development cycle can be found in our development doc.

Scripting

Scripts are written in JavaScript and loaded from a file on the user's computer.

View the scripting docs for details on the running scripts and the scripting API.

One identity

You can choose one of your devices to act as a server to which your other devices can connect. Connected devices use the IRC connection of the server device and activity is mirrored across each connected device. Whenever you install CIRC on a new device it will automatically connect to the server device. If the server is unreachable then the client use it's own connect as normal.

To use the feature use the /make-server command on the device you wish to use as the server. That device will remain the server even across sessions. Use /make-server again on a different device to change servers. The devices connect to each other using TCP sockets, so port forwarding may be required.

Details on integrating one identity with scripting can be found in this doc.

Clone this wiki locally