If I have a problem with my internet connection and had to reconnect before my previous nick was dropped I get a different nick, e.g. osa1_. After a while osa1 gets disconnected and I switch back to my original nick with /nick osa1. At that point I have to identify myself via NickServ if that's the authentication method I'm using. Currently tiny doesn't do that automatically, but I think it could. Basically if the nickserv_ident is used and nick is in the user's nick list (rather than generated by tiny while trying to find an available nick) then we should send a identify message automatically.
If I have a problem with my internet connection and had to reconnect before my previous nick was dropped I get a different nick, e.g.
osa1_. After a whileosa1gets disconnected and I switch back to my original nick with/nick osa1. At that point I have to identify myself via NickServ if that's the authentication method I'm using. Currently tiny doesn't do that automatically, but I think it could. Basically if thenickserv_identis used and nick is in the user's nick list (rather than generated by tiny while trying to find an available nick) then we should send a identify message automatically.