Continues monitoring dead "archived" threads on 4chan

[Elevon]

4chan recently started no longer immediately 404ing dead threads on some boards, instead "archiving" them for 48 hours. CTW does not distinguish between live and "archived" threads, so it continues to use resources checking dead threads for new posts. On fast-moving boards this multiplies the number of monitored threads significantly, and I've started manually stopping dead threads to stop memory usage from getting out of hand. Obviously CTW should stop monitoring archived threads automatically.

[SuperGouge]

The actual behavior is that watchers are automatically stopped on error (404, IO Error, etc.). The problem with stopping these new archived threads is that they are not 404 and someone might still want to archive them locally when stumbling upon them.

Also, those board-specific behaviors are tricky to implement properly as of now when they don't consist of only HTML parsing. This is something I am thinking of improving as well as the whole board-specific management since those particularities are increasingly more feature-breaking.

However, I am open to ideas on if and how these new particular "thread states" should be dealt with.

[dingydingo]

Why not make it so it downloads the thread once then stop it, rather than having it watch a thread that can't be updated anymore?

[ffgandalf]

Why can't you do it with HTML parsing? 4chan appends "Thread archived.
You cannot reply anymore." At the top of archived threads?