-
Notifications
You must be signed in to change notification settings - Fork 922
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request]: Remove the Autoplay interruption timer. #6808
Comments
Hello. Here's a better way to communicate what you want:
|
Explain why. |
Is there available option to disable that timer? If not, then that could be a feature request. |
oi, what do you mean the 12h timer dont compute? it works on my end.. it sucks, i can agree to that, but im too lazy to sift through endless lines of code to disable it. burgers cant be cucumbers. it is what it is |
Not sure if we should adjust the naming or add a tooltip to make it more well-known, but the timer resets on any user interaction whatsoever inside FreeTube, which I'm guessing is the piece that is not being understood here. |
|
Guidelines
Problem Description
Hello,
This aspect of the platform is arguably its most disappointing feature. Users should have the autonomy to decide when to end a playlist, yet FreeTube insists on exercising control over this decision. What is the reasoning behind this? It is incredibly frustrating to experience an interruption in the playlist due to FreeTube's intervention.
Proposed Solution
Although I recognize the presence of a 12-hour timer, it does not function effectively. While I acknowledge the existence of a 12-hour timer, it remains ineffective. I strongly advocate for the removal or an option to turn off this feature.
Alternatives Considered
This is precisely why I continue to utilize older versions. The absence of a removal timer in those earlier builds renders them superior to any of the more recent iterations of FreeTube.
Issue Labels
ease of use improvement, new feature
Additional Information
No response
The text was updated successfully, but these errors were encountered: