View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003297unrealircdpublic2007-04-24 22:302015-10-01 18:10
ReporterBricker Assigned Tosyzop  
PrioritynormalSeverityfeatureReproducibilityalways
Status closedResolutionno change required 
OSNAOS VersionNA 
Product Version3.2.6 
Summary0003297: new chanmode: prevent part msgs
Descriptiona channel mode that would determine the number of characters allowed in a /part message. I know this is done during ./Config (or so i remember it being done there) but it should be allowed to be set to something small per-channel if they want. Ideas?
TagsNo tags attached.
3rd party modules

Relationships

child of 0003284 closedsyzop 3rd Party Module Wishlist 

Activities

stskeeps

2007-04-25 03:13

reporter   ~0013675

Acknowledged, but isn't this kinda useless? People, discuss? :P

Bock

2007-04-25 05:59

reporter   ~0013679

it will not be useless: I my network many ops want this chanmode, cos f*king scripters in part message put string about 200 chars and more... Songs and etc..

WolfSage

2007-04-25 08:16

reporter   ~0013684

3rd party module or official?

Because if official, what about a topic len limit as well?

Bricker

2007-04-25 09:47

reporter   ~0013687

topic isnt much a worry because it cant really be spammed considering you have to be an op to set the topic most of the time, but as Bock says, spammers with their part messages.

stskeeps

2007-04-25 11:56

reporter   ~0013693

Write a patch ..

djGrrr

2007-04-25 12:18

reporter   ~0013696

it would make more sense to just have a mode which forces blank part/quit messages, rather than having them a specific length

Bock

2007-04-25 12:35

reporter   ~0013697

or replace with message for this trouble "like static part". But remove - more likely

Shining Phoenix

2007-04-25 16:26

reporter   ~0013699

Perhaps you could make existing channel modes, ie sCmMb, affect part messages.
And then perhaps add a new mode which makes all parts (by users without status?) in the channel static.

Bricker

2007-04-25 20:54

reporter   ~0013704

i dont see why those modes would affect /part. Anywho, stskeeps, what about one of the following

a channel mode to prevent /part messages,

and/or

a set::part that would, if the channel mode is set, replace it with a different message (like set::quit) or something of the like

Shining Phoenix

2007-04-25 20:57

reporter   ~0013705

Then you could strip colours from part messages, block coloured part messages, and stop people who can't talk from doing a part message. All this without any new settings or channel modes =P

Bricker

2007-04-26 02:56

reporter   ~0013717

you need to get your chanmodes correct next time ;P

syzop

2007-04-26 05:56

administrator   ~0013724

oh god.. this is horrible
definitely a 3rd party mod ;p

btw, i agree with:
it would make more sense to just have a mode which forces blank part/quit messages, rather than having them a specific length

but that's just my opinion

stskeeps

2007-04-26 06:19

reporter   ~0013728

I'm for syzop's opinion too

Shining Phoenix

2007-04-28 17:06

reporter   ~0013916

I'll add some more explanation for my above note.

A part message is sent to specified channel(s). People in those channels generally only see it in the relevant channel window.
A /privmsg #channel,... is sent to specified channel(s). People in those channels generally only see it in the relevant channel window.

A part message is just a different looking privmsg really, so making channel modes treat it like a privmsg makes sense to me.

Stealth

2008-03-09 15:15

reporter   ~0015224

Perhaps instead of a channel mode, we should make this an extban. People who don't want part messages can just ban ~p:*!*@*

... or we could do both

RandomNumber

2008-05-23 21:49

reporter   ~0015298

I am all for the extban for part messages. Would come in handy for a lot of situations.

Bricker

2010-04-03 19:52

reporter   ~0016060

Bump

dboyz

2015-09-30 07:23

reporter   ~0018709

There's a 3rd party module for this somewhere on the internet (written by fez or was it pena). The module still works the last time I checked.

syzop

2015-10-01 18:10

administrator   ~0018721

Yeah. Why is this still open.. hmmm...

Issue History

Date Modified Username Field Change
2007-04-24 22:30 Bricker New Issue
2007-04-25 03:13 stskeeps Note Added: 0013675
2007-04-25 03:13 stskeeps Status new => acknowledged
2007-04-25 05:59 Bock Note Added: 0013679
2007-04-25 08:16 WolfSage Note Added: 0013684
2007-04-25 09:47 Bricker Note Added: 0013687
2007-04-25 11:56 stskeeps Note Added: 0013693
2007-04-25 12:18 djGrrr Note Added: 0013696
2007-04-25 12:35 Bock Note Added: 0013697
2007-04-25 16:26 Shining Phoenix Note Added: 0013699
2007-04-25 20:54 Bricker Note Added: 0013704
2007-04-25 20:57 Shining Phoenix Note Added: 0013705
2007-04-26 02:56 Bricker Note Added: 0013717
2007-04-26 05:56 syzop Note Added: 0013724
2007-04-26 05:56 syzop Relationship added child of 0003284
2007-04-26 06:19 stskeeps Note Added: 0013728
2007-04-28 07:58 syzop Summary chanmod +(youpick) => new chanmode: prevent part msgs
2007-04-28 17:06 Shining Phoenix Note Added: 0013916
2008-03-09 00:22 immortal File Added: Unreal3.2.7.tar.gz
2008-03-09 15:15 Stealth Note Added: 0015224
2008-05-23 21:49 RandomNumber Note Added: 0015298
2010-04-03 19:52 Bricker Note Added: 0016060
2015-08-08 17:52 syzop Severity minor => feature
2015-09-30 07:23 dboyz Note Added: 0018709
2015-10-01 18:10 syzop Note Added: 0018721
2015-10-01 18:10 syzop Status acknowledged => closed
2015-10-01 18:10 syzop Assigned To => syzop
2015-10-01 18:10 syzop Resolution open => no change required