The send field should also be considered empty with regard to typing notifications when the field starts with / (eg if you start typing /join #foo, there's no need to send out @+typing since you're not writing a message to the channel)

Tested, works fine with the patch I sent and my updated bot.

OK. Then I will send a patch for @+soju.im/channel to goguma-dev and send an MR to ircv3-specs in addition to the existing issue.

Yes. Heuristics work fine in the context of a traditional client but not when using CHATHISTORY as the issue mentions.

I am suggesting to start supporting the yet-to-be-implemented tag @+draft/channel (this should be a simple +10/-0 diff ish) and I will update my bots to use them. As for bots that do not support @+draft/channel, we can do snackbars or something else.

Most bots will use NOTICE when responding directly to user commands in a channel, by sending them a direct NOTICE, as a way to avoid flooding the channel. See the linked issue for that use case. These messages should be treated as if they were regular messages sent to the corresponding channel, rather than as a private message.

PRIVMSG #chan :!help
:bot NOTICE me :Help derp.

This "Help derp" message is intended by the bot to show in the #chan channel (and it does for most clients) to avoid flooding the channel with this info. NOTICE is almost used like a special keyword to mean that this is a message that should be shown in the last used/current channel.

As for the case where bots respond to NOTICEs in a channel, I agree they should show up just like regular channel PRIVMSGs.

For traditional cases where you are have goguma opened on a particular buffer when the message is received taking the first opened buffer with both you & the sender works fine, but in the case where you fetch old history in the background it can be difficult to select the appropriate buffer (you don't necessarily know on which buffer the sender was at the moment).

Should we start supporting eg @+channel first and update some of our bots to use it and see how it goes?

One particular case of NOTICE messages is bot response messages to !commands in channels (in order to avoid flooding the channel with responses). See: https://github.com/ircv3/ircv3-specifications/issues/497

Some channels (eg an unnamed popular channel for anime encodes) use IRC formatting in their channel topics. Trim that formatting.

Instead of stripping IRC formatting (the bare minimum we can do), use IRC message formatting to render the text according to the passed format (bold, colors, etc.)

See: https://modern.ircdocs.horse/formatting.html

Also see: https://github.com/ircv3/ircv3-ideas/issues/16