this post was submitted on 21 Jan 2025
2 points (100.0% liked)
Tesseract
72 readers
4 users here now
Tesseract: An Advanced Lemmy Client
The goal of Tesseract is to address as many things in Lemmy that annoy me as I can. I also trawl various "is there any way to [blank] in Lemmy?" posts to get feature ideas. Both of those lists are pretty extensive, so Tesseract has accumulated quite a few features.
Github: https://github.com/asimons04/Tesseract/
Hosted / Demo Instance: https://tesseract.dubvee.org/
Note that the hosted instance defaults to Lemmy World, but it is unlocked to be able to connect to any Lemmy server.
Announcements, support, and guidance for the Tesseract UI.
All instance rules apply here. Beyond that, just be civil and constructive.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
One possible cause is that in the last few versions, I changed the crosspost rollup behavior so that it checks for crossposts against the whole feed and not just the current batch So a post may come in, but there's already a matching crosspost in the feed above, so it folds into that and "jumps" a bit as that one briefly appears and disappears (I'm aware of that, but it's not been too frequent of an issue).
A whole batch seems too much for that to be the cause, but it is possible.
If you scroll back up and see that some posts suddenly have crossposts listed, then that could be the cause.
If so, then I guess I can revert that to just checking for crossposts within the current batch and deal with seeing more duplicate posts.
Another possible cause could be something interrupting the fetch but the page cursor gets out of sync?
Not sure what to ask to dive deeper into those without being able to see it, but maybe I can replicate the behavior somehow.
I can probably test with the hosted instance, but just trying to get as much info as I can.
I just had a jump and checked: No crossposts on them. It was in the "all" feed with "scaled" in "hybrid" mode. Here is a video of all the jumped posts: https://imgur.com/a/PgSRhud The jump was from the PlayStation post to the Formula1/Ukraine post.
Yes.
Although feddit.org has an instance, I'm using my own selfhosted instance though podman.
I'm using Hybrid. I have the feeling it happens with unseen, hence expanded, posts though.
Yes.
Ok, thanks (to both replies). I'll match my settings and see if I can reproduce that.
With the confirmation that it's probably not rolling them up as crossposts, the only thing I can think of is it may be missing a page cursor or something?
How fluent are you with the browser dev tools? Would you be able to open those, put it on the network tab, and filter for "XHR", scroll through, and see if any API requests fail when you experience one of the jumps?
Also, what about any of the feed options? Any of those set? I don't think they'd make a difference for this, but since I'm grasping at straws at the moment, it would at least be handy to know I guess.
Other suggestions:
Disable media embeds in the feed and see if that is the issue; you can still see the embeds in the feed, but you'll have to click the thumbnail to load the iframe with the media. Always showing iframes has been mostly deprecated for a while now, and in the next release (1.4.30), those are actually going away with everything being click to play. The reasoning is in the changelog, but in short, it makes a huge improvement in performance and memory utilization.
I still have the previous "jump" session open and continued using it for your debugging proposals:
I'm not sure the jumps I see now are the same. I now reach the bottom of the site and then the batch loads and then the jump happens over that batch. In my previously encountered jumps I was not at the bottom of the site. Please keep this in mind for the following answers:
No failing requests. All are green 200 and 204. Jumped posts will get the
mark_as_readPOST request on scrolling back up past them.I have not set them to anything specific. It looks the same except the lower two options are missing for me.
I'll give this a try, but not today anymore :)
Thanks for the additional info. When I switch to my other PC, I'll try to do a run through against feddit.org, scaled sort, with all the options you had set. Hopefully I can reproduce it.
Yeah, Feddit.org is on 0.19.5 and those two options require 0.19.7 or higher, so they're hidden/disabled.
I'm hoping the issue is just with the embeds enabled in the feed. Like I said, that's been deprecated and I rarely test in that configuration. I also have some memory hacks in place that turn those back into thumbnails when they're out of the viewport, so maybe there's a bug in that process when embeds are 'always on'?
If that does turn out to be the case, then the good news is it'll be fixed in 1.4.30 since everything is click-to-play.
Edit: I think I was able to see what you're referring to. It only did it once for me (and I had matched your settings), but I believe I can confidently say that the issue does exist. So, that's progress.
Hypothesis is that when the infinite scroll buffer overflows and it pops the oldest entries from the beginning of the feed, there's some weird behavior with FF (I don't think I've seen this on FF mobile, though).
Will keep testing and see if I can pin that down as the cause or rule it out.
Here is a video demonstrating the jump/skip:
Video
Thanks. I believe that's what I saw, though I could only trigger it once.
I think I know where the problem is, and I've made some changes in 1.4.30 that should address that if I'm right.
Unfortunately, 1.4.30 is a little behind schedule because I wanted to take the opportunity to re-write and clean up the rendering pipeline for the different post media in addition to my other "to do" items and bugfixes. That said, I'm going to have to wait until those are finished before testing the fix properly.
If you'd be willing to run a beta, I can give you a shout when I'm putting the final touches on the next release and you can let me know if that addresses the issue for you. Probably be about a week from now, give or take a few days.
In the mean time, if it gets to be too annoying, the only workaround I can think of would be to disable infinite scroll, set the posts per fetch to 30, close the tab, and relaunch (there's a known quirk when togging infinite scroll).
All good, take your time :) While it is annoying, the posts don't get marked as already seen which means they just reappear somewhere in the future.
If I can pull the beta in via a podman tag, I'll happily give it a try. Not sure if this issue would be a blocker though, as it doesn't seem to be super common for anyone else.
Sadly it's not the issue. I disabled both embed media options and it still skips a bunch of posts sometimes.
I'll try to catch a jump on video later.