wallabag / wallabag/wallabagger

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

Open
#366 0 comments 3 reactions 0 assignees View on GitHub
enhancement
Dominant language
JavaScript
Stars
471
Forks
71
Avg merge
4d 17h
Merged PRs (30d)
4

Description

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.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.