Forums Bug Reports /shun bug/glitch.

If you get shunned on a network and then disconnect, mIRC treats your status as offline when technically it's still online. (As shun disallows quits. (Or is supposed to.))

I only noticed this when I tried quitting during a test shun via the disconnect button and my mIRC titlebar changed to it's offline state even though I hadn't actually quit at all.


This was actually last year, so I can't remember the version.


*edit*

This isn't limited to /shun.

On a very badly scripted mIRC IRCd I wrote at like 13, I halted the /quit command:



... and then /quit.


The $status reply reads as "disconnecting" and my titlebar is in the offline state.

So you break the IRC protocol on the server side, and then the client doesn't guess what you intended to do? How is this a bug?

That was just to test my theory.

But if you're shunned and still do that it'll read you as offline.

What version of mIRC are you using?

Also, been on many IRCD's and been oper on them, a shun will stop you executing any commands except a /quit
In any case, why would it disallow a quit? the idea of a shun is to stop an annoying person or such like, if they /quit they are gone from the server.

2nd edit: I think that mIRC had a $status bug anyway, i was the one who reported it lol

At the moment, v6.21 ... but I think it was v6.17.


*edit*

Yeah, it was five days before the release of v6.2, so v6.17.

I wasn't just talking about your script. From RFC 1459:

If some feature from some lameass ircd (unrealircd i guess?) breaks such basic things, then again, you cannot expect mIRC to keep working fully correctly. mIRC is simply waiting for the server to close the connection, and with non-broken IRC servers, that will always happen.

As a Services Admin on two networks that both use UnrealIRCd, I can state that a person that is shunned still has the ability to use /quit or /disconnect with the current version of Unreal, which is 3.2.6

soo.. this is a bug report for an outdated mirc version connected to an outdated unrealircd version?

I don't connect to any Unreal IRCd servers.

The servers that I'm on that have the SHUN command are Nefarious IRCu.


All of which disallow /quit.

Well whatever the IRCd they shouldn't be disabling /quit under any circumstances.

In my opinion mIRC should just hard disconnect after a few seconds anyway, which is what I thought it already does.

Whilst I agree that it's daft to disable /quit, I think it would make more sense for mIRC to wait until it receives the QUIT message back before acting.

/disconnect can be used for hard disconnects, /quit should leave it up to the server.

Why's that? There's only one reason anyone would ever use the quit command and that's to leave the server.

If /quit hard-disconnects after a short delay then the worst that can happen is that the quit message doesn't get seen. No big deal.

If it doesn't and the IRCd is malicious or just sucks then it's all a bit of a mess. /disconnect probably isn't all that well known to a lot of new users. Sure they can use the disconnect button in the toolbar but they'll probably be wondering why the hell they weren't disconnected by /quit in the first place.

Can't have IRC servers trying to take people hostage now can we?

The /quit command is supposed to make you quit the server, but it's the server that's supposed to close the connection. If mIRC does it, then it's not really going to be any different from /disconnect.

It just seems logical to me to leave /quit processing up to the server. New users usually manage to find their way here or to a help channel if need be.

It should be left to the server, but if the server ignores the
quit command because of a shun on the client (which is pretty
stupid) then it should disconnect after a few seconds of waiting.

That's right, mIRC sets an internal flag when you manually disconnect/quit. The only features in mIRC that are affected by this are the $status identifier and the "retry on disconnection" feature.

mIRC must set this flag for the "retry on disconnection" feature to work. If mIRC does not set it, it won't know if the server disconnected you itself or if you manually initated a quit/disconnect (in which case mIRC should not try to reconnect).