the-voidwalker / proxyhammer Goto Github PK

Some user actions will take too long to be stuck behind an infinitely pending post request. These actions should instead launch jobs. Some requirements:

• Certain tasks must be unique (can't start a new one until existing ones finish)
• Status or monitoring (doesn't have to be live, but certainly upon completion)
• Should support:
  • One off tasks
  • Scheduled tasks
  • Repeating tasks

Some occasional verification (or other pre-check) to determine that IP addresses the database thinks are blocked are actually blocked on Miraheze is required. In essence, a pruning operation.

Current idea is setting a block_expires field to the IPRange model and then purging expired ranges. Should this operation purge entries from the database entirely? If the range isn't in the latest enwiki or global lists and it expires, then purge?

• Individual IP ranges
• Individual ASN
• List of IP ranges by ASN

• Remove secret key from git and review other deployment checklist items
• Consolidate migrations into a single file
• Validate requirements.txt is up to date (ipwhois may be removed?)
• Properly build up readme and info pages

Scheduled blocks currently don't do anything. A utility to process those using a mediawiki bot account is therefore required. It should both be added to the tools page for manual running, and there should be some option for scheduled execution.

Importing Void-bot seems like the simplest and best idea.