You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 26, 2018. It is now read-only.
When IRC client requests extended-join, it will also get NickServ username and realname in join message. It could be nice if botbot logged those instead of only someone joined the channel.
When extended-join is enabled with WeeChat it shows nick [nickserv_account] (real name) (user@host) has joined#channel`
Thank you @Mikaela for the suggestion. Agreed that would be nice; unfortunately we don't have any plans or availability for working on this at the moment. We'll keep this open as a nice-to-have and let you know if the status changes.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When IRC client requests extended-join, it will also get NickServ username and realname in
join
message. It could be nice if botbot logged those instead of onlysomeone joined the channel
.When extended-join is enabled with WeeChat it shows
nick [nickserv_account] (real name) (user@host) has joined
#channel`The specification also mentions account-notify which wouldn't be a bad thing either allowing when
nick
logins asaccount
to be also logged.I think
whox
might not be so useful as what point of log would the bot put people who were already identified and it's expected to be always online.The text was updated successfully, but these errors were encountered: