|
codemastr
2003-10-07 19:48
reporter
~0003793
|
That won't cause desync. Desync is when server1 says User is in #chan and server2 says User is not in #chan. That can't happen from this. |
|
|
|
Well I may have used the wrong term but it cause problems cause people and services believe that the person is in the chan when they have already parted it. I just thought it was an easy bug to fix since I gave you the code to fix it and I have tested it so I thought I would point it out but oh well. |
|
|
|
Well the only one who thinks he left the channel is the user itself, all other parties (the server, other clients, services etc) know [s]he is still in it. A shun completely shuns a user, someone else suggested allowing /quit in the past.. this too was rejected, the purpose is to completely make the user (or bot or whatever) unable to communicate.. so even denying quit or part. |
|
|
|
I will just reopen this bug since I believe I didn't state my bug in the right way. I ment to say that it desyncs the user. So I will give you a situation. You get shuned on a server so as a regular user not knowing much about IRC you close the channel window in your program such as mIRC, now when the shun expires say 10 minutes later and if you are still connected to the server you can no longer join the channel since the server thinks that you are still in the channel. That is the only reason I think that the part command should be allowed. I can understand the quit not being allowed cause if the user closes the connection completely the server knows and you get the client exited msg. This may not seem like a problem to you guys but I don't like my users to get confused or have to reconnect to rejoin a chan. |
|
|
|
That is a big with the IRC Client really.... not unreal |
|
|
|
brentos: for the previously shunned client to rejoin after parting during a shun, they just have to first type in: /quote part #channel, then they can rejoin. |
|
|
|
Funny to see you shun ppl, and a while later you remove the shun and are concerned with their problems. Hmmm.. mass shunning or something? ;p |
|
|
|
No we use the shun to repremand people for flooding/swearing etc. by adding a temp shun to stop them since the chat is open to young users so we can not have people swearing and what not but we still want the users to be able to have a good chatting experiance |
|
|
|
ic.. was just curious :p. |
|
|
|
If mIRC is indeed closing a channel window without having received the PART confirmation by the server first, it really once more shows what a stupid client mIRC really is.
Same goes for xchat :) |
|
|
|
Ok, well I don't really like it but I can see you got a good point.
I added set::options::allow-part-if-shunned. If enabled, it will allow shunned users to part (but it will remove their 'comment' parameter), this is however disabled by default. See Changes file for more info. |
|
