You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature idea: if the usual server-side article fetch fails, fall back to fetching content from the browser. In other words: gracefully degrade content fetching so it automatically / intuitively works in more situations.
This relies on the API telling us when a server-side fetch fails. Is that supported?
Are there also "soft" failures to worry about (like, where the server-side fetch appeared to work but fetched no content or broken content)?
Ideally configurable per domain name / base URL (similar to the existing "content fetching from the browser" option in preferences).
Another idea would be to have a hotkey or other user-controlled UI/UX to fetch content from the browser so it can be done manually. I usually click through to double-check added content anyway.
The text was updated successfully, but these errors were encountered:
Feature idea: if the usual server-side article fetch fails, fall back to fetching content from the browser. In other words: gracefully degrade content fetching so it automatically / intuitively works in more situations.
This relies on the API telling us when a server-side fetch fails. Is that supported?
Are there also "soft" failures to worry about (like, where the server-side fetch appeared to work but fetched no content or broken content)?
Ideally configurable per domain name / base URL (similar to the existing "content fetching from the browser" option in preferences).
Another idea would be to have a hotkey or other user-controlled UI/UX to fetch content from the browser so it can be done manually. I usually click through to double-check added content anyway.
The text was updated successfully, but these errors were encountered: