this post was submitted on 12 Apr 2024
603 points (96.7% liked)

linuxmemes

21143 readers
1508 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [โ€“] [email protected] 7 points 6 months ago (1 children)

    I'm having some conflicts when it comes to lineage and similar OS. While, yes, they might be better from a privacy perspective (if you put the effort into it) and allow you to keep your phone longer, I simply do not trust that the OS can't be tampered with. For many devices, there is a single person maintaining that version of lineage. Who guarantees that they don't pipe important information to some server in a more or less clever way? This should not be misunderstood as an argument for closed source. The problems I'm having with this type of open source is that the code differs from device to device, it is (at least as far as I know) possible to change enough of the code to become malicious while adapting it to another device, I don't have the capacities to make sure that the code is actually safe, and they are not regularly audited. Hell, in some cases they are even provided without checksums. So you trade the spying eyes against a possible barn door of insecurities.

    Therefore, I much rather use audited ROMs like Graphene or Calyx, but they (mostly) require a device from the company that I am trying to avoid. It's such a weird situation...

    [โ€“] [email protected] 1 points 6 months ago

    Re: your last paragraph -

    Think of it this way. Google pulls in 300 billion USD a year and 80% of that is advertising revenue, not leaving a whole lot of the pie for Pixel phones once you take out subscriptions, Chromebooks, GCP, etc etc.

    Sure, they're probably making some money on every pixel sale but the point of them making mobile phones is to support their advertising business.

    I'm not a Graphene user, but that's the way I see it. At the end of the day if you get the phone secondhand you're not giving them any money at all.