-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
History searching #9
Comments
I'd love a feature like this and thought about something similar when writing ircv3/ircv3-specifications#292. I decided to keep it out the the specification as it would break several expectations - most notably that the batch assumes chronological content from a single channel or query to be displayed in-line by the client. They would also need to be separate commands with a different set of parameters. I think this would be better off as it's own specification, rather than an extension of ircv3/ircv3-specifications#292. With the exception of requiring some form of server-side logging, they do not share much else in terms of either form or function, although a |
Right, and as I've actually gone back and read the spec I came to the same conclusion. I have some ideas for how this could potentially work. |
Surprised this hasn't been brought up yet. It would be a logical extension of CHATHISTORY from all I can tell. This is critical particularly to networks meant for intra-organization communication, where it may be important to reference a previous decision, explanation, etc.
The text was updated successfully, but these errors were encountered: