795
Google Confirms Non-ADB APK Installs Will Require Developer Registration (hackaday.com)
submitted 1 year ago by to c/technology@lemmy.world
257 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 308 points 1 year ago (21 children)

Google can go fuck itself.

Hopefully this will put some jet fuel into the Linux phone development.

  • permalink
  • fedilink
  • source
  • hideshow 21 child comments
    •
  • [–] 81 points 1 year ago (14 children)

    I'm checking out Graphene OS next week and pretty pumped about it. This Google ratfucking has been just the push I need to get off Android.

    And obviously I haven't stopped telling people around me haha

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 14 child comments
    •
  • [–] 57 points 1 year ago (3 children)

    Most F-Droid users are NOT custom ROMs.
    This means that as long as F-Droid does not get their own developer key - it will become useless. F-Droid is privacy focused - both dev and user, and they oppose requiring devs to essentially give up their privacy and sign the APK with their own dev key.

    Now, if F-Droid is dead, GrapheneOS becomes useless. Who would want to develop apps for the 0.0001% of the population (i.e custom ROM users)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 21 points 1 year ago (1 child)

    This.

    I am the person you are talking about. I've looked into graphene before and I do host some of my own services at home. I also work full time and I don't want to spend all of my free time managing things. I use F-Droid, but I am on stock android on my pixel.

    I appreciate the privacy and FOSS nature of F-Droid, but I use things like Android auto Google maps for work, I use banking apps on my phone as well. I know technically micro G and blah blah blah, but like I said: work full time.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 20 points 1 year ago (8 children)

    Graphene is bult on top of android AOSP, which is owned by google... And of course they are fucking it over.

    Check calyxos.org s recent blog posts, it is basically dying (and graphene is the same)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 20 points 1 year ago (1 child)

    The pause in Calyx updates has nothing to do with Google's fuckery, and they are not "dying." They lost a major lead developer and decided they needed to restructure so no one would be so essential going forward.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 7 points 1 year ago (2 children)

    What happened to the Open Handset Alliance?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 1 year ago

    GrapheneOS isn't dying. There's an OEM partnership in the works and they'll release devices with support for GrapheneOS in a year or two. GrapheneOS still provides updates and while the changes have made some things harder, the project is still going strong.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 3 points 1 year ago (1 child)

    So.. huh, so what's the alternative then? I guess some other flavour of linux?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 13 points 1 year ago

    For mobile phones that works as a daily driver? Gobbling up iOS. Or gobbling up what's becoming of Android.

    I really wish we had open phones that "just work". I'd even go with slightly quirky but functional. Unfortunately, that requires strong cooperation between hardware maker and software developers; and it will require a lot of work. But that's not the main issue. The direction we're headed toward is "everything need an official app", and those will mostly only work on "official" phones made by big manufacturers.

    Even today, making some bank apps work on non vanilla Android is not always straightforward, and it's still relatively open and easy to do. The move by Google is going to tighten this even more, and I have no doubt, if they pull through, that this will go in the requirements for the "play protect" validation BS. Meaning if you want that bank app, or whatever state digital ID app (meh) to work, you'll need a "real" Android or an iOS device. And those apps are becoming more and more mandatory (I can't log-in to my bank's online website without their app and proprietary 2FA…).

    A niche, open-source OS, Linux or modified AOSP or whatever, will have a hard time filling that gap as things keep moving. Which is really sad.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 1 year ago* (1 child)

    i wonder if it's possible for fdroid or another dev to make a linux/windows/osx app which basically uses an adb connection to automatically upload and install applications

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •