Formerly @russjr08@outpost.zeuslink.net

  • 0 Posts
  • 67 Comments
Joined 1 year ago
cake
Cake day: December 7th, 2023

help-circle
  • Primarily I use Arch on my desktop (and by proxy, my Steam Deck which runs SteamOS), which is what I’ve landed on after a ton of distro hopping. The idea of Atomic distros catches my eyes, but for me in its present state there are too many steps needed in order to make deeper changes (for example, installing a kernel module) - but I quite like SteamOS on my Deck since I know it will always be in a “consistent” state, for example.

    On servers I run a mix of Rocky Linux and Debian.


















  • You’re thinking of install-time permissions, which technically does still exist, but pretty much most of the permissions you’d actually care about are runtime (or special) permissions - the application must request these from the user.

    There are three main types of permissions on Android:

    • Install-time, these are permissions granted to an application upon installation
      • In this group is also signature-level permissions, which are only granted to applications that are signed by the same party as the OS itself (usually your OEM)
    • Runtime permissions (also known as “Dangerous permissions” within Android internally), which are permissions that the application must request from the user. The system draws the permissions dialog, not the application itself. Permission can also be granted one-time only, or permanently (unless the user revokes the permission)
    • Special permissions, which also need to be requested by the application - except for these the system will not draw a permissions dialog, instead the application must send the user to the “Special App Access” menu within system settings, and the user must turn on the permission there. The best way I can describe these types of permissions is, “permission that the user really must think about before granting” - such as giving an app the ability to bypass DND rules, drawing over other apps, installing APKs from unknown sources, accessing all device files, etc. IIRC, Google also requires that developers provide justification for requesting these permissions when submitting to the Google Play Store as well.

    Runtime permissions were introduced in Android 6.0, which was released in 2015, I am not sure when the special permission system was implemented however.


  • Hate? No, I do not hate Google. I still use a Pixel phone (and photos/assistant on it), my Gmail is still my primary email (I also self-host a few other domains but those are primarily used for automation and a few other one-off things), I subscribe to YouTube Premium, I still utilize my Stadia controller as my primary game controller, I use a Google TV set top box, etc.

    I don’t use Search (I use Kagi instead), I don’t use Chrome (Firefox), I don’t really utilize Gemini all that much (I just run ollama for the few times I want to use an LLM).

    Really I just use their products that work well for me, and don’t use the ones that don’t. There’s no love/hate about it.