• 15 Posts
  • 1.27K Comments
Joined 10 months ago
cake
Cake day: November 12th, 2024

help-circle



  • If it is the system launcher and that permission was provided automatically, all you need to do is use another launcher.

    I am using stock android on a smartphone that was in the Android One program. I have not changed the the launcher.
    My expectation when keeping the Google first party screen lock thing is for it to not make it easier for me to make the mistake of leaving the phone unlocked.

    At this point, any app installed on a certified Android device in these regions must be registered by a verified developer.

    And that will mean that if I were to feel like making my own app for the smallest of things and just install it on my own phone, I need to tell Google: “Hey! I am programming for Android!” as if they don’t already have enough of my data.
    And then sideloading would probably require signing it with a certificate, so Google will always know that I made a software and installed it on my phone.

    There is no PR stunt here

    Yes. There is no PR “stunt” here. Not everything that includes PR is a stunt.

    Using the phrase “PR flavour text” refers to whatever PR is saying to make the actions of a company, seem less controversial. And that is the main job of a company’s PR department.
    In this case, it is:
    ‘This change aims to reduce malware and scams associated with unverified apps, as sideloaded apps are significantly more likely to contain malicious software’

    And yes, that thing is a lie as you already explained. That is why I call it PR flavour text.


    2027 and beyond: We will continue to roll out these requirements globally.

    This just gives me a deadline for switching to a Linux phone.
    Seems to have come earlier than what I thought I would be able to manage, but I will have to manage somehow.


  • What’s their PR flavour text for that?

    And how does a company get the authority to do a “ban”? Isn’t that supposed to be a Government thing?

    Seems like their real goal is to make the users of their devices as vulnerable as possible. How?

    • First they remove the ability for other apps to record phone conversations, so we can’t use call recorder apps
    • Then, in the recording feature of their own app, they don’t record the part where it says, “This call is being recorded”, making it possible for anyone to claim that they had not been informed of the call being recorded.
    • While the phone goes screen-off and lock in 15 seconds (that’s the timer I set) when doing something useful, like reading stuff on a website, if I leave it on the home screen, it seems to randomly decide sometimes that it doesn’t want to turn off (last I checked, I waited for > 2minutes before I pressed the off button myself)
      • and then using the off button too much, will make it go bad faster, which will then not have a replacement.
      • they will definitely call this a “bug” if the matter falls out of their hand. But until then, they will keep on denying it. Do they even read bug reports?


  • Well, I have seen drains clog up so bad that the parapets act like a bowl and capture the ~1m of water with the roof still staying mostly intact (although seepage would have greatly increased there), so something other than my calculations is holding up that roof.

    So I guess one would have to rely on the melting-refreezing to break down the roof, considering that without the phenomenon, the ice would be pretty fluffy and light.


  • ulternotoProgrammer HumorGIT the Princess
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    6 days ago
    git clone git@⏻_toggl:Goon%20Squad/CastleWithPrincess.git
    cd CastleWithPrincess
    git log
    git diff add-captured-princess^ add-captured_princess > ~/.cache/captured_princess_import.diff
    git reset --hard add-captured-princess^
    git push --force
    cd ~/Documents/prince-home/
    git clone git@kingdom:Prince/MyHome.git
    cd MyHome
    git apply ~/.cache/captured_princess_import.diff
    git commit -a -S -m "Your Majesty, the princess is now in your grace."
    git push
    systemctl start wait-for-munneys
    

  • ulternotoProgrammer HumorGIT the Princess
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    6 days ago

    left standing…

    Look closely, not standing.
    Being crushed underneath the overflow.


    Those that were left standing, however:

    • JavaScript: standing, staring at the ruins, contemplating Docker
    • C#: standing in line, probably hungry after not seeing a payday despite having paid the electricity bill for running Visual Studio for hours, on top of Windows license
    • Java: The horse is standing
    • Lisp: The creature generated from the 3 combined may be considered as “standing”
    • Go: Everyone seems able to stand on their own. I don’t see a problem
    • Pascal: At least the princess is still standing. Maybe not for long though.


  • Here’s what I’d give to 10y/o me.

    1. Explain partitions and filesystems (I already knew CPU, HDD, RAM etc)
    2. Explain the boot startup process
    • and how limited the motherboard’s mechanisms and the pre-OS environment is
    1. Hand over:
    • 1 working computer with an empty internal HDD (no OS pre-installed)
    • 1 USB drive with Debian ISO
    • 1 USB drive with Arch ISO
    • 1 other internet connected device with a pre-installed web browser

    Don’t do this to others.







  • Or worse still, reacting like Lemmy and Reddit did and somehow use this as an argument against Arch.

    Well, I have only seen it being used in “AUR vs Official Repos”.
    Maybe I just don’t subscribe to those types of channels.

    I’ve honestly found it easier to manage AURs than PPAs.

    And there is absolutely no way the App Stores can logically get a 1 up over the AUR in this case.
    Arch doesn’t even include an AUR helper in the Official Repos, hinting to users that they are on their own. On the other hand Apple keeps on advertising themselves as “safe”, “private” etc.
    The 2 have clearly set a different standard for those and need to be treated with said different standard, which clearly should be harder on the Apple side.