Introduction
Introduction Statistics Contact Development Disclaimer Help
weechat's weechat relay plugin
Saturday Jan 18 3:11:44 2014
Weechat supports two different relay protocols: 'irc' and 'weechat'
I know that the names 'irc' and 'weechat' sound a bit confusing
because they both refer to an internet protocol and an irc program
and also to the names of two protocols which are specific to an irc
program, weechat in this case. But I hope I can make it clear :)
Last year I wrote a phlog post on how to use the 'irc' one (which c
be used with almost any irc client). And today I will explain how t
use weechat's weechat relay plugin (which is easier to setup but ha
the disadvantage that you can only connect to it with a client that
supports it (for example weechat itself, QWeeChat or weechat-androi
You can also read the full tutorial that I added to sdfeu's website
Weechat tutorial
Let us start from scratch. To begin with, start weechat-curses,
connect to your networks/servers and join your favourite channels.
In order to use the 'weechat' protocol on sdfeu you only need one
single port which is your uid number. Type 'id' at the shell and yo
will see something similar to this:
odin:~$ id
uid=007(bond) gid=500(arpa) groups=500(arpa),600(MetaARPA),700(dba)
Only the "uid" part is relevant here, "uid=007(bond)" which means
that "007" is the "port" and "bond" is the "username". Let's now
assume that user "bond" wants to use the password "james_bond" (Thi
way, you will understand the examples better).
- Inside weechat:
* First add the relay
/relay add weechat port
Example: /relay add weechat 007
* Set the password
/set relay.network.password "password"
Example: /set relay.network.password "james_bond"
- On the client side:
Now, simply connect from your client to sdfeu.org using your port a
your password. Your client will connect to the client running on sd
and connect to all the networks and channels and besides, it will
retrieve the backlog.
Nifty!
You are viewing proxied material from sdf.org. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.