Skip to content
This repository has been archived by the owner on Jul 11, 2019. It is now read-only.

add /alias command #107

Closed
tunnckoCore opened this issue May 1, 2015 · 6 comments · Fixed by #114
Closed

add /alias command #107

tunnckoCore opened this issue May 1, 2015 · 6 comments · Fixed by #114

Comments

@tunnckoCore
Copy link
Contributor

and yea, would be good to follow irc signature

@ungoldman
Copy link
Member

This isn't compatible with the way we're handling authentication and signing for the moment -- we're using github usernames and public keys so that identities are in some way verified.

@misspokeycat
Copy link
Contributor

@ngoldman I think that he's referring to command aliases, as per http://www.ircbeginner.com/ircinfo/h-aliases.html . I imagine the syntax for an alias command would be something along the lines of /alias <alias name> <command to execute> so that a command/string of commands/long message could be easily sent. For example, /alias foo /join bar would make /foo run the /join bar command. Additionally, frequently used chat messages could be done this way, such as /alias hello Hello world! would cause the command /hello to send "Hello world!" to the channel.

@ungoldman
Copy link
Member

ah ok, I think I misinterpreted it as a /nick thing 😓

@tunnckoCore
Copy link
Contributor Author

I think that he's referring to command aliases

yes, exactly. one more link http://www.mirchelp.net/helpfile/aliases.htm

ah ok, I think I misinterpreted it as a /nick thing

ha, but you have right in your previous comment. the problem is where to save this aliases per session (per user). i guess leveldb is only used for message/channel logs? if we start using the db and for users and their aliases... it wouldn't be good thing.

@ungoldman
Copy link
Member

localStorage would work for now

@ungoldman ungoldman reopened this May 1, 2015
@tunnckoCore
Copy link
Contributor Author

ha, good idea, I forgot it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants