Skip to content

Use batched fetching instead of forcing RSS with sub count > N#9379

Open
PikachuEXE wants to merge 1 commit into
FreeTubeApp:developmentfrom
PikachuEXE:feature/limit-request-fallback-without-rss
Open

Use batched fetching instead of forcing RSS with sub count > N#9379
PikachuEXE wants to merge 1 commit into
FreeTubeApp:developmentfrom
PikachuEXE:feature/limit-request-fallback-without-rss

Conversation

@PikachuEXE

@PikachuEXE PikachuEXE commented Jul 6, 2026

Copy link
Copy Markdown
Member

Pull Request Type

  • Bugfix
  • Feature Implementation
  • Documentation
  • Other

Related issue

Taken from #9157 without the new setting

closes #9157

Description

Currently FT forces user to use RSS when subscription count within the current profile is > 125
This PR makes FT just fetch videos, live, community posts in batches of 80 regardless (sub count <= 80 = same as before)
No new setting at all, Posts tab can be shown now as sub count shouldn't matter

No idea what batch size/timeout should be used, all taken from #9157

Screenshots

Only shows video one, test the rest yourself

Screen.Recording.2026-07-06.at.15.50.37.mp4

Testing

Preparation: get 125+ subscriptions

  • Refresh sub in video tab
  • Refresh sub in live tab
  • Refresh sub in posts tab (the tab should be visible

Desktop

  • OS:
  • OS Version:
  • FreeTube version:

Additional context

@FreeTubeBot FreeTubeBot enabled auto-merge (squash) July 6, 2026 07:54
@github-actions github-actions Bot added the PR: waiting for review For PRs that are complete, tested, and ready for review label Jul 6, 2026
@efb4f5ff-1298-471a-8973-3d47447115dc

This comment was marked as low quality.

@PikachuEXE

This comment was marked as resolved.

@efb4f5ff-1298-471a-8973-3d47447115dc

Copy link
Copy Markdown
Member

Works good. Question before approval (because other PR author isnt responsive),

  • i know the 80 number comes from the other PR but could you maybe try to explain why you think this number is picked?
  • How are we sure that this wont trigger the 429 errors?

@PikachuEXE

Copy link
Copy Markdown
Member Author

I guess 80 comes from ~2/3 of 125 limit (and where does 125 comes from? dunno
And I am not sure if this works great (nob 429) since we can never be sure about how YT setup their rate limiting (not to mention some people use VPN which would might make it worse but I assume no VPN case first)
Since there is a fallback to use RSS (even it requires user setting it manually) I consider this safe-ish but adding a setting for batch interval might be needed if users start getting 429 (but doesn't have to be now)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

PR: waiting for review For PRs that are complete, tested, and ready for review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants