>>8116
>I'm sorry for this very brief post on this matter but I am currently busy with school.

don´t worry about that.As you have claimed, the archive group has had this (mostly) covered. I have been dealing with college exams as well this week.

>However this late discovery of this event made me think. Whether there could be any better ways to "detect" any potential "threats" like this as early as possible to gain maximum advantage.

well, unless that one sets up alarms in the way that mobile or message notifications work, I highly doubt that anything will beat the usual method of reporting it manually by opening a thread on /mlp/ or something that serves as a bait for seeking the attention to those happenings in a public manner.

>I was thinking of some RSS reader on steroids that would watch specific feed for specific keywords and it could launch other "actions" depending on the keyword located
that sounds neat.

>we would still be technically relying on other people to actually post the happenings, but it could be potentially very effective.
that would actually create a greater diffusion about the happening and even by doing so, it would increase the chances of getting reported on EQD and even other fansites (even though Seth has usually reported these occurrences, I am not sure why he hasn´t reported this event yet) while it also executes the actions automatically.

>The main problem that comes to mind would be to detect the correct keywords and filter out false positives as it directly affects effectivity.
that´s a tricky issue and there should be more parameters that are just specific for those cases.