| ▲ | gjsman-1000 9 days ago | |||||||||||||||||||||||||||||||
* * * | ||||||||||||||||||||||||||||||||
| ▲ | Ajedi32 9 days ago | parent | next [-] | |||||||||||||||||||||||||||||||
Yes, I think quibbling over the origin of the term and attempts to coin an alternative are a useless distraction. The term emerged organically for good reasons, and doesn't have any negative connotations as far as I'm concerned. Trying to talk about "direct loading" instead is confusing and doesn't even make sense because alternative app stores like F-Droid don't count as "direct loading" under their own definition. I think defining sideloading as "the transfer of apps from web sources that are not vendor-approved" is a good definition, because "not vendor-approved" is precisely the part I care about. The owner being able to install stuff without Google or anyone else's approval is a good and important capability for every computing device to have. In any case, I fully agree with the substantive portions of this article. What Google is doing here is a terrible attack on consumer freedom. | ||||||||||||||||||||||||||||||||
| ▲ | secstate 9 days ago | parent | prev [-] | |||||||||||||||||||||||||||||||
While I wont argue about it feeling like a conspiracy theory, I will argue that pretty much no one knows sideloading as a term with regards to what i-drive meant by it. And the fact that `adb sideload` is where the concept originated does nothing to dispel the way the term is frequently used in a derogatory fashion these days. It's wielded as a bogey man to make people afraid of unsigned applications. Despite the fact that many perfectly signed applications are full of malware and dark patterns. Also, FFS, this is hacker news. Why on Earth would be arguing in favor of Google locking down how I can install software on my device. | ||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||