Recently, Alyosha and I have been working on console-verifications of GBA games, and Alyosha was able to verify all three of g0goTBC's DK: King of Swing publications, changing the pub flags and editing the pub description to link to the console-verification video. However, g0goTBC didn't realize this had occurred until I happened to mention it a few days later.
g0goTBC suggested it might be nice to have a notification or automated message when events like this occur, and I think this might be worth considering.
One thought is the system could report on major flag changes like adding the console-verification. It does sort of depend if we want to design the system to treat console-verification as particularly important; tracking pub changes/flag changes in general might get spammy if there were multiple consecutive changes, but there's also methods of feed management that could mitigate that.
I think this also can also apply to when old submissions get re-evaluated and re-judged. And perhaps judging status changes in general? It's fine to recheck submissions every so often, I guess, but it also means it's hard to be entirely up-to-date if you aren't specifically reviewing submissions regularly.
YoshiRulz
commented
10 months ago
Recently, Alyosha and I have been working on console-verifications of GBA games, and Alyosha was able to verify all three of g0goTBC's DK: King of Swing publications, changing the pub flags and editing the pub description to link to the console-verification video. However, g0goTBC didn't realize this had occurred until I happened to mention it a few days later.
g0goTBC suggested it might be nice to have a notification or automated message when events like this occur, and I think this might be worth considering.
One thought is the system could report on major flag changes like adding the console-verification. It does sort of depend if we want to design the system to treat console-verification as particularly important; tracking pub changes/flag changes in general might get spammy if there were multiple consecutive changes, but there's also methods of feed management that could mitigate that.
I think this also can also apply to when old submissions get re-evaluated and re-judged. And perhaps judging status changes in general? It's fine to recheck submissions every so often, I guess, but it also means it's hard to be entirely up-to-date if you aren't specifically reviewing submissions regularly.