Add note to the YouTube section of the Frontends page that briefly summarizes YouTube's API changes and suggests what readers can do if they find that one frontend is unreliable
I think that this is the best way to move forward if one YouTube frontend exhibits reliability issues. The threat of YouTube making more API changes is a looming presence for these frontends, and frontend maintainers are doing their very best with their free time. Rather than remove a frontend because it doesn't work at the moment, I think it's more reasonable to ask readers to switch to another one. In fact, that's what most of the community members in the forum thread did when LibreTube exhibited issues.
For FreeTube and Yattee, mention the APIs they use to extract information from YouTube
Reorder the YouTube frontends from cross-platform to platform-specific
The new order is as follows: accessible from any web browser :arrow_right: desktop :arrow_right: Apple OSes :arrow_right: Android only.
Remove the mention that you can log in to a Piped instance on LibreTube to sync subscriptions and playlists
Reason: The warning admonition under the Piped card advises readers to not log in to any accounts. This should apply to LibreTube as well.
For ProxiTok and Invidious, mention that there are some I2P instances
Remove mention of Tor instances in the Redlib card, as the list of instances currently only shows clearnet instances
Swap the positions of the two lists of criteria
Reason: I think it makes more sense to first present why certain sites are considered for frontends (rather than using the first-party sites), then present why these particular frontends are chosen for sites that meet the previous criteria.
Add threat model label to this page
- [x] I agree to the terms listed below:
Contribution terms (click to expand)
1) I am the sole author of this work.
2) I agree to grant Privacy Guides a perpetual, worldwide, non-exclusive, transferable, royalty-free, irrevocable license with the right to sublicense such rights through multiple tiers of sublicensees, to reproduce, modify, display, perform, relicense, and distribute my contribution as part of this project.
3) I have disclosed any relevant conflicts of interest in my post.
4) I agree to the Community Code of Conduct.
Changes proposed in this PR:
Contribution terms (click to expand)
1) I am the sole author of this work. 2) I agree to grant Privacy Guides a perpetual, worldwide, non-exclusive, transferable, royalty-free, irrevocable license with the right to sublicense such rights through multiple tiers of sublicensees, to reproduce, modify, display, perform, relicense, and distribute my contribution as part of this project. 3) I have disclosed any relevant conflicts of interest in my post. 4) I agree to the Community Code of Conduct.