• 0 Posts
  • 37 Comments
Joined 9 months ago
cake
Cake day: December 7th, 2023

help-circle




  • Yep! I’m pretty sure I can remember Resetti in the original Gamecube version making me cry as a kid after getting yelled at for accidentally turning off the system without saving…

    I also remember Phyllis, who basically hated your guts for interrupting her night shift.

    And of course there’s the actual villagers of the town too, some of them were definitely a lot more… liberal… with you, personality wise!


  • Well, my father’s funeral service was today. I lost him at the beginning of the month.

    It’s been rough. There were a lot of issues between him and I during my childhood which caused me to quickly cut off contact with him after I moved out. But I’d always hoped that eventually there would be a way to fix things, and now that will never happen.

    So there’s a lot of guilt. I do not think it was wrong to remove him from my life, but it was never intended to be a permanent thing - it’s forever written in stone as it is now though.

    I need to get into some grief counseling, but starting that process has been difficult for me. It doesn’t help that I already have a lot of other medical issues constantly ongoing, and now this is just another thing to add to the list.










  • 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.





  • I dual boot on my primary/desktop PC, and only run Linux on my laptop and Steam Deck.

    I find more often times than not, I feel like I’m either fighting with Windows or it does these small but annoying things that when added up tend to really get on my nerves. For example, one thing that I’ve been running into a lot (and happened earlier today) is if I put my computer to sleep while its booted into Windows, it’ll randomly decide to wake itself up for who knows what reason - flooding my room with light often times while I’m trying to sleep or relax. It does it enough where I should by now remember to just physically turn off my monitors when I put my computer to sleep, but why should I have to? The 95% of the time that I’m booted into Linux, if I put my computer to sleep it stays asleep until I explicitly wake it up, and thus I haven’t formed a habit to turn the displays off.

    The only reason why I even keep Windows around on this PC is to occasionally play Destiny 2 and some VR stuff with friends every now and then.