Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fallback to fetching content from browser if server-side fetch fails #366

Open
meonkeys opened this issue Aug 25, 2023 · 0 comments
Open

Comments

@meonkeys
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant