-
-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Labels
investigateStuff for R&DStuff for R&Dlow priorityIssue is not as important as othersIssue is not as important as othersmay cause issuesInvestigation is needed as implementation may break somethingInvestigation is needed as implementation may break something
Description
This is a double edged sword because checking for bans has a rate limit that may or may not be shared with other calls or shared between instances.
It kinda sucks. But it would allow us to potentially speed up initial import, and prevent some minor other reflows.
In terms of importance, I rather just drop it. Everything works fine right now with the cooldown/burnout operations. But it could be a nice to have? There’s too many unknowns to safely deploy something like this.
The branch check-bans covers most of the work already.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
investigateStuff for R&DStuff for R&Dlow priorityIssue is not as important as othersIssue is not as important as othersmay cause issuesInvestigation is needed as implementation may break somethingInvestigation is needed as implementation may break something