ok i have installed bitchx on debian so that i can use the irc channel on there while i work on the other pc which is xp pro. so what i need to know is
basic...how do i log the server for suck-o
bit harder.... how do i edit the batch file so that when someone does the /whois command they only see the nickname given on irc not my pc name?
thanks in advance
bitchx
- computathug
- Administrator
- Posts: 2693
- Joined: 29 Mar 2007, 16:00
- 17
- Location: UK
- Contact:
The question is: is he asking how to log chat or to connect to the server and join the channel?
A good tutorial on bitchx would be: http://linuxreviews.org/software/irc/bitchx/
About the /whois, there are different possibilities. If you're talking about not showing your IP address, then it all depends on the server. Some servers will mask your IP automatically, some servers will mask it if you register, it's a matter of what server Suck-o uses.
A good tutorial on bitchx would be: http://linuxreviews.org/software/irc/bitchx/
About the /whois, there are different possibilities. If you're talking about not showing your IP address, then it all depends on the server. Some servers will mask your IP automatically, some servers will mask it if you register, it's a matter of what server Suck-o uses.
- computathug
- Administrator
- Posts: 2693
- Joined: 29 Mar 2007, 16:00
- 17
- Location: UK
- Contact:
thanks for the info,
here is what i was looking for kind of
edit* reason behind why i am askin is when using bitchx on 1 pc and java on another i can use the
when using bitchx but when returned
i get no return using java
here is what i was looking for kind of
and through searching found what i was really looking for which isctcp cloacking: If you press the 'del' key, you'll turn on (or off) ctcp cloacking. This will prevent other users from getting extended information about i.e your bitchx version and stuff.
*** ADD MORE OPTIONS LIKE FLOODING, IGNORING, SHITLISTS, ETC
thought id post just incase someone else needs the same infoThere's one more detail you should be aware of before starting BitchX; the
shell variable IRCNAME will control your "Real Name" as displayed to other
people on IRC when they use the /whois command on you. You don't have to set
this, it's not vital, but if you would like to customize it's value set the
IRCNAME shell variable before starting BitchX like this:
export IRCNAME="your irc name"
I place a command like this in my user's .bash_profile startup script
(/home/username/.bash_profile).
edit* reason behind why i am askin is when using bitchx on 1 pc and java on another i can use the
Code: Select all
/whois thug
Code: Select all
/whois computathug
That's probably on the Java client's side.
I was looking through the IRC RFC (this is a link in case you want to check it out) a moment ago. Unless bitchx is messing with some of the information it sends in when you connect to the server, the server will always send back the information you gave it (such as nickname, full name, etc.) and the information that it knows about you (such as your hostname/IP address, channels you're in, etc.). Now the information it knows about you cannot be changed from your end because it doesn't need to ask you for it so there is no way you can give it inaccurate information.
/whois is not like /ping where it's between two clients, it's between the requesting client and the server. The target client may not even be aware of the /whois.
I was looking through the IRC RFC (this is a link in case you want to check it out) a moment ago. Unless bitchx is messing with some of the information it sends in when you connect to the server, the server will always send back the information you gave it (such as nickname, full name, etc.) and the information that it knows about you (such as your hostname/IP address, channels you're in, etc.). Now the information it knows about you cannot be changed from your end because it doesn't need to ask you for it so there is no way you can give it inaccurate information.
/whois is not like /ping where it's between two clients, it's between the requesting client and the server. The target client may not even be aware of the /whois.