Skip to content

Check if banned before banning on import #98

@SocksTheWolf

Description

@SocksTheWolf

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    investigateStuff for R&Dlow priorityIssue is not as important as othersmay cause issuesInvestigation is needed as implementation may break something

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions