View Issue Details

IDProjectCategoryView StatusLast Update
0001611unrealircdpublic2004-06-04 14:20
Reporterfez Assigned To 
PrioritynormalSeverityfeatureReproducibilityalways
Status closedResolutionopen 
Product Version3.2-RC1 
Summary0001611: notice recipient segregation grandfathering...
Descriptionok I propose this feature, let me know what you think:

as it is, one can do a /notice @#channel to send messages only to ops on a channel, or /notice %#channel to send only to halfops...

i propose to perhaps make a simple modification to src/modules/m_message.c so that when one does /notice %#channel, it sends the message to halfop OR BETTER (including +o, +a, +q)...
(the same principle would be applied to /notice +#channel, etc...)

what do you think?

-- fez
3rd party modules

Activities

Praetorian_

2004-03-01 04:04

reporter   ~0005261

While it sounds sensible

This would then prevent people being able to message only half ops or only voiced or only op'd... :)

AngryWolf

2004-03-01 12:26

reporter   ~0005262

Is that difficult to type %@&~#channel? :)

Bergee

2004-03-01 22:07

reporter   ~0005265

I'll chime in because I was just coming here to post this exact suggestion. I've had reports of problems with people spamming just the voiced members of the channel, it would be useful if these types of notices went to voice and everyone above so such problems can be dealt with easily by the channel ops.

If not being able to notice only the voices is a problem for some people as Praetorian seems to suggest, then maybe it should only apply if you're not a channel op or above.

codemastr

2004-03-04 18:18

reporter   ~0005298

But what if you want it to just be sent to voiced users? I mean that's why we support multiple flags.

m0wl

2004-03-05 02:24

reporter   ~0005303

If someone had ~&@%+ the notice/privmsg-sender would not see it anyway.

aquanight

2004-06-04 01:44

reporter   ~0006572

With, 0001812, bugnote 0006270, I think this can be closed now ;) .

syzop

2004-06-04 14:20

administrator   ~0006589

Hmm indeed. I think I even used the wrong bug # in Changes (1812 instead of this one.. since this one was earlier :P).. Ah well ;).

Issue History

Date Modified Username Field Change
2004-03-01 03:47 fez New Issue
2004-03-01 04:04 Praetorian_ Note Added: 0005261
2004-03-01 12:26 AngryWolf Note Added: 0005262
2004-03-01 22:07 Bergee Note Added: 0005265
2004-03-04 18:18 codemastr Note Added: 0005298
2004-03-05 02:24 m0wl Note Added: 0005303
2004-06-04 01:44 aquanight Note Added: 0006572
2004-06-04 14:20 syzop Status new => closed
2004-06-04 14:20 syzop Note Added: 0006589