It is currently Fri Dec 14, 2018 4:52 am

All times are UTC [ DST ]




 Page 1 of 1 [ 10 posts ] 
Author Message
 Post subject: [General] /notice or /ctcp #channel
PostPosted: Sun Jul 16, 2006 1:35 pm 

Joined: Wed Mar 27, 2002 1:00 am
Posts: 76
Location: Trois-Rivières, Canada
Other than being used for sending pub or flooding, are there any useful reasons why such commands exist? If not, how difficult would it be to disable these commands?


Offline
 Profile  
 
 Post subject:
PostPosted: Sun Jul 16, 2006 1:41 pm 
User avatar

Joined: Sun Aug 01, 2004 9:22 pm
Posts: 639
Location: Backyard
i believe this thread shouldn't be posted here, on General posts section. and i don't see any reason(s) why it should be disabled. if you are a channel operator into a certain channel and someone is advertising/spaming/flooding trough notice, its quite simple, ban him/her.



_________________
"A wise man writes down what he thinks, a stupid man forgets what he thinks, a complete idiot punishes himself for what he thinks."
Offline
 Profile  
 
 Post subject:
PostPosted: Sun Jul 16, 2006 3:05 pm 

Joined: Wed Mar 27, 2002 1:00 am
Posts: 76
Location: Trois-Rivières, Canada
SpYdeRX wrote:
i believe this thread shouldn't be posted here, on General posts section. and i don't see any reason(s) why it should be disabled.

Where else should it be since I am not asking for help but just seeking opinions?

SpYdeRX wrote:
if you are a channel operator into a certain channel and someone is advertising/spaming/flooding trough notice, its quite simple, ban him/her.

Yes, I am chanop serving on a channel having more than 300 users at peak time. I have a script which stop them within the second they start flooding. No, we don't ban them because that would only fill in the banlist and I am not re-opening that debate again.

Here is a excerpt of what's happening. Do you still believe that "its quite simple, ban him/her". I hope you have a fast connection and that you're quick on the gun. :-)

