Return to Question

The information that is tracked are edits, suggested edits, close votes, reopen votes, deletion by the system (a.k.a., the roomba) and deletion by users. Since the API does not return deleted questions, the tracking logic considers a question is deleted when it is not returned by the API anymore. To distinguish between a manual and a system deletion, it performs a best guess based on the roomba logic.

Closed: Codeigniter on Godaddy results in 404 removing index.php, GoDaddy issues with directory (differences with "webroot" and "root"), godaddy shared hosting NICE command path and PHP path.

The bot runs under the user Burnaki and sits 24/7 in SOBotics chat room.

The information that is tracked are edits, suggested edits, close votes, reopen votes, deletion by the system (a.k.a., the roomba) and deletion by users. Since the API does not return deleted questions, the tracking logic considers a question is deleted when it is not returned by the API anymore. To distinguish between a manual and a system deletion, it performs a best guess based on the roomba logic.

Closed: Codeigniter on Godaddy results in 404 removing index.php, GoDaddy issues with directory (differences with "webroot" and "root"), godaddy shared hosting NICE command path and PHP path.

The bot runs under the user Burnaki and sits 24/7 in SOBotics chat room.

The information that is tracked are edits, suggested edits, close votes, reopen votes, deletion by the system (a.k.a., the roomba) and deletion by users. Since the API does not return deleted questions, the tracking logic considers a question is deleted when it is not returned by the API anymore. To distinguish between a manual and a system deletion, it performs a best guess based on the roomba logic.

The information that is tracked are edits, suggested edits, close votes, reopen votes, deletion by the system (a.k.a., the roomba) and deletion by users. Since the API does not return deleted questions, the tracking logic considers a question is deleted when it is not returned by the API anymore. To distinguish between a manual and a system deletion, it performs a best guess based on the roomba logic.

The information that is tracked are edits, close votes, reopen votes, deletion by the system (a.k.a., the roomba) and deletion by users. Since the API does not return deleted questions, the tracking logic considers a question is deleted when it is not returned by the API anymore. To distinguish between a manual and a system deletion, it performs a best guess based on the roomba logic.

• When a question has been closed. The goal is to ensure the question gets attraction for a potential inappropriate close.
• When a reopen vote is cast on a closed question. This means that the question was potentially wrongly closed during the effort and needs to be re-reviewed.
• When an edit is made to a question removing the tag being burninated. This helps to track which questions were edited and potentially act on wrong edits or users on an edit-spree.
• When a question is deleted. In the same way as closed questions, the goal is to make sure the question gets another review.
• When a question is undeleted. This means that the question was wrongly deleted and needs attention. NOTE: the Stack Exchange API does not return deleted posts, so it is not possible to raise a notification when an undelete vote is cast.
• When a new question is posted.

The bot runs under the user Burnaki and sits in SOBotics chat room.

This application is currently in testing phase. Still, all of the features above are implemented and work correctly.

The information that is tracked are edits, suggested edits, close votes, reopen votes, deletion by the system (a.k.a., the roomba) and deletion by users. Since the API does not return deleted questions, the tracking logic considers a question is deleted when it is not returned by the API anymore. To distinguish between a manual and a system deletion, it performs a best guess based on the roomba logic.

• When a question has been closed. The goal is to ensure the question gets attraction for a potential inappropriate close.
• When a reopen vote is cast on a closed question. This means that the question was potentially wrongly closed during the effort and needs to be re-reviewed.
• When an edit, or a suggested edit, is made to a question removing the tag being burninated. This helps to track which questions were edited and potentially act on wrong edits or users on an edit-spree.
• When a question is deleted. In the same way as closed questions, the goal is to make sure the question gets another review.
• When a question is undeleted. This means that the question was wrongly deleted and needs attention. NOTE: the Stack Exchange API does not return deleted posts, so it is not possible to raise a notification when an undelete vote is cast.
• When a new question is posted.

The bot runs under the user Burnaki and sits 24/7 in SOBotics chat room.

This application is currently in semi-production phase. All of the features above are implemented and work correctly, apart from suggested edits that needs further thought (with regard to API quota).