Skip to content

Notice handling

Jump to bottom
James Wheare edited this page Apr 24, 2015 · 6 revisions

Client handling

  • Notices are rendered as monospace, with a shaded background, and only prefixed with the source if it's a nickname
  • Notices can trigger temporary popup overlays, that hide after 5 seconds, except in the following cases:
    • Source is the same as recipient (echo message)
    • Destination is the currently selected buffer
    • Destination is server buffer and source is a server hostname
    • Destination is a channel
  • 5 second timeout can be cancelled by hovering over the overlay
  • Notices mark a channel as unread except in the following cases:
    • Source is the same as recipient (echo message)
    • Source is a server hostname
    • Destination is sever buffer and message has been copied to PM buffer
  • Notices sent to a PM buffer do not increment its highlight count the way PRIVMSG does

Categories of use:

  • Notifications set up by a channel maintainer
  • Global announcements from a server admin
  • Standard connection handshake
  • Notifications about a personal account or connection
  • Response to a query
  • On-join/on-connect messaging/advertising

Channel notices

Source Target Destination
server hostname or nick channel channel only 
:server.example.com NOTICE #channel :message
:[email protected] NOTICE #channel :message

Notification bots

23:17 <IrssiGithub> irssi/master c122a2a Alexander Færøy: Merge pull request #241 from pstray/master...
23:23 <travis-ci> irssi/irssi (9540a60: Alexander Færøy): The build passed.

Channel member messaging, higher profile privmsg

09:20 <james> hello

Takeover protection: TS change notification on rejoin, souce: server

22:34 *** Notice -- TS for #bleepie changed from 1423953245 to 1266862539

Spam, source: server

22:56 [freenode-info] if you're at a conference and other people are having trouble connecting, please mention it to staff: http://freenode.net/faq.shtml#gettinghelp

Obvious server notices

Source Target Destination
server hostname varies: *, Auth, connecting user (ignored) server buffer only 
:server.example.com NOTICE * :message

Connection handshake progress

22:38 *** Looking up your hostname...
22:38 *** Checking Ident
22:38 *** Found your hostname
22:38 *** Got Ident response

Other server status

13:27 *** You are banned from GeekShed (Session limit exceeded)

All other notices

Source Target Destination
nickname connecting user (ignored) server buffer, if a PM already exists with the source a copy is sent there too 
:[email protected] NOTICE mynick :message

Auth status on connect/identify

19:07 <NickServ> This nickname is registered. Please choose a different nickname, or identify via /msg NickServ identify <password>.
19:07 <NickServ> You are now identified for james.

Auth abuse notifications

22:38 <SaslServ> 6 failed logins since last login.
04:12 <NickServ> NlackBigger!~Nlack@unaffiliated/illya failed to login to jwheare.  There has been 1 failed login attempt since your last successful login.

Supplementary MOTD on connect

15:07 <InfoServ> *** Message(s) of the Day ***

Global admin announcement

19:32 <GeekShed-Announcer> Services are now back online. GeekShed apologizes for the inconvenience.

Status messages

19:32 <OperServ> The session limit for your host brockwell.irccloud.com has been exceeded. This means there are too many clients connected to our servers from your network or internet connection.

Chanserv set join message (notably not targeted at channel)

22:38 <ChanServ> [#nginx] Community Nginx support channel. Don't ask to ask; just ask! Config pastes via http://p.ngx.cc only. This channel is publicly logged.

Response to query

19:04 <NickServ> ***** NickServ Help *****
09:27 <NickServ> Information on jwheare (account jwheare):

Response to CTCP

09:17 <james> TIME Fri, 24 Apr 2015 08:17:25 GMT
Clone this wiki locally