[22:02:27] CTCP VERSION: from Noelle (Noelle!~bbbb@213.23.4.74) to #channel
[22:02:27] CTCP PING: from Noelle (Noelle!~bbbb@213.23.4.74) to #channel
[22:02:27] CTCP VERSION: from Roselaine (Roselaine!~disque@correo.hoteldoncarlos.com) to #channel
[22:02:27] CTCP PING: from Roselaine (Roselaine!~disque@correo.hoteldoncarlos.com) to #channel
[22:02:27] CTCP VERSION: from Orphelisa (Orphelisa!~marcher@85.11.155.42) to #channel
[22:02:27] CTCP PING: from Orphelisa (Orphelisa!~marcher@85.11.155.42) to #channel
[22:02:27] CTCP VERSION: from Elidie (Elidie!~erreur@correo.hoteldoncarlos.com) to #channel
[22:02:27] CTCP PING: from Elidie (Elidie!~erreur@correo.hoteldoncarlos.com) to #channel
[22:02:27] CTCP VERSION: from Gratiala (Gratiala!~protected@62.14.109.126) to #channel
[22:02:27] CTCP VERSION: from Chrenelie (Chrenelie!~frozen@62.14.109.126) to #channel
[22:02:27] CTCP PING: from Gratiala (Gratiala!~protected@62.14.109.126) to #channel
[22:02:27] CTCP PING: from Chrenelie (Chrenelie!~frozen@62.14.109.126) to #channel
[22:02:27] CTCP VERSION: from Annabella (Annabella!~documents@217.86.154.37) to #channel
[22:02:27] CTCP PING: from Annabella (Annabella!~documents@217.86.154.37) to #channel
[22:02:27] CTCP VERSION: from Ildephonsine (Ildephonsine!proxy@212.92.5.163) to #channel
[22:02:27] CTCP PING: from Ildephonsine (Ildephonsine!proxy@212.92.5.163) to #channel
[22:02:27] CTCP TIME: from Gratiala (Gratiala!~protected@62.14.109.126) to #channel
[22:02:27] CTCP VERSION: from Maximilienne (Maximilienne!~divan@217.86.154.37) to #channel
[22:02:27] CTCP PING: from Maximilienne (Maximilienne!~divan@217.86.154.37) to #channel
[22:02:27] CTCP VERSION: from Edmond (Edmond!~aaaa@160.254.broadband6.iol.cz) to #channel
[22:02:27] CTCP PING: from Edmond (Edmond!~aaaa@160.254.broadband6.iol.cz) to #channel
[22:02:27] CTCP TIME: from Chrenelie (Chrenelie!~frozen@62.14.109.126) to #channel
[22:02:27] CTCP TIME: from Orphelisa (Orphelisa!~marcher@85.11.155.42) to #channel
[22:02:27] CTCP TIME: from Elidie (Elidie!~erreur@correo.hoteldoncarlos.com) to #channel
[22:02:27] CTCP TIME: from Roselaine (Roselaine!~disque@correo.hoteldoncarlos.com) to #channel
[22:02:27] CTCP VERSION: from Odovic (Odovic!~pas@211.105.188.237) to #channel
[22:02:27] CTCP PING: from Odovic (Odovic!~pas@211.105.188.237) to #channel
[22:02:27] CTCP TIME: from Odovic (Odovic!~pas@211.105.188.237) to #channel
[22:02:27] CTCP TIME: from Noelle (Noelle!~bbbb@213.23.4.74) to #channel
[22:02:27] CTCP VERSION: from Ostias (Ostias!~tonmail_p@220.122.82.34) to #channel
[22:02:27] CTCP PING: from Ostias (Ostias!~tonmail_p@220.122.82.34) to #channel
[22:02:27] CTCP TIME: from Ostias (Ostias!~tonmail_p@220.122.82.34) to #channel
[22:02:27] CTCP FINGER: from Gratiala (Gratiala!~protected@62.14.109.126) to #channel
[22:02:27] CTCP TIME: from Annabella (Annabella!~documents@217.86.154.37) to #channel
[22:02:27] CTCP FINGER: from Annabella (Annabella!~documents@217.86.154.37) to #channel
[22:02:27] CTCP VERSION: from Holdore (Holdore!~primo@195.243.136.99) to #channel
[22:02:27] CTCP PING: from Holdore (Holdore!~primo@195.243.136.99) to #channel
[22:02:27] CTCP TIME: from Holdore (Holdore!~primo@195.243.136.99) to #channel
[22:02:27] CTCP FINGER: from Roselaine (Roselaine!~disque@correo.hoteldoncarlos.com) to #channel
[22:02:27] CTCP TIME: from Ildephonsine (Ildephonsine!proxy@212.92.5.163) to #channel
[22:02:27] CTCP FINGER: from Ildephonsine (Ildephonsine!proxy@212.92.5.163) to #channel
[22:02:27] CTCP FINGER: from Chrenelie (Chrenelie!~frozen@62.14.109.126) to #channel
[22:02:27] CTCP TIME: from Maximilienne (Maximilienne!~divan@217.86.154.37) to #channel
[22:02:27] CTCP FINGER: from Maximilienne (Maximilienne!~divan@217.86.154.37) to #channel


Offline
 Profile  
 
 Post subject:
PostPosted: Sun Jul 16, 2006 4:44 pm 
Forum Moderator
User avatar

Joined: Fri Nov 19, 2004 9:51 pm
Posts: 594
Location: Europe
If you set channel mode +r then only registered users will be able to join the channel, and almost all flood bots are not logged in to X. If you use channel mode +m then they won't be able to /msg, /notice or /ctcp #channel. You may choose which mode to use. You can also code your script to set channel modes +mr when the channel is flooded and ban the bots afterwards if you don't want to use any of these two modes permanently.

Best Regards,
Mit.



_________________
Dimitar Tnokovski aka Mitko
Image
Offline
 Profile  
 
 Post subject:
PostPosted: Sun Jul 16, 2006 6:17 pm 
Forum Moderator
User avatar

Joined: Tue Feb 17, 2004 11:12 am
Posts: 760
Location: Romania
Moderator note: Topic moved to a more proper section.

On Topic:

