Some sort of a overlay check should be done over recently "closed"/no longer in API response zones (seems like 10m or so would generally be enough based off these ones at least), to see if some percentage of the new outage fits within the previous one and consider it split if so, and make its initial post note that, and be a reply to the previous outage.

Implications to consider:

Should small outages that were a part of the previous medium/large one get posted?
Should the child outages also carry the parent's hashtag?

It looks like SCL will split an outage into seperate ones, I've captured what appear to be a couple below: ### Haller Lake (161138) Original Outage: https://mastodon.gruezi.net/@seattlecitylight_bot/111775679138888604 Split parts: - https://mastodon.gruezi.net/@seattlecitylight_bot/111775973867011673 - https://mastodon.gruezi.net/@seattlecitylight_bot/111775974141765649 ### Chinatown/International District Original Outage: https://mastodon.gruezi.net/@seattlecitylight_bot/111775128567022107 Split parts: - https://mastodon.gruezi.net/@seattlecitylight_bot/111775325101170110 For both of these, there were almost certainly smaller outages within the original large event zone that just didn't get posted about. Some sort of a overlay check should be done over recently "closed"/no longer in API response zones (seems like 10m or so would generally be enough based off these ones at least), to see if some percentage of the new outage fits within the previous one and consider it split if so, and make its initial post note that, and be a reply to the previous outage. Implications to consider: - Should small outages that were a part of the previous medium/large one get posted? - Should the child outages also carry the parent's hashtag?