From 3f1f42145e386490b5d201bad44883f2ab390aa7 Mon Sep 17 00:00:00 2001 From: mhmdanas <32234660+mhmdanas@users.noreply.github.com> Date: Sun, 6 Dec 2020 16:52:03 +0300 Subject: [PATCH 1/5] Update "Updates" to account for F-Droid bug Pun not intended (oh really?). --- README.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 2568b7624..b29e2c758 100644 --- a/README.md +++ b/README.md @@ -82,12 +82,13 @@ NewPipe supports multiple services. Our [docs](https://teamnewpipe.github.io/doc ## Updates When a change to the NewPipe code occurs (due to either adding features or bug fixing), eventually a release will occur. These are in the format x.xx.x . In order to get this new version, you can: - 1. Build a debug APK yourself. This is the fastest way to get new features on your device, but is much more complicated, so we recommend using one of the other methods. - 2. Add our custom repo to F-Droid and install it from there as soon as we publish a release. The instructions are here: https://newpipe.schabi.org/FAQ/tutorials/install-add-fdroid-repo/ - 3. Download the APK from [Github Releases](https://github.com/TeamNewPipe/NewPipe/releases) and install it as soon as we publish a release. - 4. Update via F-droid. This is the slowest method of getting updates, as F-Droid must recognize changes, build the APK itself, sign it, then push the update to users. -We recommend method 2 for most users. APKs installed using method 2 or 3 are compatible with each other, but not with those installed using method 4. This is due to the same signing key (ours) being used for 2 and 3, but a different signing key (F-Droid's) being used for 4. Building a debug APK using method 1 excludes a key entirely. Signing keys help ensure that a user isn't tricked into installing a malicious update to an app. + 1. Add our custom repo to F-Droid and install it from there as soon as we publish a release. The instructions are here: https://newpipe.schabi.org/FAQ/tutorials/install-add-fdroid-repo/ + 2. Download the APK from [Github Releases](https://github.com/TeamNewPipe/NewPipe/releases) and install it as soon as we publish a release. + 3. Update via F-Droid. This is the slowest method of getting updates, as F-Droid must recognize changes, build the APK itself, sign it, then push the update to users. (**IMPORTANT**: as of the time of writing, an F-Droid bug is preventing updates later than 0.20.1 from being published. Thus, till this bug is solved, if you want to use install updates from F-Droid, we recommend method 1.) + 4. Build a debug APK yourself. This is the fastest way to get new features on your device, but is much more complicated, so we recommend using one of the other methods. + +We recommend method 1 for most users. APKs installed using method 1 or 2 are compatible with each other, but not with those installed using method 3. This is due to the same signing key (ours) being used for 1 and 2, but a different signing key (F-Droid's) being used for 3. Building a debug APK using method 4 excludes a key entirely. Signing keys help ensure that a user isn't tricked into installing a malicious update to an app. In the meanwhile, if you want to switch sources for some reason (e.g. NewPipe's core functionality was broken and F-Droid doesn't have the update yet), we recommend following this procedure: 1. Back up your data via Settings > Content > Export Database so you keep your history, subscriptions, and playlists From 5d2d9f3493f02d630b48e8fce80d4aa91a5d2463 Mon Sep 17 00:00:00 2001 From: mhmdanas <6daf084a-8eaf-40fb-86c7-8500077c3b69@anonaddy.me> Date: Fri, 15 Jan 2021 18:13:52 +0300 Subject: [PATCH 2/5] Rename updates section to installation Also added a hidden span so that old links won't break. --- README.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index b29e2c758..96835a1fe 100644 --- a/README.md +++ b/README.md @@ -12,7 +12,7 @@


-

ScreenshotsDescriptionFeaturesUpdatesContributionDonateLicense

+

ScreenshotsDescriptionFeaturesInstallationContributionDonateLicense

WebsiteBlogFAQPress


@@ -80,12 +80,14 @@ NewPipe supports multiple services. Our [docs](https://teamnewpipe.github.io/doc * media.ccc.de \[beta\] * PeerTube instances \[beta\] -## Updates -When a change to the NewPipe code occurs (due to either adding features or bug fixing), eventually a release will occur. These are in the format x.xx.x . In order to get this new version, you can: + + - 1. Add our custom repo to F-Droid and install it from there as soon as we publish a release. The instructions are here: https://newpipe.schabi.org/FAQ/tutorials/install-add-fdroid-repo/ - 2. Download the APK from [Github Releases](https://github.com/TeamNewPipe/NewPipe/releases) and install it as soon as we publish a release. - 3. Update via F-Droid. This is the slowest method of getting updates, as F-Droid must recognize changes, build the APK itself, sign it, then push the update to users. (**IMPORTANT**: as of the time of writing, an F-Droid bug is preventing updates later than 0.20.1 from being published. Thus, till this bug is solved, if you want to use install updates from F-Droid, we recommend method 1.) +## Installation +You can install NewPipe using one of the following methods: + 1. Add our custom repo to F-Droid and install it from there. The instructions are here: https://newpipe.schabi.org/FAQ/tutorials/install-add-fdroid-repo/ + 2. Download the APK from [Github Releases](https://github.com/TeamNewPipe/NewPipe/releases) and install it. + 3. Update via F-Droid. This is the slowest method of getting updates, as F-Droid must recognize changes, build the APK itself, sign it, then push the update to users. (**IMPORTANT**: as of the time of writing, an issue is preventing releases later than 0.20.1 from being published. Thus, till this issue is solved, if you want to use F-Droid, we recommend method 1.) 4. Build a debug APK yourself. This is the fastest way to get new features on your device, but is much more complicated, so we recommend using one of the other methods. We recommend method 1 for most users. APKs installed using method 1 or 2 are compatible with each other, but not with those installed using method 3. This is due to the same signing key (ours) being used for 1 and 2, but a different signing key (F-Droid's) being used for 3. Building a debug APK using method 4 excludes a key entirely. Signing keys help ensure that a user isn't tricked into installing a malicious update to an app. From 970a656c4cc369eaffee6c3ef5fd7c63f32ca63a Mon Sep 17 00:00:00 2001 From: mhmdanas <6daf084a-8eaf-40fb-86c7-8500077c3b69@anonaddy.me> Date: Fri, 15 Jan 2021 18:16:28 +0300 Subject: [PATCH 3/5] Hide F-Droid badge --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 96835a1fe..12b874f25 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,9 @@

NewPipe

A libre lightweight streaming frontend for Android.

-

+ + +

From 38a12a27e9d050b95959770c7a08a1ed651f7bdf Mon Sep 17 00:00:00 2001 From: mhmdanas <6daf084a-8eaf-40fb-86c7-8500077c3b69@anonaddy.me> Date: Fri, 15 Jan 2021 18:16:45 +0300 Subject: [PATCH 4/5] Add period to end of comment --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 12b874f25..2f3612bbb 100644 --- a/README.md +++ b/README.md @@ -82,7 +82,7 @@ NewPipe supports multiple services. Our [docs](https://teamnewpipe.github.io/doc * media.ccc.de \[beta\] * PeerTube instances \[beta\] - + ## Installation From 1361871072c53b04a61752ed917be612743e4f38 Mon Sep 17 00:00:00 2001 From: mhmdanas <6daf084a-8eaf-40fb-86c7-8500077c3b69@anonaddy.me> Date: Fri, 15 Jan 2021 22:18:49 +0300 Subject: [PATCH 5/5] Rename installation to installation and updates --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index d61c65653..141bedb10 100644 --- a/README.md +++ b/README.md @@ -14,7 +14,7 @@


-

ScreenshotsDescriptionFeaturesInstallationContributionDonateLicense

+

ScreenshotsDescriptionFeaturesInstallation and updatesContributionDonateLicense

WebsiteBlogFAQPress


@@ -85,7 +85,7 @@ NewPipe supports multiple services. Our [docs](https://teamnewpipe.github.io/doc -## Installation +## Installation and updates You can install NewPipe using one of the following methods: 1. Add our custom repo to F-Droid and install it from there. The instructions are here: https://newpipe.schabi.org/FAQ/tutorials/install-add-fdroid-repo/ 2. Download the APK from [Github Releases](https://github.com/TeamNewPipe/NewPipe/releases) and install it.