"Original story could not be proxied" after logging in to website

[dostillevi]

Unexpected behavior when opening an article in Story mode

I default to viewing my articles in Story mode, but recently this has stopped behaving as expected. Here’s what I expect: I select an article from the site feed. The webpage of that article loads fully in the viewing panel. It should look something like this: [image] (note the story is still being fetched, more on that) Here’s what’s happening today: I select an article from the site feed. The site starts to load, but the crosswalk icon appears for text and story views on the bottom left…

I made the above post describing this same proxy issue.

Maybe the following behaviors would improve the situation:

1. The proxy appears to be failing when it isn’t actually failing (the story starts to load before I’m kicked back to text view). If the proxy is only partially successful, it could display that partial content.
2. If the proxy fails, the first fallback should be a direct load of the site rather than switching to text view (which is premium only, while direct load is not). I can get to the direct load state right now simply by clicking on story after the failed proxy, so I think making that the default fail state would be an improvement. Even better would be a fast-fail so the non-proxied site loads without a partial attempted proxy site appearing to the user (faster, fewer flashing/changing views as content loads).

For kicks I tried newsblur in private mode (firefox) and the behavior was the same, so I don’t think any of my privacy extensions are related to the issue I’m seeing.