Optimize message handling in memes#215
Draft
iN1PE wants to merge 1 commit into
Draft
Conversation
|
Author
|
I forgot to include the following exhibit B when drafting the PR. 
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Based on a thorough statistical analysis of historical deletion events, and as outlined by the community (exhibit A), I have determined that waiting for the community to react to XiRLord's posts in #memes is an unnecessary use of everyone's time.
The outcome is, at this point, a foregone conclusion. XiRLord posts something, everyone reacts with ♻️, it gets deleted. Every, single, time. Without fail.
So this PR streamlines the process by skipping the reaction phase entirely. XiRLord's messages are now dead on arrival when posted in #memes.