redirect non answered support to general

[mandar1jn]

[wassfila]

RFC

https://hackmd.io/d9rRIFcGQ9KF5DI4ciVsrA

implementation spec:

1. collect all non answered support posts of last day, 12h, ... configurable in number of hours

2. post a message in general with an intro text, link to each support post

3. the posting time is to be dropped in a window from e.g. 12h + - 2h, which gives 4h window in which activity is identified

4. activity is to be identified every 30 min, with only the number of unique participants and not the number of posts. Polling every 30 min or on event count.

5. a threshold is to be set configurable on numbers that trigger the post

6. post a message in each of the unanswered suport posts that mention help has been asked.

if the windows of 4h runs out often without hitting the threshold, we can observe daily cycles and then define a new approach.

[wassfila]

Now that this repo is public, we can open up RFC discussions in here

[mandar1jn]

I understand the first 2 steps and the last one, but I'm struggling to comprehend the others

[wassfila]

OK, so I gave them numbers to be clearer, so I would say we split this in two stages

Stage 1, we only proceed with 1,2, 6, the ones that are clear and we replace 3,4,5 with a "Fixed posting time in the day"

Stage 2, we can alter the posting time with additional features.

Now regarding stage 2
Imagine I'm in charge of posting the message manually, I know I should post it around midday, but it could happen that at exactly 12:00 no one is there on the channel chatting, so what I would do, I'd rather "watch" the channel from 10:00 till 14:00 and keep counting how many are chatting. I'm not interested if one person posted 20 messages at 11:00 or let's say 2 persons posted 30 messages, that only count as 2, but if at some point 5 different persons posted 15 messages, that is more interesting.
So what I do, every 30 min, I check all messages e.g. from 10:00 till 10:30 and I extract the persons that posted all messages, if a person posted more than one message, all of the're messages are going to count only 1.
So I get e.g.

• 10:30 - 5
• 11:00 - 7
• 11:30 - 4
• 12:00 - 5
• 12:30 - 8
• 13:00 - 7
• 13.30 - 6
  It is helpful if we create passive stats days so that we have an idea what should be the number to trigger the post, e.g if I say I post if 10 persons are there, I would not have reached that number, if I say 6 is my trigger, then 11:00 would have been the time where 7 > 6. that is the parameter that could be configurable.

The "on event count" is a final optimization with which if let's say the new person from 10:30 till 11:00 that made the count reach 6, has posted exactly on 10:47, I would have reached count 6 on 10:47 triggered by that message post event, so I do nto need to wait till 11:00 to react, but post already right after that message that reached 6 users.