Skip to content

Optional :entry-base-url feed property overrides base URL derivation#479

Open
kamidon wants to merge 1 commit intoskeeto:masterfrom
kamidon:entry-base-url-override
Open

Optional :entry-base-url feed property overrides base URL derivation#479
kamidon wants to merge 1 commit intoskeeto:masterfrom
kamidon:entry-base-url-override

Conversation

@kamidon
Copy link

@kamidon kamidon commented Jan 17, 2023

Bofore this commit, when displaying entries in
'elfeed-show-refresh--mail-style' a base URL would be inserted that was derived from the feed URL by removing any URL path and query parameters. However, some feeds are hosted on a different domain then the entries they reference. For example, the feed for kottke.org is on 'https://feeds.kottke.org/' while the entries are on just 'https://kottke.org/'.

This commit allows the user to override the derived base url for entries of a feed by specify an altenative base URL in the ':entry-base-url' property on the feed.

An alternative implementation that derived the base URL from the entry URL instead of the feed URL was considered but rejected because the entry URLs are controlled by the feed and following the entry URL from the elfeed UI requires a user action while the base URL for displaying embedded content in the feed data would not. With this solution the user explicitly acknowledges an additional location from which they are comfortable loading embedded content.

Bofore this commit, when displaying entries in
'elfeed-show-refresh--mail-style' a base URL would be inserted that
was derived from the feed URL by removing any URL path and query
parameters. However, some feeds are hosted on a different domain then
the entries they reference. For example, the feed for kottke.org is on
'https://feeds.kottke.org/' while the entries are on just
'https://kottke.org/'.

This commit allows the user to override the derived base url for
entries of a feed by specify an altenative base URL in the
':entry-base-url' property on the feed.

An alternative implementation that derived the base URL from the entry
URL instead of the feed URL was considered but rejected because the
entry URLs are controlled by the feed and following the entry URL from
the elfeed UI requires a user action while the base URL for displaying
embedded content in the feed data would not. With this solution the
user explicitly acknowledges an additional location from which they
are comfortable loading embedded content.
@kamidon
Copy link
Author

kamidon commented Jan 17, 2023

Resolves issue #476.

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

Successfully merging this pull request may close these issues.

1 participant