Menu
▾
▴
SILC Client 0.9
|
From: Pekka R. <pri...@ik...> - 2002-05-16 07:01:25
|
The SILC Client version 0.9 is now available! The software is available
from the following sources:
http://silcnet.org/
ftp://ftp.silcnet.org/
And here we go with the new Irssi SILC client version 0.9, implementing
all the nice things found in the SILC protocol version 1.1. Before going
into details a warning is due here. This version is not fully compatible
with older servers so if you end up connecting to older server with this
new client you may experience minor problems. Another warning is that
this is a major new release so it is quite possible there's some problems.
Also I'd like to announce that I won't be residing anymore on "#silc"
channel after this release. I will pack my bags and move to "silc"
channel. You are all welcome there. :) I have updated every reference on
the silcnet.org webpage to point "silc" and not "#silc". :)
But then, let's talk a bit about new features in this version:
o New DETACH command. This command can be used to detach from the server
but still remain in the network. When you give the /DETACH command
(it takes no arguments) your connection to the server will be closed
and a "detachment" data will be saved into ~/.silc/session file.
Next time you connect to any server in the network the Irssi SILC client
will read that file and use the data inside to resume your detached
session back. If you were joined on channels when you detached, you
will also automatically "join" those channels when you resume. It will
only seem like you joined them, for real you were joined those all the
time. This is to just bring the user interface up to date after
resuming.
A note here I have to make. If you have joined many channels then
the resuming may take some time, something like 2 - 5 seconds maybe,
depending on how many channels you were joined. Reason for this is that
when you resume your detached session to the server, the client will
resolve information about channels, channel users, modes, topics etc
from the server by sending commands, and server will think that you are
flooding it with commands so it starts limiting for how many commands
you may execute. This is the reason it may take a few seconds, because
server is limiting your command flooding. If you have joined only one
or two channels there should not be any delay during resuming.
If there is an error during resuming the server will close connection
and you will have to reconnect, and the session will not be resumed.
Messages that has been sent to you while you were detached are always
dropped by the server, so you never get them.
So to test this you can do something like this:
/server silc.silcnet.org
/join silc
send "blabla" to channel
/detach
*** connection lost to silc.silcnet.org
/server silc.silcnet.org
*** connection resumed to silc.silcnet.org
send "blabla" to channel
Also note that server may limit your detaching. It is possible for
the server to disallow the DETACH command. You won't be able to detach
your session in the server which has denied this. Also, server may set
a time limit for preserving detached sessions. For example, server may
have a 24 hour limit which means that if you don't resume your session
back after 24 hours the server will disconnect your session and you
won't be able to resume it back.
o New presence settings with UMODE command. People have used to give
the /AWAY when leaving the network. Now there are other presence
indicators in SILC as well, and you can set them with UMODE command
(maybe later there's aliases like /AWAY is too):
/umode +g set to be "gone" (same as /AWAY)
/umode +i set to be "indisposed"
/umode +b set to be "busy"
/umode +p set to be "awaiting paging"
/umode +h set to be "hyper active"
The "indisposed", "busy", "page me dummy" and "I'm hyper active" are
the new presence indicators. See /help UMODE for more information.
If someone is for example "busy" you can see it with /WHOIS command.
o There's also a "robot" user mode that is suggested to be used if you
are actually a robot program. I'm sure bots will start appearing soon
in SILC and I for sure will allow them only if they have the robot user
mode set. It can be set with the UMODE command. See /help UMODE.
This mode is important because some users can block messages from robots
by setting +r mode with CUMODE command.
o Yeah, message blocking. You can block unwanted private messages by
setting yet another user mode with UMODE command, this time it's
/umode +P. If you set this no one can send you private messages unless
they first negotiate private message key with you (for example with /KEY
command). This is nice feature if you don't want to talk with private
messages unless they are strictly secured with private message key.
Then blocking messages on channel. The +r mode to CUMODE was to
block channel messages sent by robots like I said. If you want to live
on the edge you can set +b mode; it will block *all* channel messages,
just give: /cumode channel +b yournick. If you don't want to be that
extreme there's also +u mode which can be used to block messages sent
by normal users. You will receive only messages sent by operators and
founder.
o Channel moderating. "Would you like to shut up those that don't have
ops?". Well, just set +m mode with CMODE command and normal users
won't be able to talk on the channel. "Would you like to shut up those
that DO have ops?" :) Well, just set +M mode and those that have ops
won't be able to talk. Set both +m and +M if you want that only the
founder on the channel can talk.
o "Tired of receiving invites to channels?". You probably answer No, but
if you would happen to answer Yes, you *can* block invites as well.
Just set yet another user mode with UMODE, this time it's +I, and
you won't get invites. Note that this may make joining to invite only
channels a bit harder.
o You want to have permanent channels, don't you? Set the +f mode with
CMODE command you have your very own channel, and you will be able
to reclaim the founder rights back on any server in the network.
The -pubkey option from CMODE, CUMODE and JOIN commands is history now.
So to set the +f, give: /cmode channel +f, and that's it. To reclaim
founder rights during joining give: /join channel -founder, and that's
it. To reclaim founder rights after joining give: /cumode channel +f
yournick. So the difference is that you don't have to give the -pubkey
option any more. On the other hand, you cannot give passphrase anymore
to +f mode, the public key is used automatically.
o New WATCH command. It can be used to watch some nicknames. To add a
nickname to be watched give: /watch -add foonick. When the "foonick"
comes to the network, leaves the network, changes user mode (like /AWAY,
or detaches from the network), or changes nickname you will be notified.
To remove nickname from watch list give /watch -del foonick.
If *you* don't want that someone can watch you, you can set yet another
user mode with UMODE. Give, /umode +w and nobody can watch you.
See also /help WATCH.
o Latest bugfixes taken from the Irssi.org CVS for the Irssi SILC client.
That's about it. Please test a lot since this version suffers from lack
of testing since I haven't had time to test. Report bugs here on the
silc-devel mailing list.
Please refer to the ChangeLog on the website, or the CHANGES file in the
package for complete list of changes.
Pekka
________________________________________________________________________
Pekka Riikonen priikone at silcnet.org
Secure Internet Live Conferencing (SILC) http://silcnet.org/
|
