Anyone else having trouble with links not showing as read? (sh.itjust.works)

submitted 1 month ago by jballs@sh.itjust.works to c/main@sh.itjust.works

6 comments fedilink hide all child comments

I've been using Sync for Lemmy for a year or so, but very recently (within the last day or so) links have stopped showing as read when I click on them and then go back. I tested this with a lemmy.world account and don't have the same problem.

I saw a post saying sh.itjust.works was updating to Lemmy v19.5 a few days ago. I'm wondering if maybe it caused a problem or if it's just me having this issue.

Thanks

top 6 comments

sorted by: hot top controversial new old

[-] kersploosh@sh.itjust.works 11 points 1 month ago* (last edited 1 month ago)

It's a known bug in Sync with Lemmy 0.19.5:
https://github.com/laurencedawson/sync-for-lemmy/issues/539

lemmy.world is still on Lemmy 0.19.3.

[-] bobagem@sh.itjust.works 5 points 1 month ago

For greater clarity, it's an issue with Sync for Lemmy continuing to use an API parameter that was formerly deprecated and now entirely removed from Lemmy.

Sync for Lemmy is identifying a post that needs to be marked as read using a single value parameter, but it should use a slightly different parameter that could accept multiple posts.

[-] jballs@sh.itjust.works 2 points 1 month ago

Ah that explains it. Thanks!

[-] bobagem@sh.itjust.works 2 points 1 month ago

Just found this post. Copying and pasting a comment I made elsewhere:

I just started having this problem in the past few days after it working for a long time.

I've cleared all my data and reset all my settings. On the web I have it set to not show read posts. In the app I haven't set to mark read on scroll. And to show read posts as dimmed.

But no matter how much I scroll nothing gets dimmed, and when I refresh everything is still there.

[-] jballs@sh.itjust.works 3 points 1 month ago* (last edited 1 month ago)

Yeah if you look at that GitHub link in the other comment, it mentions that a Lemmy variable was renamed in the latest release. So there's nothing that we, as users, can do. It needs a code change.

Edit: Didn't see your other comments. Looks like you already understood the issue.