Preconfigured Nick Lock Option - No Appended Nicks

[ndoggac]

Instead of attempting to reconnect as fast as possible upon internet connection return, with a new appended nick using the math.random approach, have a feature option where you can force that it will only reconnect using the original configured nick. If connection is denied, then wait a configured amount of time before attempting reconnect again - again only with the preconfigured nick.

My ISP is terrible, and I lose internet every other day for just a minute or two at a time. Upon reconnect to internet, thelounge connects back up as fast as possible, often with a randomized nick if the original gets denied because it's still in use. I don't like this as many of my connections earn me rewards (i.e. meaningless site stats) for connection time, but it has to be using my originally configured nick. The random nick doesn't get me anything. To fix I have to manually disconnect, open the connection options, correct the appended nick, save, then reconnect. Even if I restart, the appended nick is now my default option. It's a huge pain! I'd rather wait 10-15 minutes for my "nick in use" to clear on the server, and only connect using my preconfigured nick. Also, my preconfigured nick should not be permanently overwritten so even after restart I'm affected.

[fnutt]

When TL auto-reconnects, it will try to use your nick. If it is taken it will use a new nick. However, it will try to regain your old nick as soon as possible when it is free.

[ndoggac]

When TL auto-reconnects, it will try to use your nick. If it is taken it will use a new nick. However, it will try to regain your old nick as soon as possible when it is free.

This is not the behavior I experience. It's never reconnected using the originally configured nick, and it also overwrites the pre-configured nick. When I override manually (usually hours later when I realize) my nick is always available, so why didn't the program auto change over prior? Is there a config option that I need to enable to get this function? I'm on latest v4.2.0.

[itsjohncs]

The Lounge will already try to get your original nickname if it sees that the nick become available. But the implementation is somewhat limited.

After it connects with an alt nick it will look for a quit message from your old nick. If it sees one, it will immediately reclaim it. So The Lounge isn't seeing your old nick's quit message. I don't know exactly why that's the case, and don't have a workaround to give you, but perhaps someone else will.

I don't think a nick lock option is necessary here. If we get dev time to improve this situation, I think improving the mechanism for reclaiming the nick will be good. A couple quick thoughts on how that could be done:

• Poll to see whether the nick is still around on some interval, maybe with a backoff.
• Use MONITOR to ask the server alert us when the nick is free, if the server supports it.

[ndoggac]

After it connects with an alt nick it will look for a quit message from your old nick. If it sees one, it will immediately reclaim it. So The Lounge isn't seeing your old nick's quit message. I don't know exactly why that's the case, and don't have a workaround to give you, but perhaps someone else will.

I'm specifically asking for an implemented workaround here. Every server I connect to exhibits this same behavior. So either every server is not implementing the quit message properly or TL is not handling a received quit message properly. If the former does happen (which I'm sure it will, always), then better logic around the "quit" message isn't going to make a difference and a TL user has no recourse. The implementation of a "nick lockout" feature with a configurable timeout for reconnect attempt seems a lot simpler, and more desirable approach to me. There's no scenario where I want my client to reconnect using any other nick than the one I configured, and I'm not able to do this in TL. Instead random nick updates are forced upon me in the pursuit of "quickest reconnect time". I don't care about speed of reconnect, I care about auto re-connecting with only my configured nick no matter how long I'm unable to reconnect. The configurable time is only so I don't hammer on the server. Perhaps have a max reconnect attempts option too.

[ndoggac]

Wondering if this option is being entertained by devs? I love TL, but this is a very annoying limitation.

[brunnre8]

@ndoggac simply needs someone doing the work, can you send a patch? john outlined the solutions in this thread

[c10l]

I don't think a Nick lock option would be ideal either. The Lounge should never change a user-set parameter in the server config.

I understand (although don't necessarily agree with) trying randomly-suffixed nicks when the original has been taken but please don't touch my settings!

[bobokun]

Is it possible to have this feature implemented? It's really annoying when I have to always re-adjust my nickname back to the original one after it pre-appends some numbers to it

[zDEFz]

I also experience the behavior that

1. TL does try to use the set nick, and if its taken, it uses another
2. Once it has its new name and the old is free, it does not re-take the original nick
3. It overwrites the server settings (nick) to whatever iteration it succeeded with
4. It completely ignores the nick set in the SASL configuration

[ndoggac]

@ndoggac simply needs someone doing the work, can you send a patch? xPaw outlined the solutions in this thread

I see no xPaw outlined solutions in this thread. I am not a capable enough programmer to implement the feature.

[qaqland]

Any update here?

[qaqland]

When comes to oftc.net, use Commands in User preferences instead of Cerft could get the same nickname.

/msg NickServ identify <passwd> <name>