I tried this frontend and liked it, but the next time I went there I just got that spinning hypercube animation endlessly, with no other UI to interact with. Is there a forum to discuss that frontend or something?
Can you hit f12, go to the console tab, and grab any errors being reported there?
This is on mobile, so, not really. It seems to work on desktop.
Can you try now? I just bumped to the latest version.
I’m still getting the issue, but it seems to be specific to Firefox on Android. Chrome works, I’m just trying not to use that anymore. But I guess this is mostly a “me” problem. Thanks for your work on it, though! I’ll just stick with the old interface for now.
Hmm I can’t reproduce on firefox android. Can you try clearing your cache?
Oh, sure enough, that fixed it. I only cleared “cached images and files” and it loaded right up. Thanks!
I just love how much choice we have for how to view Lemmy. Tesseract looks pretty nice!
Its got the community search on the left column subscription list just like how old reddit with res did.
Yeah, I like that. Helps you keep up with smaller communiities that you enjoy but their content may not have a far reach.
Top tier admins. Thanks for all you do!
Not sure if this is on your as admins or on the tesseract devs, but my blocked users appear to get through on that UI (the lemmit bot)
I noticed that too but haven’t dug into it yet. I would guess it’s a tesseract bug since that’s not anything I configure.
Just rolled out 1.4.30 which should fix this issue. The data snapshots are now keyed to the active profile ID when they were fetched.
Updated!
Thanks
You’re all doing awesome as admins BTW
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.
That might be what happened, now I’m not seeing any of those posts.
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.
