Obviously Google is just gaslighting us. Those ******* bastards ought to know better than to assume we like the changes, none of us like the changes to Android.
What I do not get is: where tf are they getting this 90 times from? Who is their analyst? I guess I will drop them this question, being one myself.
In ancient times in India, there was this dwanda (debate) and I am now thinking of getting into one with this analyst. Their assessment is bad as f.
Guess you censored the F word too. Regardless, I hate changes in general, and Developer Verification is one I would reverse immediately to maximize Privacy & Freedom.
Of course, with F-Droid 2.0 having a bad UI (Yeahā¦Googleās Files application spurred my hatred when it comes to unnecessary UI modifications), I feel like F-Droid could suffer a similar issue that leaves me behind deliberately.
@hans asked the Google lawyers in the actual EU DMA hearing to show the analysis back in 2023-2024, but they deflected
The numbers only go upā¦ as if to justify somethingā¦
Yeah, their earlier flow had I think a lesser variation.
Anyhow, I probably believe they are somehow trying to own the world where they will only bring the apocalypse and then be the hero to bring some peace. Dual role you know. 
for every nerd that sideloads foss there is probably 100 normies who sideload pirated games, so nah youāre not winning that argument
the way that they are gaslighting you here is that in reality developer verification has nothing to do with sideloading restriction. developer verfication helps them fight bad actors in google play, and boy they have a problem with that, but to not admit to it they pile it together with sideload restriction so they can misdirect from one to another in their rhetoric.
- we need to deanonymize all devs in google play!
- why? there is lot of malware in google play?
- nonononono, wait, look over there! so many people sideload malware, this will solve this, causeā¦ ummmā¦ yeah we goona use this same mechanism to restrict sideloadingā¦ yeah, thatās it!
- so this is total lockdown like apple?
- nonononono, this is developer verification for developers
they could have restricted sideloading without developer verification, or vise versa, but that would require them to independently admit 2 extremely negative things
- need for developer verification means there is plently of malware in google play
- sidloading restriction usurps eveyones right to use their devices as they see fit, not just developers
Exactly what I said earlier. Just in not so many words.
they have this for years, thatās why TODAY devs with apps in Play are already registered
not sure what you mean
well i donāt keep up with google fads so is all news to me, however that doesnāt change the fact that they are still combining the two concepts in their rhetoric to misdirect, and you should be careful to not fall for it
here is how it goes:
- hey look at this new thing called developer verification
- evil bad developer hide behind anonymity to malware you
- and the poor inoccent users sideload metric ton of malware
- so to save poor innocent users we goona spank that naughty developer, verify him good and make him pay
now out of all of this every single word is a lie, except for the fact that people do infact sideload metric ton of malware, and somehow this one truish statement is the only thing you decide to single out and argue against, being succesfully gaslit into doing exactly what the author of this article wanted by highlighting it
If you only distribute apps outside of Google Play, you can create an account in Android Developer Console today.
Basically, this if not already forced today, but tomorrow will be mandated, and an account will be needed without which you cannot move ahead on a device. Especially new devices.
Even that sounds like a diversion to me, the main event is that the googleās proprietary software is finally going to show some teeth and start deciding what you can or cannot install, exactly like apple. Without that total power grab that affects all users no verification of no developers would matter. Everyone is going to jail. All the rest is just a minor consequence in comparison. Like I seriously would not be surprised if it turns out the main reason for doing this is to combat piracy, cause that some extra moneys in their eyes that they could have had, but donāt have now, and the whole security and malware thing is just a charade as always. Some of them pirate sites are literally better than google play for discovering apps that are actually good or are made good through mods, big threat to their wallet, and also something a lot of devs would also be very happy to see brought down, another reason why devs donāt matter here. So we are back to square one, same thing all over again, except gaslighting intensifies, what was then called DRM is now called ādeveloper verificationā, and itās the worst kind. The absolute garbage that would infect your entire system to make sure you behave, and that everyone hated with passion is now so normalized itās like nobody even sees it.
Unless we keep protesting, Google will literally get away with it. Plus, Governments donāt care, since itās more money in their pockets and it āProtects the Kidsā, but in reality itās nothing more but a power grab and a Mass Surveillance tool.
I understood that the creation of a Google developer account is not needed for users to install any software, after jumping through the new hoops to turn on Unknown Sources.
Isnāt that the case?
If yes, in effect, not much changes from the current way of installing any software other than the (more bothersome) way of turning on Unknown Sources.
But still, ADB exists. Duh, just use that and you can forcibly install APKs.
Thatās the best possible interpretation, but would you trust it when itās fed to you with gaslighting about evil scameers? They can keep this as a system setting as before entirely in userās control, or they can engage their always online DRM to enforce this. Which one it would be, you wouldnāt know unitil you see it. The jaws are tightening and you should use that as an excuse to scream and if it indeed gets them to relax a bit, you should then scream even harder to get them off your neck entirely, not be content with barely being able to breath. Donāt accept their narrative.
- against scammers we employ this mild measure, agree?
- agree
- oops, data shows it didnāt work, naturally as you agreed that scammers are a problem and measures need to be taken, we will now employ stricter measures
- *surprised pikachu face*
My apologies for the colourful idiom, which not all speakers of English are familiar with. To 'āteach grandma to suck eggsā means to lecture someone about something they are very familiar with, potentially more so than the lecturer ; )
My apologies, this was not specified in the question : )
This new developer verification is all about āside loading". They want to restrict installing apps outside the play store to only apps from verified developers.
The gaslighting is that they tell us this is for security and protecting users. But itās all about control, being able to prevent app distribution. And no, this will not be limited to malware. Iām convinced we will see this being applied to other apps.
It is a known fact that it will apply to all app developers, not just those suspected of injecting malware into their apps. Besides, handwaving at malware as an excuse is clearly reputation laundering, because Goggle themselves are well known for injecting malware into absolutely anything they can get their filthy mitts on. To collect personal data about people, with or without our knowledge or consent. If the Android/Linux developer registration program was about reducing malware, it would be a classic case of putting the fox in charge of the henhouse.
It really is time to liberate the Android/Linux from Goggleās control, as OpenOffice was liberated from Oracleās control by the Document Foundation with their LibreOffice fork. What would be required to get the /e/ Foundation, for example, into a position to hard fork Android on top of a standard Linux kernel (or even better Linux-libre), for use by device vendors and mobile developers?
Iāve figured as much, but I have an issue with you folks that are so familiar with it but still continue to peddle āthe next proprietary siloā