search

ircv3 / ircv3-ideas

46 stars 3 forks source link

Standardise NOTICE within channel context #44

Closed jesopo closed 1 year ago

jesopo commented 5 years ago

Simple premise - imagine a bot that greets users via NOTICE when they join a channel. This is currently often done by NOTICE user :[#channel] hello! but I think we could do something a lot better than that.

My proposition: @+channel-context=#channel NOTICE user :[#channel] hello! - it'd be backwards compatible and be a lot more concretely related to a channel.

DanielOaks commented 5 years ago

This sort of tag sounds reasonable but the "[#channel] " on the front of the message feels not-that-needed. Most of the time, if users join a channel and instantly get a message from a bot they're gonna recognise it (and most other channel-specific bot dms are gonna happen in response to commands they actively run, so no worries about them noticing what it's from).

grawity commented 5 years ago

The prefix is useful as the client can use it as a hint for choosing the window (e.g. WeeChat shows such notices as PvNotice in the channel window, like a whisper). Without it, clients either dump notices in the server window (where they can get lost) or in the foreground window (which can be the wrong channel entirely).

I realize that ctctags are more suitable but the prefix is in active use now, e.g. by Atheme's Chanserv and the aforementioned WeeChat.

DanielOaks commented 5 years ago

Mm. Yeah thinking about it sounds fine, esp as something that works right now everywhere.

DanielOaks commented 5 years ago

It seems this prolly already exists out there by way of cnotice/cprivmsg, if we can just use this then cool: https://tools.ietf.org/html/draft-hardy-irc-isupport-00#section-4.6

jesopo commented 5 years ago

that would prohibit non-op bots from using it and it seems to not include a channel context - just allows an op to message the user without flood controls.

DanielOaks commented 5 years ago

ah, I missed the bit about that being restricted to ops/etc. if that's true then that too, bleh. fairfair

emersion commented 4 years ago

Alternatively, this could be a server tag, and the server could add the prefix if the client doesn't support the extension.

jesopo commented 3 years ago

on review of this, I think I'd prefer this be moved to a numeric instead of a NOTICE. I don't know if clients are good at redirecting unknown notices to channel buffers though.

emersion commented 1 year ago

This has been standardized with https://github.com/ircv3/ircv3-specifications/pull/498