-
Notifications
You must be signed in to change notification settings - Fork 104
f-droid #8
Comments
preferably also via a separate repo like the main newpipe does; fdroid sometimes takes a while to roll out updates |
Depends on #12 |
+1, main repo and a hosted one or maybe izzy's repo. |
I'd also say both, the official one, and a custom onel with faster updates, like the newpipe one, but keeping the same f-droid FLOSS policies on the custom one... Thanks ! |
This is the main reason that's keeping me from using this: Newpipe needs frequent updates so it won't stop working with YouTube. Keeping an app updated manually on multiple devices is much more effort than just skipping sponsored segments manually... |
the updates are not that frequent plus fdroid updates the same way newpipe updates unless you are rooted (which is bad for security anyway) |
fdroid does some verifications, not all repos but their main and izzy's repo i know do |
the advantage of using fdroid's main repo is that you trust them to build from source instead of downloading whatever binary the main dev puts in releases , but again , unless you audit the code yourself you still need to trust the dev anyway izzy afaik just grabs binaries from releases |
https://apt.izzysoft.de/fdroid/index/info
as with anything
It doesn't need frequent updates but there are times where Google does something and Newpipe fixes it then a day later it's broken again then a few more times then Newpipe is fine for months if not longer. |
I would prefer a repo with only NewPipe x SponsorBlock, as Izzy contains proprietary software. EDIT: |
Upstream code checks whether the current APK was signed with the release key for various reasons: - in order to show/hide the "Updates" settings menu - in order to make the "Updates" settings menu searchable or not - in order to check/not check for updates at the application start This behavior was removed in NewPipe SponsorBlock fork, but it probably shouldn't have been: - the newer APK installation won't work if the locally installed APK wasn't signed with the same key - `isReleaseApk` function was still invoked in NewPipe SponsorBlock to allow searching "Updates" settings from settings menu. But as the fingerprint wasn't correct (see 25575ea), the update settings would not be searchable which is a bug - this is a requirement for F-Droid inclusion as they sign their APKs with their own keys (so the updater wouldn't work) and they explicitly forbid auto-updaters by policy (see also polymorphicshade#8)
Any updates on this? |
Just submitted https://gitlab.com/fdroid/fdroiddata/-/merge_requests/11402 . We'll see where this goes. 🤞 |
We'd probably want to wait for the Tubular rebranding. That might entail a new app ID. |
I'll leave it in draft then. Please let me know when the rebranding happens. It may also be needed to update the fastlane metadata btw. I'd argue against an app id change though because it's rather internal and will mostly cause upgrade issues to users, who will likely have to reimport their subscriptions and recreate their preferences. |
Agreed |
no news? |
I'm working on a new build recipe, but currently the build fails due to missing dependencies on jitpack.io. But until then we should figure out if any rebranding is wanted/needed for F-Droid inclusion. Compilation error
|
can you please add your fork to f-droid so it can have a larger audience and at same time we can have automatic updates
The text was updated successfully, but these errors were encountered: