3 ms·
Very interesting. We already track "errors" (responses that don't have connections) and we could make a real time error corrector. Let's say you have a yes/no q
by zekenie 13y ago
Very interesting. We already track "errors" (responses that don't have connections) and we could make a real time error corrector. Let's say you have a yes/no question and someone says "nah." If you didn't want them to recieve a text saying "the options were yes and no," we could maybe make it so you could click on the node you wanted it to go to... But, I'm not sure if there's much demand for this type of feature in general. I think most users won't want to have real time people sitting in the trext app. I'd be interested in talking about it more though!
- jmhnilbog 13y agoRight, mine is a pretty specific use case. However, if a thesaurus lookup can figure out that nah is close enough to no that it should just normalize the response to no, that's a win for the user. (Scraping urban dictionary to act like a thesaurus would be a decent way to decipher txt spk and euphemisms as well.) Yes/No questions could be special cased to accept more oddball responses off the bat..'for sure', 'totally', 'no way', etc.
- zekenie 13y agoAgreed. I'm not a natural language expert by any means, but from the research I did a little while ago, it seemed like the thesaurus apis matched "yes" to "affirmative" and not to "yeah." Maybe I haven't found a good one?