this post was submitted on 31 Jan 2025
63 points (98.5% liked)

Lemmy.ca's Main Community

2988 readers
34 users here now


Welcome to the lemmy.ca/c/main community!

All new users on lemmy.ca are automatically subscribed to this community, so this is the place to read announcements, make suggestions, and chat about the goings-on of lemmy.ca.

For support requests specific to lemmy.ca, you can use [email protected].


founded 4 years ago
MODERATORS
 

Hi everyone!

Tesseract is now available as an alternative front end at https://tess.lemmy.ca/

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 5 points 2 weeks ago (1 children)

Yeah, I can't seem to reproduce that. Was it right after you logged in?

My only theory is that the initial post feed came in unauthenticated (which wouldn't have any blocks), you logged in, and then the main feed was still cached from the initial load.

Try just refreshing the page to refresh the feed and/or opening it in another tab. I'm currently waiting on approval to setup an account on lemmy.ca to see if I can reproduce it there. I tested on 0.19.7 and below, and the blocking all works as expected.

[–] [email protected] 5 points 2 weeks ago (1 children)

That might be what happened, now I'm not seeing any of those posts.

[–] [email protected] 6 points 2 weeks ago

That's the only thing I can think of that might cause that since the blocking is all API-based, and it doesn't return content for blocked users (and Tess can only show what the API returns).

Assuming that is the case, I'll add a step to clear the feed snapshot/cache when logging in. It already does keep separate snapshots when you switch accounts, but it doesn't clear the initial unauthenticated one when you log in for the first time.

Thanks for reporting that as it's not a case I've tested for.