• sexhaver87@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 hour ago

    “They” is a pronoun. Hope that helps clear things up.

    Sideload wasn’t loaded language before Android OS and still isn’t: it’s a bogus, overreactive claim.

    The term “sideload” was coined by i-drive, a bunk dot-com contributor who applied to trademark the term because they were corporate ghouls. Their version of sideloading involved giving them a link to a file on the internet, and they would store it for you, so you didn’t have to download it yourself. The idea behind sideloading is just transferring a fucking file. It’s loaded language, despite whatever freedom or restrictions an implementation provides. Call it what it is, a file transfer.

    Clear use cases for casual users exist for

    What about the clear use case for a FOSS developer who doesn’t want to go through the Google authority for validation? What happens when Google thinks an app is dangerous when it shows no clear malicious behavior? What happens when Google enforces the idea that blocking ads is malicious?

    (even as Google turns out to be a shitty authority)

    In my opinion, what a massive understatement.

    Edit: Put the documentation where your mouth is. Show me the “clear documentation that power users can still install any package they want,” because F-Droid would like to have a word with you. While you’re reading that, do take care to note that Google already has a service to protect against malicious applications. They don’t need to limit application installs based on developer registration. They need to make a profit for their shareholders. They’re corporate ghouls.