-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a separate program/process to scrape election status on all network sites #60
Labels
feature
Features and enhancements
Milestone
Comments
This was referenced Aug 17, 2021
Election chat rooms can be automatically created by CMs and linked on the election page; announced here Automatically create a chat room Just need to figure out the correct selector for the bot, if it needs changing. |
Looks like the selector (line 167, election module) still matches the chat room URL, just checked that on an election page - so I think we are all set here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, the setting up of this bot is done manually by changing environment vars in Heroku:
If we can create a program to scrape all network sites' election pages, and store the status in a persistent database, we could potentially use this to automatically spin up a new instance for that site if a scheduled election is detected (usually the announcement on per-site meta comes later, although they are automating the election process - so look out for changes).
Maybe we don't need to find/scrape default chatroom urls for each site, since that is unlikely to change. The list can be fetched from https://api.stackexchange.com/docs/sites#filter=default&run=true, and the room with the most users & messages should be the default (e.g.: https://chat.stackexchange.com/?tab=site&sort=people&host=serverfault.com).
But it would be nice for the bot to detect the election chat room if there is one, using the following methods (in order):
The text was updated successfully, but these errors were encountered: