This could be achieved with the following check:

containsVeryLongWord && nonEnglishPost

I'll fix that. The issue is just a reminder for myself.

When I report an answer to Natty with the command @Natty report <link to answer> and the answer is not to an old question, I recieve the following message from Natty:

Post is not allowed to be reported in this room.

This message doesn't make it clear that I tried to report a too new answer. It would be better to have a specific error message for that, something like:

Post is not a new answer to an old question.

Or even shorter, although the abbreviation might be confusing for newer users:

Post is not a NATO.

Use this issue to report any Feature Requests. They can be of the type,

• Additional Filters : They extend the Validator and return only those results that pass that filter.
• Blacklisting Keywords : Of the type, Please help, How can I, etc

The feedback tp should work as report command if post is not already present this since it will avoid userscript to have to call Natty or Sentinel api to check if already reported.

Suggested modification:

@Natty feedback <link> tp

should if post is not present report the post, hence work as the report command. The check is that post (NATO) is not present and the command is tp. The response will be as if it was reported and post will be marked with tn

Workaround: http://chat.stackoverflow.com/transcript/message/35071517#35071517

If we add support for more pages in the SE-network, we should make lists that define, which filters are used on which site. This could be achieved by adding the interface FilterList and classes like StackOverflowFilterList and AskUbuntuFilterList that are implementing this interface

The

• etiquette docs at
  • https://natty.sobotics.org/etiquette and
  • https://github.com/SOBotics/Natty/blob/588794cca038c23678ffa2fbbbc056857dabd206/docs/etiquette.md ,
• and the autoflagging docs at
  • https://natty.sobotics.org/autoflagging and
  • https://github.com/SOBotics/Natty/blob/588794cca038c23678ffa2fbbbc056857dabd206/docs/autoflagging.md

are empty. Only headings exist with no normal text. These pages should either be filled in or removed.

I've noticed a couple of "inconsistencies" recently in Natty links. The first time I figured it was a user-error on my end, but this time it seems more obvious that something's going wrong. Or it could be another user-error ...

Natty responded SOBotics chat permalink to a @natty fetch links 5 with two unhandled (but deleted) posts. When checking via Sentinel, it showed that Feedback had been received, two hours earlier, by two separate users. The reports were via Natty, not Sentinel as I can see in the chat search.

So it seems that Natty is responding with links that have already been handled?

Implement method to retract flags from chat room

Currently api does not support this, but with latest change in chat lib probably a jsoup request should be enough.

For more details see How can bots retract flags on answers?

Can we have a cancel command on fetch ? I accidentally hit @Natty fetch without the amount option and @ Natty keep posting indefinitely the posts with feedback needed.

Other suggestion would be not letting fetch command run without amount option

In some languages, there might be piled symbols in the code: http://sentinel.erwaysoftware.com/posts/12275

To exclude these, I'll try to check if the symbols are within a code-block

The current blacklist catches lots of tps, but it's pretty dumb. Every phrase has a value of 2.0.

Statistics show, that not every blacklisted word works as good as the others. Some have a higher percentage of fps, others almost none.

If Natty would frequently (once a day?) fetch statistics about each blacklisted phrase (like the statistics provided in Sentinel's search), we could calculate the value based on the percentage of fps.

Example:

((1−fps/postsMatchingThePhrase)^maxScore) * maxScore

maxScore should be pretty high, so that a post containing a phrase with 0% fps will always be reported. Let's use for example 4.

For "please help", this would result in a value of 3.96.

"i have the same problem" has a higher percentage of fps. So the value would be only 2.98.

I tried to show this in a spreadsheet:

Natty-IntelligentBlacklist.xlsx

hope the export from Apple Numbers worked correctly.

I can't find the new commands added in v4 (like who, for example) anywhere in the docs. Those should be added.

send f t u t u u t t t t t f t t t t t f yields "Too many feedbacks, Too less reports".
https://chat.stackoverflow.com/transcript/message/34836989#34836989
I think it's because you are simply splitting the string on every space or counting spaces somewhere.

Since Natty recently crashed, because there was no space left for new logfiles, we should delete old logs automatically like SOBotics/Guttenberg#27.

With 16,000+ unhandled Natty reports on Ask Ubuntu, I'm not sure we ever catch up to the point where fetch links is helpful.

It would be nice if fetch links reported most-recent first so that we could make sure that recent, more "urgent" reports are handled.

As you might have heard, Stack Exchange will remove OpenID.

Since tunaki/chatexchange is currently using OpenID to connect to chat, we had to release an update. If you don't update, you won't be able to connect to chat after July 25, 2018.

We've moved the project to org.sobotics.*. This is the updated dependency:

<dependency>
  <groupId>org.sobotics</groupId>
  <artifactId>chatexchange</artifactId>
  <version>2.0.0</version>
</dependency>

You'll have to update your import statements. All APIs are still the same, so you don't have to modify the implementation.

If you have issues updating your project, feel free to ask for help in our chatroom.

When you report an answer manually using the report command, Natty only provides a FMS link, instead of Sentinel, even if Sentinel is up.

For consintency, this should be handled the same way as in normal reporting, where FMS is only used when Sentinel is not reachable/down.

Travis should deploy each tag/release to the server automatically

When we switch the style of the reports in SOBotics, it could be useful, having a why command like Smokey. Replying why to a report could trigger a message in the style of check explain