{"action":"created","issue":{"url":"https://api.github.com/repos/freenode/ircd-seven/issues/14","repository_url":"https://api.github.com/repos/freenode/ircd-seven","labels_url":"https://api.github.com/repos/freenode/ircd-seven/issues/14/labels{/name}","comments_url":"https://api.github.com/repos/freenode/ircd-seven/issues/14/comments","events_url":"https://api.github.com/repos/freenode/ircd-seven/issues/14/events","html_url":"https://github.com/freenode/ircd-seven/issues/14","id":173104433,"number":14,"title":"Wishlist: /botnotice command","user":{"login":"a-raccoon","id":1052090,"avatar_url":"https://avatars.githubusercontent.com/u/1052090?v=3","gravatar_id":"","url":"https://api.github.com/users/a-raccoon","html_url":"https://github.com/a-raccoon","followers_url":"https://api.github.com/users/a-raccoon/followers","following_url":"https://api.github.com/users/a-raccoon/following{/other_user}","gists_url":"https://api.github.com/users/a-raccoon/gists{/gist_id}","starred_url":"https://api.github.com/users/a-raccoon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/a-raccoon/subscriptions","organizations_url":"https://api.github.com/users/a-raccoon/orgs","repos_url":"https://api.github.com/users/a-raccoon/repos","events_url":"https://api.github.com/users/a-raccoon/events{/privacy}","received_events_url":"https://api.github.com/users/a-raccoon/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-08-25T03:07:26Z","updated_at":"2016-08-25T09:33:46Z","closed_at":null,"body":"```\r\n4.4.3 Bot Notices\r\n\r\n      Command: BOTNOTICE\r\n   Parameters: <channel> <nickname,s> :<text>\r\n\r\n   The BOTNOTICE message is used similarly to NOTICE.  As with NOTICE,\r\n   automatic replies must never be sent in response to a BOTNOTICE\r\n   notice.  The difference between NOTICE and BOTNOTICE is the addition\r\n   of a target parameter and how the NOTICE is received by the target\r\n   client or clients.  The first parameter is the channel from which the\r\n   NOTICE is to appear to have been sent to, and the second parameter is\r\n   the actual target client (or clients) who should receive the NOTICE.\r\n\r\n   Only clients with channel operator (+o) status may be able to send\r\n   a BOTNOTICE command for a given channel.*  Whether the issuing client\r\n   is a bona fide automaton or just a client user is unimportant to the\r\n   function of this command.  The purpose is to permit bots and client\r\n   scripts to interact with and address users in the context of a\r\n   channel.  This allows client programs to know where to paint the\r\n   notice text so it can appear in the channel window instead of a\r\n   status or query window that the user isn't interacting with or\r\n   currently paying attention to.\r\n\r\n   **Many bots do not utilize NOTICE as they should (see: 4.4.2), because\r\n   the authors of those bots know that standard NOTICEs tend to go\r\n   unnoticed, and missed.**\r\n\r\n   Examples:\r\n\r\n   BOTNOTICE #Twilight_zone Angel :Welcome to the channel!\r\n                           ; Message sent to Angel in #Twilight_zone\r\n\r\n   :Wiz NOTICE #Twilight_zone :Welcome to the channel!\r\n                           ; Message from Wiz to Angel in #Twilight_zone\r\n\r\n\r\n   See PRIVMSG for more details on replies and examples.\r\n\r\n   * Channel op status is not necessarily necessary, and the command can\r\n   ideally be used by any helper bot or client script without being any\r\n   more abusable than regular /notices or /msgs.  Client /ignore and\r\n   /filter commands already silence channel-targeted notices when said\r\n   user is placed on ignore.\r\n\r\n```"},"comment":{"url":"https://api.github.com/repos/freenode/ircd-seven/issues/comments/242330522","html_url":"https://github.com/freenode/ircd-seven/issues/14#issuecomment-242330522","issue_url":"https://api.github.com/repos/freenode/ircd-seven/issues/14","id":242330522,"user":{"login":"Xenthys","id":15252571,"avatar_url":"https://avatars.githubusercontent.com/u/15252571?v=3","gravatar_id":"","url":"https://api.github.com/users/Xenthys","html_url":"https://github.com/Xenthys","followers_url":"https://api.github.com/users/Xenthys/followers","following_url":"https://api.github.com/users/Xenthys/following{/other_user}","gists_url":"https://api.github.com/users/Xenthys/gists{/gist_id}","starred_url":"https://api.github.com/users/Xenthys/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Xenthys/subscriptions","organizations_url":"https://api.github.com/users/Xenthys/orgs","repos_url":"https://api.github.com/users/Xenthys/repos","events_url":"https://api.github.com/users/Xenthys/events{/privacy}","received_events_url":"https://api.github.com/users/Xenthys/received_events","type":"User","site_admin":false},"created_at":"2016-08-25T09:33:45Z","updated_at":"2016-08-25T09:33:45Z","body":"That effectively is a mean I did not think about.\r\nHowever, routing notices that appear as public to only one client can be a bit frowned upon, as clients will not be able to say if it really is a public NOTICE or if it is a BOTNOTICE, so it could be misleading.  \r\nFor the alternative prefixed notice, we fall under a client compatibility that is not everywhere.\r\nI am currently using @HexChat and it does not seem to support it properly."}}
{"actor":{"display_login":"Xenthys"}}