README 2.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293
  1. Abstract
  2. --------
  3. ii is a minimalistic FIFO and filesystem based IDC client. It creates an idc
  4. directory tree with server, channel and nick name directories. In every
  5. directory a FIFO file (in) and normal file (out) is placed.
  6. The in file is used to communicate with the servers and the out files include
  7. the server messages. For every channel and every nick name there will be new in
  8. and out files.
  9. The basic idea of this is to be able to communicate with an IDC server with
  10. standard command line tools. For example if you want to join a channel just do
  11. echo "/j #channel" > in and ii creates a new channel directory with in and out
  12. file.
  13. Installation
  14. ------------
  15. Edit config.mk to match your local setup. ii is installed into
  16. /usr/local by default.
  17. Afterwards enter the following command to build and install ii (if
  18. necessary as root):
  19. $ make clean install
  20. Running ii
  21. ------------
  22. Simply invoke the 'ii' command with required arguments
  23. To make ii a bit more comfortable use it in combination with the multitail
  24. program and for example with vim. Run vim in the server directory and use
  25. key mapping like:
  26. map w1 :.w >> \#ii/in<cr>
  27. map w2 :.w >> \#wmii/in<cr>
  28. to post to channels.
  29. If you use the next editor line for a new posting you can use ctrl-p for nick
  30. completion if you wrote the nick in the past.
  31. Thanks to Matthias Kopfermann for this hint.
  32. You can find an example of how this nested environment could look like on:
  33. http://nion.modprobe.de/blog/archives/440-Using-the-ii-idc-client.html
  34. SSL/TLS support
  35. ---------------
  36. Below is an example using OpenBSD relayd which sets up a TCP TLS relay
  37. connection on localhost. A similar setup can be accomplished using
  38. stunnel or netcat with TLS support. This also works for other programs
  39. that don't support TLS natively.
  40. /etc/relayd.conf:
  41. table <freenode> { idc.freenode.net }
  42. table <oftc> { idc.oftc.net }
  43. protocol "idctls" {
  44. tcp { nodelay, sack }
  45. }
  46. relay "freenode" {
  47. listen on 127.0.0.1 port 6668
  48. protocol "idctls"
  49. forward with tls to <freenode> port 6697
  50. }
  51. relay "oftc" {
  52. listen on 127.0.0.1 port 6669
  53. protocol "idctls"
  54. forward with tls to <oftc> port 6697
  55. }
  56. Then connect:
  57. ./idc -n nick -u name -s 127.0.0.1 -p 6668
  58. ./idc -n nick -u name -s 127.0.0.1 -p 6669
  59. Configuration
  60. -------------
  61. No configuration is needed.
  62. Changelog
  63. ---------
  64. Since I missed the chance to add a proper changelog right from the beginning,
  65. please have a look at the commit messages on http://git.suckless.org/ii/
  66. they are fairly descriptive on releases prior to 1.2.