If my figuring is correct, we have now officially reduced the review queue to half of what it was at its peak (Sept. 7). We burned through 12,800 (and counting) reviews in 8 days.
@Mast Congratulations! You are now a blacklist manager. You should run !!/amicodeprivileged to verify and force SD to update its cache of permissions. You may need to do that on each instance, depending on when they update their cache. Do you have a GitHub account? If so, please provide me with enough information to find it, so I can invite you to join the OAP team in the Charcoal-SE organization.
@Daniil If it contains a user and an MS link, then it's to that related link. If it doesn't have one, then it's to the most recent Smokey report, yeah.
user435118
@thesecretmaster Can we have additional autoflagging configurations for specific reasons? i.e. I wouldn't mind an autoflag if one of the reasons was 100-weight no matter the weight or other reasons.
@Daniil It could technically be a race condition now that the account that sends those messages are split in two. If Smokey reports a new report before MS has a chance to send the LAST report's "feedback received" message, then I guess it could be staggered.
@Daniil If it doesn't have links, then it's to the report which MS thought was most current at the time which it generated the message. Due to timing issues, that may not be the most recent report posted in chat.
@Daniil Well, there are actually two different ways to get it from the WebSocket. Personally, I suggest the newer WebSocket interface, as it provides more information. However, with that interface, when a feedback is created, you'll often get both a "creation" and an "update" message, both for the same feedback.
@Daniil Both use the same URL for the WebSocket in the documentation. In order to get the new events, I found that the following JavaScript worked for what to send once the WebSocket was open in order to get creation, update, and destroy events for feedbacks:
@RyanM Trial by fire in current job. Passing JSON around pays the mortgage. :) But I'd probably be faster spinning that up as a Java object and using Jackson to turn it into JSON to send to a socket....
@Mast You're welcome to post it where ever you'd like. If you're added to the team, that will be semi-public information (actually only available to other team members, IIRC). So, if you want to send it to me via Keybase, that will keep some privacy, I think. It's not something which I've really looked at wrt. keeping a GitHub account private, as anything you do with the account on the team will be public. SO users commonly put a GitHub link in their profile.
In other words, if you're concerned about privacy for a GitHub account, I'd suggest doing some research, as I haven't looked at it from that POV.
user435118
@Makyen So what am I actually doing? Listening to the socket? Subscribing to it?
