• Admiral Patrick@dubvee.org
    link
    fedilink
    English
    arrow-up
    5
    ·
    18 hours ago

    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.

      • Admiral Patrick@dubvee.org
        link
        fedilink
        English
        arrow-up
        6
        ·
        16 hours 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.