Home | Notifications | New Note | Local | Federated | Search | Logout
Note Detail
Reply to @hj@shigusegubu.club
rees@rees@tsundere.love (2026-07-31 08:53:23)
@hj @Nudhul @sun if there is a glitch at high speed then it's also happening at slower speed, but your cpu is fast enough for it to not be noticeable. this is something wrong with the code, and even if it doesn't affect you on your machine it's still causing battery drain, or lag on people with slower computers or phones
---Reply---
Denpa mode :flag: :cute__i: @hj@shigusegubu.club (2026-07-31 08:58:17)
@rees @Nudhul @sun the code is actually very simple - it only renders visible content, when content goes out-of-sight it stores its height and replaces all out-of-sight statuses with a two spacers (above and below) with height of sum of those hidden.
If we don't do that any update to the timeline (or thread) will cause massive lag and possibly CPU usage, just vue things.
You can compare how timeline behaves to how threads behave - as I said - threads don't have virtual scrolling at all. You can also disable this optimization completely if you wanna compare.
---Attachments---
image: https://shigusegubu.club/media/cd45d07a-770a-4d6b-9279-424970f36bb9/image.png?name=image.png
Reply
---Replies---
rees@rees@tsundere.love (2026-07-31 08:58:54)
@hj @Nudhul @sun >just vue things
you might as well just have claude rewrite it in a better framework with ultracode in like a day