reporting broken article when it can't be read by the extension

[mircealungu]

this morning i was recommended this article:

2546441

however, i didn't "save" first, but went to read it with the extension.

the extension can't read it:

two things to do:

1. investigate why did this one escape our paywalled filter

2. make sure that when we detect an "unreadable" article in the extension, we automatically update the article to broken. there is no doubt at this point that from our POV, this is a broken article.

[tfnribeiro]

You can see this article was from the 19 aug. so it was after the content removal change but before we deployed the fix to continue to filter out these article (4 days ago, 23 aug). This shouldn't occur again now.

Though I guess if we ever detect a failure to read the screen with we could report a broken article to the API and the reason it wasn't loaded + the fact it was from the extension rather than Crawler/user