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

Warn users not to ask to ask #53

Open
Unihedro opened this issue Mar 5, 2015 · 11 comments
Open

Warn users not to ask to ask #53

Unihedro opened this issue Mar 5, 2015 · 11 comments

Comments

@Unihedro
Copy link
Owner

Unihedro commented Mar 5, 2015

When users show an asking pattern that appears to be enquiring for topic experts, whether they can ask a question, or if anyone's active, the bot should warn them not to ask to ask, as having chat users to reply with that reduces efficiency.

A sample message might look like a derivative of this:

Don't ask to ask. Don't ask for topic experts. Don't ask if anyone's online.

@Vogel612
Copy link
Collaborator

Vogel612 commented Mar 5, 2015

This should be rather easily solvable over the already existing "Interactions"-System. A list of "phrases" to fuzzily react to might include:

  • Can I ask a question
  • Is there someone
  • anyone who is|knows
  • Can someone help (me )?with
  • ...

@Unihedro
Copy link
Owner Author

Unihedro commented Mar 6, 2015

Most of the "someone"/ "anyone" phrases should be interchangeable as well, so make them (?:any|some)one, and we probably need to make the match case-insensitive (you probably already realized this before me), and phrases like "I have a problem" or "anyone good at" doesn't hurt to be included as well.

@Vogel612
Copy link
Collaborator

Vogel612 commented Mar 8, 2015

There is a first preview available at Vogel612/javabot@e207772

@Vogel612
Copy link
Collaborator

Vogel612 commented Mar 8, 2015

It might be inconcievably simpler to just add a command for that, and dump the whole Interaction concept, because of the sheer complexity of human language.

@Zomis
Copy link

Zomis commented Mar 8, 2015

Speaking of complexity of human language, this issue seems related to Duga searching for comments on Stack Overflow about Programmers and Code Review and trying to filter them and post them to chat rooms. See Zomis/Duga#62

Please don't give up on this :) I'm sure it's possible, somehow! And when you have figured it out, you can help me who's dealing with a similar problem ;)

@fge
Copy link
Collaborator

fge commented Mar 8, 2015

@Zomis just forget it; why do you think there is a dedicated research group for this at Stanford, no less, which has procuded StanfordNLP?

And if you look at their API, you had better have preliminary, and extensive at that, knowledge of both linguistics and parsing. This subject is of practical implication, surely enough, but it is hard.

VERY hard.

@Zomis
Copy link

Zomis commented Mar 8, 2015

That is what I was afraid of, @fge. I knew this was a research-topic in itself. Was primarily hoping to get some assistance in this difficult quest.

@Unihedro
Copy link
Owner Author

Well, after short thinking a regex is probably still the most effective for figuring this out, as well as duplicate checks to make sure we don't spam the message to the same user(s) many times. I'm going to collect some existing candidates for poking with the message and then see if I get anything worthy of attention.

@Vogel612
Copy link
Collaborator

Alternatively we could define some keywords, and weigh them against some other factors. The message then would get posted if we pass a certain threshold.

@Unihedro
Copy link
Owner Author

@Vogel612: That's so ArcticEcho/Phamhilator.

@Vogel612
Copy link
Collaborator

'course it is. But it works well for them, it seems to also have worked for Andy's flag-bot, why shouldn't it work for us??

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

No branches or pull requests

4 participants