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
@SoniEx2 wants me to have PRIVMSGs sent by bots be bracketed with "[bot]\x01CW0 " and "\x01", which, under a proposed CTCP extension of theirs (SoniEx2/CTCP-S#7), would result, if I understand correctly, in supporting clients rendering the message as hidden by default, prefixed with the text "[bot]".
As far as I am aware (and as far as @SoniEx2 has said) no clients currently implement this CTCP extension, and in WeeChat at least I see the bracketing strings come through mostly unchanged (the one change being that the start-of-heading characters are shown as ␁ SYMBOL FOR START OF HEADING), thus:
2018-08-30 01:41:50 <SoniEx2> [bot]␁CW0 example␁
I am open to adding an option for having bots bracket their messages like this, but I'm loath to make it the default with neither wide client support nor popular demand.
The text was updated successfully, but these errors were encountered:
@SoniEx2 wants me to have
PRIVMSG
s sent by bots be bracketed with"[bot]\x01CW0 "
and"\x01"
, which, under a proposed CTCP extension of theirs (SoniEx2/CTCP-S#7), would result, if I understand correctly, in supporting clients rendering the message as hidden by default, prefixed with the text "[bot]".As far as I am aware (and as far as @SoniEx2 has said) no clients currently implement this CTCP extension, and in WeeChat at least I see the bracketing strings come through mostly unchanged (the one change being that the start-of-heading characters are shown as
␁
SYMBOL FOR START OF HEADING), thus:I am open to adding an option for having bots bracket their messages like this, but I'm loath to make it the default with neither wide client support nor popular demand.
The text was updated successfully, but these errors were encountered: