A typical smoke detector message is formatted like this:

[ SmokeDetector ] Bad keyword in body: How to read some columns from a CSV file with C++? by Adrian on stackoverflow.com (..mentions..) …

Would it be worth adding that prefix to the bot as well? I'm assuming that most people interact with the bot by reacting to reports auto-announced. It will also help advertise that it's a bot and give a quick way to access the commands.

[ SOCVFinder ] [tag:possible-duplicate] [tag:java] [tag:rest] [tag:spring-restcontroller] [tag:spring-rest] Currency Symbols like €,£ are Corrupted in Spring HTTP.GET

Queen messages posted in SOCVR are getting a bit too much, more than our cv-pls.

Here are my ideas to lower the report count:

1. Only allow a set number of reports per time frame. For example: 5 reports per 60 minutes.
2. Only report when some part of the post as reached a threshold, like the score is < -1.

These two options however dilute the speedyness of the reporting system. If the point of the bot is to allow people to dup-hammer quickly on newly created posts, these options are less than ideal.

Two other options:

1. Don't ping people in SOCVR, ping them in the SOCVFinder room. (Doesn't really solve the "massive number of reports in SOCVR problem)

2. Instead of posting each report in SOCVR, tell a user

   There are 3 [tag:possible-duplicate] posts created recently in your watched tags. View them [here].

   The link would send you to the first message in SOCVFinder.

_{Title reference}

Hydrant - A dashboard for Heat Detector

After collecting some important points about the new dashboard, I'm compiling them here and formalizing the creation of a new dashboard.

Need

Heat Detector is quite famous networkwide for its ability to detect rude and abusive comments.
However the problem that we are facing at hand is that not many people are feeding back accurately
(The bot utilizes ML and feedback is very very important for it's improvement).
This issue can be easily solved by having a web dashboard.

Thoughts

Unlike CopyPastor, which had to be written from scratch, the dashboard for HD can be easily modeled based on Sentinel. The similarities between Natty and HD are:

• Both are related to flagging (comment vs answer)
• Both have various reasons for detections
• Both need feedback

Changes

Changes needed on the HeatDetector side:

• A proper/strict rule to differentiate between what should be a true positive and what should be a false positive.
• A way to provide feedback through a command, so that a userscript could be made use of.
• And of course, calling the dashboard in every report.

Challenges

• Framing the strong rules to differentiate between a heated argument and not is often subjective. Quantizing this in someway in order to improve the algorithm would be the first challenge. (This is not related to the dashboard development work, but the way we provide feedback).
• Few of the posts might be borderline, and we wouldn't want to feedback these. Hence a way to "not provide feedback" would be needed.
• We are also tracking a few keywords like "spam", "rude", etc which aren't noisy comments, but are meant to help us discover spam or r/a posts. We need a different feedback type for this.
• We need to find a way to anonymize the data which we display on the dashboard. Some kind of a login would be nice, but one other idea is to display minimal information (just the comment text and reasons, for example), and display all the details after logging in.
• Art is very very busy at the moment and certainly won't have much time to design the dash. Hence we'll need to either do it in one of the languages which we know or recruit someone who knows Ruby and RoR. Given that we still haven't put up an opensource ad this time, it might be a bit hard.

Hosting

We can host it on the sobotics webserver. That would not be an issue.

http://socvr.org:222/api/socv-finder/dump-report is no more.

We should move to https://github.com/SOBotics/Reports

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 maven 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.