From Newsgroup: comp.mobile.android
Arno Welzel wrote:
Well - <https://keepandroidopen.org/> can only tell about things that
are known. Maybe seems Google updated their plans without telling everybody.
Also see:
<https://keepandroidopen.org/faq/>
<https://developer.android.com/developer-verification/guides/faq?hl=en#general>
Hi Arno,
Apparently Google is "rolling it out" to test areas first where it appears Google is becoming a gatekeeper for software it doesn't even distribute.
Even if Google Play is completely uninvolved.
The Keep Android Open campaign and numerous open-source/digital-rights organizations have specifically objected to this closing of Android.
<
https://en.wikipedia.org/wiki/Keep_Android_Open>
Google's new Android Developer Verification system requires an app to be associated with a developer whose identity has been verified by Google.
<
https://blog.accrescent.app/posts/android-developer-verification/>
Do we want your APK to install normally on a certified Android phone?
It won't happen unless the developer has already registered with Google.
That applies even if we got the APK from F-Droid, Accrescent, another app store, a website, GitHub, etc. even as Google added an "advanced flow"
allowing experienced users to install apps from unverified developers.
The catch is that Google has added additional friction/warnings, including
a 24-hour waiting period and explicit additional user-authentication steps.
In addition, some great apps, like Aurora or NewPipe, may perhaps disappear
if the developer doesn't want to personally register his name with Google.
I think that's the biggest threat, but I don't know how it all works yet.
--- Synchronet 3.22a-Linux NewsLink 1.2