Notice and ctcp are sometimes usefull as you don`t always pay attention to irc, and some irc clients make sounds on notice/ctcp and you might find an use in that. I also like the onotice feature...where ops talk in the channel among themselfs without regular users being able to see what they talk.

Msgs are also used to notice/flood...wouldn`t you like to disable that too? Sheesh...always disableing features...



_________________
sirAndrew @ Undernet.org

8 years on this forum and i'm still the #1 poster around.
Offline
 Profile  
 
 Post subject:
PostPosted: Sun Jul 16, 2006 6:19 pm 

Joined: Wed Mar 27, 2002 1:00 am
Posts: 76
Location: Trois-Rivières, Canada
Mitko, I appreciate your reply. This is exactly what my script does - +rm as soon as they start flooding either by ctcp or notice. My query was simple. Other than flooders, who would use these commands? For me, these commands directed to a channel seem to be used by flooders only. We don't use them on our channel.

regards,


Offline
 Profile  
 
 Post subject:
PostPosted: Mon Jul 17, 2006 2:05 am 
Senior Cservice Admin
User avatar

Joined: Sun Jul 06, 2003 2:47 am
Posts: 564
Location: Hamilton, New Zealand
History lesson:

CTCP's are client commands, and it's worth noting that /me IS a ctcp command.

CTCP's are really just ordinary messages that start and end with a ctrl-a (like colours - ctrl-c#,# (mirc converts the ctrl-k you type to ctrl-c for transmission), bold - ctrl-b, etc). your irc client should easily be able to disable use of CTCP's. (most irc clients just stop responding to them, while still allowing /me to work fine)

/notices are actually intended to be /msg's that scripts, and bot's (X, eggdrops, emech's etc) are supposed to use as responses to commands, but not to recieve commands with, therefore stopping any possible loop that could be created by bots responding to bots responding to bots ... get the idea.

So in short feel free to disable CTCP's they aren't actually part of IRC, they just use IRC to communicate over. /notice's are part of irc and therefore disabling is a bad idea.



_________________
xplora @ undernet.org
Past Co-ordinator
Undernet Channel Services Committee
Offline
 Profile  
 
 Post subject:
PostPosted: Tue Jul 18, 2006 11:17 am 

Joined: Wed Mar 27, 2002 1:00 am
Posts: 76
Location: Trois-Rivières, Canada
tx xplora

I always though that ctcp's were commands. I'll feel more intelligent when I go to bed tonight.

Keeping in mind that I'm talking about ctcp's and/or notices targetted to a channel rather than a particular user, could chanmodes be set to controlled them?

Like I mentioned before, I am not affected by any of this but our clientele is. I'm wondering if there would be other means to help clueless users who are simply interested in chatting and nothing more.


Offline
 Profile  
 
 Post subject:
PostPosted: Tue Jul 18, 2006 12:58 pm 
Senior Cservice Admin
User avatar

Joined: Sun Jul 06, 2003 2:47 am
Posts: 564
Location: Hamilton, New Zealand
there are no such modes at present, the coder are loath to do a channel mode that requires filtering actual messages (which would be required for ctcp's) however theres no reason the coders couldn't create a channel mode that could stop channel notices...

But in the end, there is no way to stop flooders, even MSN/ICQ/Yahoo/AIM/gTalk/you-name-it have this problem. stopping CTCP's and notices doesn't stop the problem :(

The best we can do is teach the users.



_________________
xplora @ undernet.org
Past Co-ordinator
Undernet Channel Services Committee
Offline
 Profile  
 
 Post subject:
PostPosted: Tue Jul 18, 2006 8:17 pm 
Forum Moderator
User avatar

Joined: Tue Feb 17, 2004 11:12 am
Posts: 760
Location: Romania
Actually adding modes to block ctcps/notices in channel are used on other networks and can we easily implemented in ircu...the only thing is coders to think it is necesarry to make such a change....but as undernet is unique by no nick registration and not filtering colors/ctcps/notices and no topic resynch i don`t think you`ll see such modes implemented on the network anytime soon.



_________________
sirAndrew @ Undernet.org

8 years on this forum and i'm still the #1 poster around.
Offline
 Profile  
 
Display posts from previous:  Sort by  
 Page 1 of 1 [ 10 posts ] 

All times are UTC [ DST ]


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  

cron