-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
[Request/Query]RE: Future support for legacy (devices)? #15
Comments
Any changes to only https://github.com/TeamNewPipe/NewPipe do NOT affect this fork. Any changes to https://github.com/TeamNewPipe/NewPipeExtractor DO. If they do change in a way that breaks compatibility I will most likely NOT keep updating either of the 2 versions. Legacy or normal. PS: I only read the TLDR |
@XiangRongLin, I thank you for the swift reply as well as the clarification, it is appreciated. I understand, and hope that nothing too major happens that would cause such inconvenience for anyone. That being said, please do not hesitate to be as elaborate as required when responding to me, I appreciate any knowledge that you can provide and would like to learn as much as I can so that I can provide the most pertinent information that best helps both people to solve any issue without miscommunication(s) being a factor. Also, once more I apologize for any unintended misunderstanding or offence. Thank you for your time and attention. PS. I will keep in mind that you only read the TL;DR should we ever communicate in the future. TL;DR
|
@johnth3doe Have you read this? TeamNewPipe/NewPipe#7602 (comment) |
Describe the feature you want
It is not a feature per se, rather than a general query about this fork and if/will it be (able to provide) continuing support for certain legacy device versions (in this case 4.4).
Is your feature request related to a problem? Please describe it
Yes.
It has come to my attention that this issue and this pull request intend to drop support for not only legacy versions of android (in this case 4.4) but potentially all legacy versions of NewPipe (according to this comment) as well.
It should be known that I am not very techn(olog)ically literate, and do not know how this will affect the future of this fork. Furthermore, the original namesake legacy version has not been updated in over a year, so this fork (I thank you so much for it), is a saving grace for those that have potato-devices like I do.
Additional context
I don't know how the changes mentioned in the section above affects the extractor nor how the legacy-compatible versions will be affected (v0.21.12-legacy on this fork at the time of this request/query), but I would appreciate the ability to continue using NP(-legacy) until such time where it is otherwise impossible.
and that
How will you/everyone benefit from this feature?
There are (older) devices that are still NewPipe compatible/functional, and would still be able to use it; However, despite this fact, the fellow member who made issue #7602 for discussion, decided that they didn't "see any further benefit" in said discussion, then led the charge to implement the PR that is a primary reason that I am submitting this request/query.
While there are ample reasons mentioned/discussed, the consensus ultimately suggests that the changes will be implemented; and this negatively affects users that would otherwise still be able to enjoy the benefits of NP.
Additional Notes
I would like to put forward that there were valid points provided in the all of the respective linked/mentioned comments/issues, and I admit that I have a biased opinion in this because I have a potato-device, that cannot be updated (for technical reasons), and I am unable to get a new device (for financial reasons) and therefore this change affects me.
PS.
Notwithstanding the foregoing, I am unaware if this is the correct place or method to put my point forward, and I apologize for any unintended due diligence, inconvenience, misunderstanding or offence at any point.
TL;DR
I would like to know if the support changes to NP will affect this fork negatively, and hoping that it is not the case.
Thank you for your time and attention.
Also, thank you again to @XiangRongLin for your continued time, effort and support towards the community and for this fork.
Stay safe, be well.
The text was updated successfully, but these errors were encountered: