-
Notifications
You must be signed in to change notification settings - Fork 23
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
livemarks uses alternate instead of primary URL for feeds #486
Comments
Well this is just a bad situation all around, not sure what we can do. Feedburner needs to keep working in any case. |
let's break it down. wallabag does this:
feedburner does this:
it also has Could we prioritize the plain I think this is fundamentally an interoperability problem between RSS (which doesn't specify a |
Feed URL
Please specify the feed URL: private URL, but an example would be:
This is a feed generated by Wallabag.
Add-on version
Add-on version: 3.8
Describe the bug
With the above feed, livemarks now links to (e.g.)
https://lib3.net/wallabag/view/38722
instead of the canonicalhttps://gitlab.torproject.org/groups/tpo/tpa/-/boards?scope=all&utf8=%E2%9C%93&state=opened
. This means an extra click to actually get to the article.This is, from my perspective, a regression that was introduced in response to #34, in 345156e, which deliberately prioritised the alternate links to "fix" feedburner feeds, but from my perspective, this is actually inaccurate: the "alternate" is a fallback, well, an alternative in any case... Certainly not the best link for wallabag!
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Before the above change, the bookmarks were pointing to the right place, which is the article itself, not the wallabag link.
Thanks!
The text was updated successfully, but these errors were encountered: