1229
Google's shocking developer decree struggles to justify the urgent threat to F-Droid (www.neowin.net)
submitted 11 months ago by to c/technology@lemmy.world
298 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 11 months ago (10 children)

and what's the problem with android other than google's fuckery?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 10 child comments
    •
  • [–] 10 points 11 months ago (9 children)

    Assuming google's fuckery doesn't affect them, nothing.

    But we're relying on google to keep up that code and not see them as a threat. Right now AOK, but in the future that makes longevity questionable.

    It's something to be noticed and understood so there's no surprises when the company that did no evil now does all the evil.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 9 child comments
    •
  • [–] 4 points 11 months ago (7 children)

    they can take down the code today and not much will happen, as the code is mirrored elsewhere.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 8 points 11 months ago

    Obv, they can't take what we have, which is why for now we're OK. The winds are shifting, though. I expect at some point, I expect android will require a deal with the devil from manufacturers. Start actively combatting linux phones.

    For now, it's a quick path to privacy, long term, we're going to need friendly hardware

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 11 months ago (5 children)

    I think the big problem with this, as far as I know, is that this code needs pretty rapid security updates that require a fairly huge and experienced team of people to both find, understand and implement the security changes. Otherwise it becomes very insecure very quickly. So yeah we can always use 2019 Android, etc. But it would just put you at a huge security risk.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 2 points 11 months ago (4 children)

    doesn't the same apply to any operating system, including the linux phone distributions? android has security measures that may be breached, but mobile linux has much fewer security measures at all

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 11 months ago (3 children)

    Yes, it does apply to every operating system - hence, the differentiator becomes whether the operating system has hundreds of millions of dollars to spend on dedicated security development. This is why a lot of companies now don't even let you use Android devices for BYOD aside from Google or Samsung, because they're the only companies with the resources to keep their security really up to date.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 11 months ago (2 children)

    my point is that if the open source community cannot figure out just maintenance of an android system, there's no chance of creating a real mobile linux distribution, as it would need the aforementioned maintenance and the development of additional features

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 11 months ago* (1 child)

    Ahhh I see, I was confused about what you were getting at. My mistake. And yes that's very true...hmm. More dire than I was even thinking then..

    Honestly this is exactly the kind of thing that taxes and governments are supposed to be good for handling. Failures within failures I suppose!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 11 months ago

    no worries. but that's why I think android would be a much better base for a free software mobile operating system than a current linux distribution. lots of engineering work and experience went into making it, both on the technical sides and in the UX, with lots and lots of feedback. it has largely solved permissions, inter-app communication, power saving, things like these, and I mean all in the AOSP project, forgetting about the proprietary google mobile services.
    not everything is perfect, lots could be improved, and there are things we don't like, like how app background activity is handled is not too transparent and neither customizable, etc, but those would be much easier to fix and maintain then reimplementing everything. hardware drivers are a problem, but it is anyway, and with android we at least have a working system with which reverse engineers can analyze the drivers in operation. certainly android is not the cleanest codebase but its not so bad either to warrant throwing it away. in the parts of the code I looked over the years, it's quite organized, but of course I have only seen very little.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 11 months ago

    By “Google’s fuckery” you mean “Google doing all the updates and giving it to them” though, right?

    Until these alternative AOSP-derived OS developers stop relying on Google and start doing their own stuff, Google will have the ability to break their OS’s. This isn’t a Google issue, it’s a OS developer issue.

  • permalink
  • fedilink
  • source
  • parent