View Issue Details

IDProjectCategoryView StatusLast Update
0003302unrealircdpublic2007-04-27 03:16
ReporterShining Phoenix Assigned Tostskeeps 
PrioritynormalSeveritytweakReproducibilityalways
Status resolvedResolutionduplicate 
Platformi386OSLinuxOS Version2.6.10-1.771_FC2
Product Version3.2.6 
Summary0003302: Suggestion: If someone can't talk, they can't nickchange either
DescriptionIf a user cannot speak in a channel, they should not be able to change their nickname while in it either. Permanent bye-bye to * User is now known as I_Need_Voice !! :D
There is one question to ask - when a channel has modes u and m but not M set, should users without voice still be able to nickchange?(If this tweak gets done)
TagsNo tags attached.
3rd party modules

Relationships

duplicate of 0001853 closed Some modes block user talking, but not nick changing? 

Activities

Bricker

2007-04-26 02:47

reporter   ~0013713

eh

stskeeps

2007-04-26 06:30

reporter   ~0013731

This just affects the state in other channels, which is silly. Why not be able to change your nick? I know it's irritating but that's .. life :P

syzop

2007-04-26 06:35

administrator   ~0013733

it's very annoying if you're on various chans AND a +mu channel (like auto news feed from one bot) and you cannot nickchange.
this can be very true for +m channels as well (similar story as above but not +u)

users can already not nickchange if +b
you can already prevent all users from nickchanging with +N
you can already prevent all users from nickchanging with +b ~n*!*@*
etc..

so I'd say: no. Set +N explicitly if you want no nickchanges, don't inherit it from +m.

As for +M, it's probably confusing to do things differently for that.

syzop

2007-04-26 06:36

administrator   ~0013734

yeah i'm a slow typer now :(

Issue History

Date Modified Username Field Change
2007-04-26 00:35 Shining Phoenix New Issue
2007-04-26 02:47 Bricker Note Added: 0013713
2007-04-26 06:30 stskeeps Status new => closed
2007-04-26 06:30 stskeeps Note Added: 0013731
2007-04-26 06:30 stskeeps Resolution open => wont fix
2007-04-26 06:35 syzop Note Added: 0013733
2007-04-26 06:36 syzop Note Added: 0013734
2007-04-27 03:16 stskeeps Relationship added duplicate of 0001853
2007-04-27 03:16 stskeeps Duplicate ID 0 => 1853
2007-04-27 03:16 stskeeps Status closed => resolved
2007-04-27 03:16 stskeeps Resolution wont fix => duplicate
2007-04-27 03:16 stskeeps Assigned To => stskeeps