amrav
commented
4 years ago Haha, I read somewhere that it's good to set cron times to something random in the range you want, to avoid many expensive jobs running at the same Schelling point (eg on the hour). Not really an issue for us but seems like good practice.
Anecdotal aside: I've seen a system exceed capacity because some job scheduling web UI defaulted to midnight, and most users just went with the default.
On Sat, 27 Jul 2019 at 15:33, Siddharth Kannan notifications@github.com wrote:
@icyflame commented on this pull request.
In jobs/crontab https://github.com/metakgp/metakgp-wiki/pull/66#discussion_r307967059:
@@ -2,3 +2,4 @@
11 /root/update_top_trending.sh
- 1 /root/MetaMaint.sh +47 3 * /root/update_spam_blacklist.sh
Any specific reason for this time? If there is none, I think we should change it to something less specific, 00:01 or 01:00 sound like good times to me.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/metakgp/metakgp-wiki/pull/66?email_source=notifications&email_token=AAJBT73UMGUKNL643P26DSTQBRMEHA5CNFSM4IHJKYDKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB7YUPSQ#pullrequestreview-267470794, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJBT7YIXWZGZPWWD4D4RR3QBRMEHANCNFSM4IHJKYDA .
This extension checks edits against an updated list of spammer IPs across various forums, and prevents edits and account creations from those IPs.
Set up nightly cron job to update spam blacklist.
Ran locally and confirmed that adding my local IP to the blacklist prevented me from editing. Also confirmed that the update cron job works as expected.