2024-06-19 07:53:27 +02:00
|
|
|
<!-- @format -->
|
|
|
|
|
|
2023-03-16 18:53:28 +01:00
|
|
|
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
|
|
|
|
|
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
|
|
|
|
|
|
|
|
|
|
- [Using NOTICEs instead of PRIVMSGs](#using-notices-instead-of-privmsgs)
|
|
|
|
|
- [Other options](#other-options)
|
|
|
|
|
- [Other plugins](#other-plugins)
|
|
|
|
|
- [Reverting](#reverting)
|
|
|
|
|
|
|
|
|
|
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
|
|
|
|
|
|
2021-06-13 14:19:17 +02:00
|
|
|
# Using NOTICEs instead of PRIVMSGs
|
|
|
|
|
|
2024-06-19 07:53:27 +02:00
|
|
|
Like https://tools.ietf.org/html/rfc1459#section-4.4.2 &
|
|
|
|
|
https://tools.ietf.org/html/rfc2812#section-3.3.2 say should be used.
|
2021-06-13 14:19:17 +02:00
|
|
|
|
2024-06-19 07:53:27 +02:00
|
|
|
This is per-channel, because of
|
|
|
|
|
https://github.com/42wim/matterbridge/issues/1393 and surely getting a new PM
|
|
|
|
|
buffer in some clients or consistency, I don't remember the other reason.
|
2021-06-13 14:19:17 +02:00
|
|
|
|
|
|
|
|
```
|
|
|
|
|
config channel #CHAN supybot.reply.error.withNotice True
|
|
|
|
|
config channel #CHAN supybot.reply.withNotice True
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
## Other options
|
|
|
|
|
|
|
|
|
|
`supybot.reply.withNoticeWhenPrivate` to have noticed used in private, not
|
|
|
|
|
channel-specific
|
|
|
|
|
|
|
|
|
|
## Other plugins
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
config channel #CHAN supybot.plugins.RSS.notice False
|
|
|
|
|
```
|
|
|
|
|
|
2023-02-26 18:01:13 +01:00
|
|
|
- RSS announces as NOTICEs
|
2021-06-16 23:15:58 +02:00
|
|
|
|
|
|
|
|
### Reverting
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
config reset channel #CHAN supybot.reply.error.withNotice
|
|
|
|
|
config reset channel #CHAN supybot.reply.withNotice
|
|
|
|
|
config reset channel #CHAN supybot.plugins.RSS.notice False
|
|
|
|
|
```
|
