• 2 Posts
  • 10 Comments
Joined 1 year ago
cake
Cake day: July 23rd, 2023

help-circle
  • Free software (not open-source, it’s really free software that’s important) that depends on a single for-profit vendor is not free.

    MicroG is open-source but it’s not free. It fails to address two problems:

    • What do I care looking at the source code of a Google Play Services replacement when Google still holds my cellphone by the balls for certain critical functions?
    • Why do I need permission from Google for apps to function properly on my cellphone?

    I don’t think OP cares about getting the source of the apps they run so much as the apps being free-as-in-libre in his original question. Many people mistake open-source for free software and MicroG is not truly free.







  • This danger is why I quit using the Purple Teams plugin for Pidgin: it works well enough (considering Teams isn’t exactly open to third-party clients, it works amazingly well in fact) it’s GPL-3.0, the source is provided and I compiled it.

    So I believe it’s clean, but that’s not good enough for me to hit our corporate Teams channels with it and I don’t have the time to audit the code. Not to mention, while my company trusts my good judgment, I’m pretty sure running an unauthorized client is against IT policies.

    So I dropped it, sadly. It’s a bummer because Pidgin uses a fraction of the resources needed by that pig of an Electron app - the official client - made by Microsoft.


  • So you really trust Google to release code that doesn’t do something it shouldn’t behind your back do you? How cute…

    I am an embedded developer so please don’t patronize me. And I know enough about security to know that Google’s security model on the Pixel phones is the best yet. That’s not the issue. The issues are:

    • Google’s code is untrustworthy unless reviewed, and proprietary binary blobs can’t be reviewed. If Google codes anything, they have an ulterior motive and it’s rarely in your best interest. If that’s not a security shortcoming, I don’t know what is. Or said another way, there’s something deeply ironic in claiming to have the most secured deGoogled OS and the lynchpin of that security is Google itself.

    • Yes, using a phone other than a Pixel phone with a deGoogled OS other than GrapheneOS as I do (I use a FP4 with CalyxOS) is less secure than GrapheneOS on a Pixel phone - assuming you trust Google’s drivers aren’t doing other things unrelated to their driver function.

      But as I said, my most important goal in anything technical I use is to not use Google. That’s my ideal. Some people have ideals and aren’t willing to compromise.

      With that in mind, and considering that I’m a low-value target, I deem the security provided by CalyxOS on my FP4 more than adequate for my use case. Or said another way, GrapheneOS’ - short-sighted, in my opinion - obsession with security gets in the way of my main goal, which is to avoid Google.


  • Graphene is against GNU ideals getting in the way of security,

    Funny, Graphene’s obsession with security is getting in the way of my ideals.

    Fuck Google and their proprietary security updates. I want no Google in my life and if that means a bit less security, I’m okay with that. In fact, I’d argue that running Google code that does who-knows-what for your security is itself not a very safe thing to do.