Feedbin's parser seems to choose the first available link element for the entry in the feed. I believe that's wrong. Atom by design allows multiple <link> elements per entry, distinguishable per rel, type and hreflang attribute. Not to discriminate between them is not ideal. For a backlink/permalink of the blog post per spec a <link> element with rel="alternate and possible a type="text/html is used.
The same bug occurs in Reeder with Feedbin as backend. Perhaps Feedbin propagates the false URL via its JSON API?
A feed in question is https://blog.whatwg.org/feed (gist copy).
While clicking the title of the newest entry of that feed in Feedbin web view to load the original page, Feedbin wants to send me to https://blog.whatwg.org/improving-interoperability/feed. Which itself is a feed of the comments of the blog post, the original post is at https://blog.whatwg.org/improving-interoperability/.
The WHATWGs Blog uses the Atom Threading Extensions which results in two
<link>elements in the feed:Feedbin's parser seems to choose the first available link element for the entry in the feed. I believe that's wrong. Atom by design allows multiple
<link>elements per entry, distinguishable perrel,typeandhreflangattribute. Not to discriminate between them is not ideal. For a backlink/permalink of the blog post per spec a<link>element withrel="alternateand possible atype="text/htmlis used.The same bug occurs in Reeder with Feedbin as backend. Perhaps Feedbin propagates the false URL via its JSON API?