Is it just me?

My hot it full of months, or even years old posts that have almost no upvotes or comments. Why are they there?

And unlike actually “hot” posts they don’t seem to want to go away. Is this a bug? I’m not seen any discussion on it, not even on github.

  • ttalikka@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    9
    ·
    3 years ago

    Yeah, just recently saw a news article pop up in my Hot feed which stated that “Canada finally starts requiring a negative COVID-19 test to enter the country”. Weirded me out for a moment before I realized that the post was over two years old :)

  • poVoq@slrpnk.net
    link
    fedilink
    English
    arrow-up
    5
    ·
    3 years ago

    Its a known bug and 0.18 already improved it a bit. O.18.1 will hopefully fix it completely. For now the instance admin can restart the Lemmy backend to renew the stalled hot sorting.

    • MentalEdge@sopuli.xyzOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      3 years ago

      This ain’t that. Before it would freeze entirely and keep the same posts for days.

      Now, it’s updating, and showing brand new posts, but also posts from YEARS ago.

      • poVoq@slrpnk.net
        link
        fedilink
        English
        arrow-up
        4
        ·
        3 years ago

        Yes I am aware, but I talked to one of the developers and apparently it has the same root cause.

        And I can definitly see that restarting the backend temporarily fixes it.

  • FuyuhikoDate@diggit.xyz
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 years ago

    I realized the Same with pinned posts! It depends on the sort order, But the pinned posts are then always on top. Whish i could just hide those ^^

  • vacuumpizzas@t.bobamilktea.xyz
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    3 years ago

    Upgraded the UI to 0.18.0-rc1 and the backend to a few commits ahead of 0.18.0-rc1. I haven’t seen this issue so far today.

    And I just got a 14 day-old post. So it seems like the issue is still there.