doc/technical/elemental-deviation: Add information about elemental's use of global SNOMASKs
This commit is contained in:
parent
6da1d031e8
commit
fd552b946a
|
@ -33,3 +33,22 @@ Handling removal is similar.
|
|||
Currently, the only way to detect if a remote server supports these extended
|
||||
modes is to remotely query a server's `VERSION` and read out the `005` reply.
|
||||
|
||||
### Things added to existing commands
|
||||
|
||||
#### Server notice mask broadcasts
|
||||
|
||||
Currently the NEEDSASL, DNSBL hit, hunted command flooding and `m_post` rejections
|
||||
are globally broadcast server notices. They will show up in TS6 lines such as:
|
||||
|
||||
<<< :[sid] ENCAP * SNOTE [snomask] :[server name] :[message]
|
||||
|
||||
For a more practical example:
|
||||
|
||||
<<< :47G ENCAP * SNOTE b :rarity.shadownet.int :Client floodbot (~a@127.0.0.1) is attempting to flood ADMIN
|
||||
|
||||
These broadcasts are there for IRC operators on more centrally managed networks
|
||||
to better see what is going on on other ends of the network without having to hop
|
||||
servers and check. Bots or pseudoservices may also uses these lines to perform
|
||||
additional actions (such as `AKILL`s or logging to channels) as needed by the
|
||||
bot author.
|
||||
|
||||
|
|
Loading…
Reference in New Issue