Most entries in lemmy’s RSS feed have a <link> that points to the relevant lemmy post eg

Title: Any DE or distro without touch support?
Author: https://lemmy.ml/u/tarius
Date: Wed, 15 May 2024 01:24:59 AEST
Feed: Lemmy - linux
Link: https://lemmy.ml/post/15632012

That makes sense - clicking the link takes me to the conversation.

Other entries however, include a link to the subject of the conversation eg

Title: Wayland usage has overtaken X11
Author: https://lemmy.world/u/KISSmyOSFeddit
Date: Tue, 14 May 2024 03:30:46 AEST
Feed: Lemmy - linux
Link: https://lemmy.world/pictrs/image/a71c1b49-fb63-420d-8afc-d40661ffd79c.png

The feed I’m using is https://lemmy.ml/feeds/c/linux.xml

This is unfortunate as clicking the link in my reader (elfeed) does not show the conversation - I rely on the <link> to take me there.

elfeed being built in elisp in emacs, I have been able to concoct a fix especially for lemmy - but it really feels like a bug in lemmy as no other feed needs it. Where can I report it or discuss it?

  • Andrew@piefed.socialEnglish
    0·
    7 months ago

    That’s arguably the expected behaviour - for a discussion, ‘link’ effectively takes you to the comments, for an article (or a link to a image), it takes you there instead.

    You could use ‘guid’ instead - that always links to the post on Lemmy, and it usually contains a useful thing on other sites’ RSS feeds.

    • StrangeAstronomer@lemmy.mlOP
      0·
      7 months ago

      It might be more expected for you but I’m going to differ.

      for an article (or a link to a image), it takes you there instead.

      … and then you can’t get to the discussion.

      The RSS-2.0 definition of <link> is

      The URL to the HTML website corresponding to the channel.

      so clearly, it should point to the lemmy post. No other RSS feed that I know of has this problem.

      Fortunately, emacs can flex around this, but duh! Where can I raise a bug report?

    • StrangeAstronomer@lemmy.mlOP
      0·
      7 months ago

      I followed up on github as you suggested and a very nice young man took a look at it and said that the code already does work the right way (at least the way I and their little poll think it should work). But, it turns out that the fix (from 2021) has not been deployed - it’s to be in the next release.

      So I don’t know what will happen now - I’ll continue to use my workaround, so I’m happy enough.