Repository navigation
Conversation
EtorixDev
marked this pull request as draft
October 15, 2026 07:03
Declare the message collection length in Vencord’s Discord types.
EtorixDev
marked this pull request as ready for review
October 15, 2026 11:05
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a plugin to improve backreading a channel.
Currently if you scroll any faster than a snail's pace you're often hit with rubberbanding as Discord pushes your scroll position back down as it renders messages and fetches more.
4 main fixes for that:
Used Codex (6.1 Sol/6 Astra) via T3 Code to investigate the rubberbanding issue, to implement patches and then review logged scroll height and request timings while I scrolled a channel's history, and then to implement the plugin. Manually tested and reviewed each patch/setting individually. PR written and opened manually. Code comments kept intentionally, and reviewed. I like my patches explained in layman's terms.
Checklist before submitting