Skip to content
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

Tell users how to open messages #1

Open
paulwalko opened this issue Oct 8, 2018 · 2 comments · May be fixed by #6
Open

Tell users how to open messages #1

paulwalko opened this issue Oct 8, 2018 · 2 comments · May be fixed by #6

Comments

@paulwalko
Copy link
Member

The current message is "$user: You have messages".

Many people don't know how to receive messages so something like "$user: You have messages. Say something to open them." would be nice.

@echarlie
Copy link
Member

echarlie commented Oct 8, 2018

That seems a little noisy and doesn't resolve the real problem, which is that tell behaviour is just dumb and inconsistent with the rest of Phenny's interface. We probably should just fix the stupidity of tell s.t. the syntax is more like:

<paulwalko> .tell echarlie fix that bug on phenny
<Phenny> Okay; I'll tell echarlie "fix that bug on phenny"
--> echarlie has joined #fakechannel
<Phenny> echarlie: you have messages
<echarlie> .pop 1
<Phenny> Pop 1 message: echarlie: fix that bug on phenny -- paulwalko

or somesuch. Perhaps make .open equivalent to .pop @ (open all messages). I guess we could make it a queue instead of a stack.

@mutantmonkey
Copy link
Contributor

So, while I agree that users might be confused as to how they read their messages, what I've usually seen happen is that people ask "how do I check my messages?" at which point phenny responds with their messages. So while it might be unclear initially, users can quickly figure it out; I'm not convinced any changes are necessary.

@echarlie I strongly disagree, that's going to horribly confuse people.

@mutantmonkey mutantmonkey transferred this issue from mutantmonkey/phenny Oct 22, 2019
@paulwalko paulwalko linked a pull request Oct 22, 2019 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants