Global message delivery/Instructions
Global message delivery is getting a makeover! Check out this note for further information.
- Access list — make sure you're listed here
- Update the "Spam" page appropriately.
- The key is a unique string. It ensures that in case the bot has to restart (due to a Toolserver hiccup or an API hiccup or whatever), people will not receive the same message twice. The string can be anything, but for simplicity's sake, just add one to the current count. If you have to restart the bot because for some reason it didn't work (e.g. because the target wasn't in the correct format), you still have to change the key.
- At present it is a four-digit number, the simplest thing to do is to increment it.
- Follow the guidelines at Global message delivery.
- The key is a unique string. It ensures that in case the bot has to restart (due to a Toolserver hiccup or an API hiccup or whatever), people will not receive the same message twice. The string can be anything, but for simplicity's sake, just add one to the current count. If you have to restart the bot because for some reason it didn't work (e.g. because the target wasn't in the correct format), you still have to change the key.
- Update the bot's "Status" page to "Start". The bot's current status is: Completed run successfully.
You may want to watch the status page as well. If there is an error or some sort of issue, the bot will (perhaps) update the status page with a description of the problem.
When working on multiple projects, you can use this or this tool to check where the bot has run. If the Toolserver lag is too high, the linked Toolserver tools won't be reliable. You can try to keep track of the bot's global editcount instead (good luck).
If you're sure that you'll not send duplicate messages, you can set the status page to "Really start" instead of "Start", overriding the key check. The bot will check the key on each page and will skip the pages that already have a message with the same key.