• xiii@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      ·
      11 hours ago

      It took 6-10 years for Android to take shape.

      On Linux, every app has full access to your browsing history, clipboard (passwords), photos with geo-tags, music, list of other installed apps, contacts. Unrestricted battery and network access – it’s a tracking paradise. And all it takes is one supply chain attack on npm install with typical 4000K dependency packages

      • timestatic@feddit.org
        link
        fedilink
        English
        arrow-up
        9
        ·
        10 hours ago

        Thats why flatpaks exist for those kind of apps and sandboxes are very much possible on linux (even if not widely used for normal programs)

        • xiii@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          3 hours ago

          Flatpack is only a piece of the puzzle. I remember in early Android version, an app could increas gyroscope query frequency (i.e. a racing game demanding precise phone tilt), then crash and the gyroscope would drain battery within hours. And again — this is only one example.

          The ecosystem must grow — to this day, I cannot set Immich as my default gallery app on LineageOS. So I take a photo, and can’t immediatelly look at it. And Android is already mature. There must be a standard and secure way of exchanging calendar events, notes, photos. Developers must adopt this new ecosystem — it takes years.

          The best option we have right now is to pressure Google to allow alternative to Play Services and also sponsor AOSP development outside of Google. There are numerous Linux distros, including commercial ones, I don’t see why we can’t have numerous Android flavors.

          • timestatic@feddit.org
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 hour ago

            Honestly I would much rather long term have decent Linux for phones, as AOSP derived programs will always rely in some way on google code. I would prefer having one large FOSS Linux ecosystem

      • DupaCycki@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        9 hours ago

        Linux phones have already been around for many years. Right now we’re very close to Linux phones that are usable on a daily basis. Not as close to decent Linux phones, of course, but with the right (not at all unrealistic) resources it could be completely within reach in a year or two.

        Also, Flatpaks exist and work pretty much just like Android apps.

        • xiii@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 hours ago

          I made a full comment in this thread. The bottomline is

          1. Sandboxing of resources both hardware (gyroscope, network devices) and data (photos, music) takes a lot of trial and error.
          2. There is a need for an ecosystem: i.e. apps sould be able to create calendar events, or access shared mediaplayer — also with permissions
          3. Developers need to adapt to the software ecosystem
          4. Hardware companies e.g. smart watch, projectors, TV need to adapt

          It all takes years.

          Linux phones are around for enthusiasts since Nokia N900 (which was/is a masterpiece) — yet nothing is remotely close to a mainstream phone.

    • Bilb!@lemmy.ml
      link
      fedilink
      English
      arrow-up
      13
      ·
      17 hours ago

      Just in time for them to be practically outlawed, if my gut can be trusted. I hope not.

      • JustAnotherPodunk@lemmy.world
        link
        fedilink
        English
        arrow-up
        30
        ·
        18 hours ago

        Yeah we can do that. What do you think side loading means? Changing the name of an install doesn’t make it different. Back in my day we called it installing a program. Things changed. Then we called it downloading an app. Things changed. Now if it’s not approved it’s called side loading? Blow it out your ass.

        Its a program. Take the training wheels off of the Internet. I grew up when this was a cautionary tale. But up and deal with the consequences or get out.

      • NewOldGuard@lemmy.ml
        link
        fedilink
        English
        arrow-up
        43
        ·
        20 hours ago

        “Side load” is just language used to mean installing software outside of the official approved vendor store. Linux lets you install software from wherever you want, you’re not locked into a vendor or manufacturer ecosystem. So in a sense all you do is “sideload,” it’s just normal non-corporate OSes call that “installation”

      • cmhe@lemmy.world
        link
        fedilink
        English
        arrow-up
        15
        ·
        18 hours ago

        I guess you are joking? And mean “side-loading” as in injecting custom code via LD_PRELOAD and not the strange definition phone makers use for describing ‘installing an app’.

      • nathan@lemmy.permisuan.com
        link
        fedilink
        English
        arrow-up
        8
        ·
        20 hours ago

        How would reverse engineering c code be side loading? You can get .deb, .rpm etc and install them on your distro as long as it supports the format, regardless of who developed the app, and honestly even if it doesn’t support the format there are ways. You can even compile the source code of more Linux apps, at least the FOSS ones, with just a few commands. If anything it would be more realistic to say you can ONLY side load on Linux