@Rob I'm really not sure what you were attempting to do with the !!/watch you posted. Regexes that are added via !!/watch are checked against post content, post titles, and usernames (be very careful with watches you add intended for usernames, as they tend to catch multiple users). Were you trying to have us look at everything that user posts? If so, the way to do so is to add the user to the user-blacklist. You can do that with the !!/addblu command.
@Undo Also, while I'm here, do you think I should swap my current pinned message for one asking people to test /search_fast? Seems like there aren't any bugs with the rest of the redis stuff, and I want to fully migrate over to /search_fast..
@JakeSymons If they say they copy-&-pasted it, then it's not plagiarism. Plagiarism is presenting work done by someone else as your own, either intentionally or by just forgetting to credit the source. In academia, there is also a concept of self-plagiarism, as there are contexts where you really need to note that you are copying from earlier work done by yourself.
@Makyen OK, I noticed that there was one user whom posted a NAA with the URL you were concerned about at the end of her post. My intention was to watch for that user with slightly more weight and check everything they post since they made a first post with an URL that was of concern to you. Also that site is part of the Amazon Referral Network and doesn't permit spamming. That is why I specifically left a message for you, but others read it and wished to act upon it, decided they
couldn't understand their intercepted message or know the background of your reasons and cancelled the PR.
@ThomasWard Cool. Sounds good. Hopefully it does behave. :-) Given that the other instances reacted the same as Solar wrt. not recovering from MS downtime, I don't think that's a problem with Solar's config. It seems much more a general SD issue.
