this post was submitted on 28 Jun 2023
56 points (96.7% liked)

Lemmy

12542 readers
28 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.

founded 4 years ago
MODERATORS
 

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.

top 23 comments
sorted by: hot top controversial new old
[–] ttalikka@sopuli.xyz 13 points 1 year ago (1 children)

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 :)

[–] Macawesome75@sh.itjust.works 2 points 1 year ago

I've been keeping on getting one for the itch io ukraine bundle, which was over a year old

[–] Sibbo@sopuli.xyz 7 points 1 year ago (1 children)

At least was a bug. If a post for whatever reason is requested again from another instance, then it would be inserted into the database with a very high hot score, as if it was a new post. But I thought that was fixed.

[–] MentalEdge@sopuli.xyz 3 points 1 year ago* (last edited 1 year ago) (1 children)

Indeed, that github issue is closed.

I'm not sure this is that, though.

[–] thal3s@sh.itjust.works 3 points 1 year ago

That doesn’t mean it’s been deployed yet.

[–] poVoq@slrpnk.net 6 points 1 year ago (2 children)

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.xyz 3 points 1 year ago (1 children)

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 4 points 1 year 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.

[–] anthr76@lemmy.kutara.io 2 points 1 year ago (1 children)

I'm on 0.18.1-rc.1 and I'm still seeing it.

[–] poVoq@slrpnk.net 2 points 1 year ago* (last edited 1 year ago)

Hmm, better make a specific bug report then ASAP.

[–] aski3252@lemmy.ml 3 points 1 year ago (1 children)

The sorting algorithm seems like it needs a bit of work. I don't have the issue that I see month old posts, I tend to see very new and not very upvoted posts instead, but that's fine with me. I just saw your post on hot near the top page, for example.

[–] MentalEdge@sopuli.xyz 1 points 1 year ago

I do get new and actually upvoted posts, but there's a bunch of older stuff sticking around, and they seem to do so longer than other stuff.

[–] bionicjoey@lemmy.ca 2 points 1 year ago (1 children)

Use Top Day or something with even less time like Top 6 hours if you want fresh posts.

[–] MentalEdge@sopuli.xyz 3 points 1 year ago (1 children)

I would, not yet available in thunder, so only on desktop for now.

[–] bionicjoey@lemmy.ca 2 points 1 year ago (1 children)

I've been using Lemmy in browser and ìt works decently well

[–] imaqtpie@sh.itjust.works 1 points 1 year ago

Same. Top 6 hours is my jam. Occasionally switch to Top hour or Top day

[–] Stanley_Pain@lemmy.dbzer0.com 2 points 1 year ago (1 children)

Had the same problem but 0.18 fixed it for me.

[–] MentalEdge@sopuli.xyz 3 points 1 year ago* (last edited 1 year ago) (1 children)

My instance is on 0.18. Was among the first to update.

[–] Stanley_Pain@lemmy.dbzer0.com -1 points 1 year ago

Oh wow that's weird. When my instance switched to the new version that problem went away for me.

[–] Fuyuhikodate@diggit.xyz 2 points 1 year 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 1 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] admin@lemmy.magnor.ovh 1 points 1 year ago (1 children)

I think that as long as the instances you scrape from have not updated, the bug will remain.

Ah that’s good to know. I suppose this is a reasonable limit to what I gain by living on the bleeding edge.

load more comments
view more: next ›