There was a last minute hick up during the tip scans yesterday. I thought I would share what happened, specially with our admins including
@Bugsam, to avoid any misunderstanding.
Last week I posted a detailed post about the variations of acceptable and non-acceptable tip headers. A few hours later, the post was moderated upon my request. Moderation was necessary, otherwise the scanner would have easily misread that post as a tip. This has worked well before when
@ammie asked to moderate some of her posts to avoid confusion.
However, this time, the program stopped at my moderated post. The reason was, when I run the scans while I am logged in, the moderated post is still visible to the program (because, I am the author of the post). Some code changes could have fixed the issue, but I did not want to take any risks. So I did a quick fix - created another account, just to continue the scans. I knew that this may be against the HC rules, but that was the quickest way I could fix the issue and move forward. After running the scans with the newly created account, I thought I can continue to use this account for scanning purposes from now on, so I will not have to change any codes specifically to tackle my own posts.
A few hours later I received an email from HC saying that the new account is rejected, whilst advising that this account can only be used as a read only account. Now, a read only account will be more than enough for scanning purposes as long as it is not against the HC rules. I also do not want my original account affected by this action.
Hope admins will understand the situation. Just thought to share this here for transparency.
Cheers, CC
(20min delay)