Hi, sorry about the delay. It’s not looking likely, as that Story pane is a proxied version of the original website, which means cookies won’t work. This came up again earlier today as it seems folks do want to have that view do something different.
Here’s the issue. Right now that view uses a local proxy to ensure the content gets delivered. I can switch back to a non-proxied view that would allow you to login and it would work, but that would probably have to be an advanced preference. It’s certainly not the right answer for everybody, which is why the default is to use the special NewsBlur proxy.
I’m having this response on most of the webcomics sites I visit (if not all) in Story mode, it has little or nothing to do with logging in on those sites. Not sure if it’s really related, or if I should make a new topic?
I’m getting the “could not be proxied” error for every feed I chose to see in “story” view, it started a week ago or so. The affected feeds are almost exclusively comics, so definitely no login cookies involved.
The behavior is like this: I select an item, it starts displaying in the story view (I even have enough time to read the contents sometimes), then the error appears and the view changes to “text”. Clicking “story” after that shows the “story” view for the item as if nothing happened and does not error out again.
I made the above post describing this same proxy issue.
Maybe the following behaviors would improve the situation:
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.
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.
Also, while I don’t claim to really understand the proxy use-case, doesn’t proxying run the risk of showing an outdated version of the article content? One of the nominal benefits of story view is seeing the present state of the article instead of the content pushed via RSS.
This happens on all feeds, regardless of what needs logging in. I don’t default to story view, but when I double click a feed, I expect it to jump straight to story view rather than auto-load into text mode like it did before this started happening in December.