Comment by HiPhish
11 hours ago
We need to stop calling it "sideloading", we should call it freely installing software. The term "sideloading" makes it sound shady and hacky when in reality it is what we have been able to do on our computers since forever. These are not phones, they are computers shaped like phones, computer which we fully bought with our money, and I we shall install what we want on our own computers.
I like the term "direct install" which someone suggested in one of the previous threads.
Or just "install". This word was sufficient my entire life until the Apple App Store came along and hijacked it.
"Why should I change my name? He's the one who sucks"
https://youtube.com/watch?v=ADgS_vMGgzY&t=3s
You could certainly say that. But if you go up to a normal person on the street and say "Google has prevented you from installing apps on your phone", while they're still able to install from Google Play just fine, they're going to look at you like a crackhead.
Language is for conveying information to other people. If your audience doesn't understand what you're saying, you're effectively screaming into the void.
1 reply →
Would it be possible to exclude app store install from "Install", eg swapping positions with sideloading? The idea would be that "app store sideloads" are more like enabling features than installing something novel, and installs allow something unplanned to be enabled.
I wonder where the term started?
Android itself calls it "install" when you open an APK file, there's not mention of "sideload" in Android at all as far as I can tell.
There is, actually, but in a different context. The `adb sideload` command allows you to boot a device from an image without flashing it.
This command is also used to install 3rd-party ROMs.
There is an option in the TWRP recovery tool to sideload any capable .ZIP file.
How badly screwed are we that the term "installing" doesn't work because it doesn't exclude the now default assumption that someone else controls everything you are allowed to install.
>The term "sideloading" makes it sound shady and hacky
"side" refers to the fact that it's not going through the first party app store, and doesn't have any negative connotations beyond that. Maybe if it was called "backloading" you'd have a point, but this whole language thing feels like a kerfuffle over nothing.
I get where you are coming from. However, language like this matters when it comes to legislation. People outside there space will be guided by the sideload language to think it's just "something extra on the side so why should I care?"
Agreed. "Sideloading" has been marketed as a boogeyman opening doors to malware, when in fact malware exists on the play store anyway.
1 reply →
Sounds like "sidestepping" i.e. doing something illegitimately or at least outside the normal path.
Language strongly influences how people perceive things. For example, people shown videos of a car crash estimated higher speeds and falsely remembered seeing broken glass if the crash was described as "smashed" or "collided" rather than "hit" or "contacted"[0].
"Direct installation" sounds neutral to me, but "sideloading" sounds advanced or maybe even sneaky.
[0] https://www.simplypsychology.org/loftus-palmer.html
Mandatory googleloading.
if anything, installing the app spoon fed to you by your phone OS provider should get the pejorative.
Let's calling, "Lameloading" or something to really nail it home.
How about "unlocked install"?
Consumers are already familiar with what a "locked phone" is.
Unfortunately not. They are calling it "phone" and ("rooted phone" or "unlocked phone").
Sounds too much like illegal jailbreaking. Direct install better IMO
I like your point. Never thought of it that way. Totally agree
If Google provides a permanent mechanism to disable this in developer settings, then this devolves to an inconvenience.
The setting to allow unsigned apps could be per appstore tracked by an on-device sqlite database, so a badly-behaving app will be known by its installer.
Have you read anything about this? What you are proposing is exactly what is being disabled.
Let's say that Google implements this restriction, but allows F-Droid a permanent permission to disable it for apps installed through their store.
Then there is both increased protection and accountability.
8 replies →
indeed, but they're not talking about your phone, they're talking about android, which is something you don't buy nor own, you buy a license to use it on the provider's terms.
linux phones can't come soon enough ...
your point about the termn "sideloading" is spot on, though. perverting the language is the first step of manipulation: installing software is "sideloading", sharing files is "piracy", legitimate resistance is "terrorism", genocide is "right to defend oneself" ...
> which is something you don't buy nor own, you buy a license to use it on the provider's terms
The distinction between "own" and "license" is purely a legal one. If I buy a kitchen table I own it, I can chop it up and use the pieces to make my own furniture and sell it. When I buy a copy of a Super Mario game I cannot rip the sprites and make my own Super Mario game because I don't own the copyright nor trademark of Super Mario. But I do own the copy, and Nintendo does not get to march into my home and smash my games because they want me to buy the new one instead of playing my old ones.
> linux phones can't come soon enough GNU/Linux. I used to think Stallman was being petty for insisting on the "GNU" part, but nowadays I understand why he insists on calling it GNU/Linux. There is nothing less "Linux" about Android than Debian, Arch or any other GNU/Linux distro, but GNU/Linux is fundamentally different in terms of user freedom from Android.
> Nintendo does not get to march into my home and smash my games because they want me to buy the new one instead of playing my old ones.
This is a really interesting example to choose because the new Nintendo Switch 2 cartridges have literally no data storage except to hold a license key. The content has to be downloaded from their servers, which they absolutely will take offline eventually.
> linux phones can't come soon enough ...
That would require a lot tighter and broader (but not corp-controlled) organization than what open source is accustomed to - making cheap and capable phones that aren't tied to a big corp is big challenge.
> "your point about the termn "sideloading" is spot on, though. perverting the language is the first step of manipulation [...]."
Precisely.
> when in reality it is what we have been able to do on our computers since forever
You do realise that's been changing right? Slowly of course, there's no single villain that James Bond could take down, or that a charistmatic leader could get elected could change. The oil tanker has been moving in that direction for decades. There are legions defending the right to run your own software, but it's a continual war of attrition.
The vast majority of people on this site (especially those who entered the industry post dot-com crash) ridicule Stallman.
"Dan would eventually find out about the free kernels, even entire free operating systems, that had existed around the turn of the century. But not only were they illegal, like debuggers—you could not install one if you had one, without knowing your computer's root password. And neither the FBI nor Microsoft Support would tell you that."
https://www.gnu.org/philosophy/right-to-read.en.html
Yeah in the name of "security".
Unfortunately it also means giving the key to the Kingdom to a company like Microsoft or Google which are definitely adversaries in my book. Keeping them in check was still possible with full system access.
Even Apple I don't trust. They're always shouting about privacy but they define it purely as privacy from third parties, not themselves.
And they were the first to come up with a plan where your phone would spy on you 24/7.
> The vast majority of people on this site (especially those who entered the industry post dot-com crash) ridicule Stallman.
I've been in tech and startup culture for over a thousand programmer-years (25-30 normal years). It wasn't dot-com or the crash. It was mobile. The mobile ecosystem has always been user-hostile and built around the exploitation of the customer rather than serving the customer. When the huge mobile wave hit (remember "mobile is the future" being repeated the way political pundits repeat talking points?) the entire industry was bent in that direction.
I'm not sure why this is. It could have been designed and planned, or it could have evolved out of the fact that mobile devices were initially forced to be locked down by cell carriers. I remember how hard it was for Blackberry and Apple to get cell carriers to allow any kind of custom software on a user device. They were desperately terrified of being commoditized the way the Internet has commoditized telcos and cable companies. Maybe the ecosystem, by being forced to start out in a locked-down way, evolved to embrace it. This is known as path-dependence in evolution.
Edit: another factor, I think, is that the Internet had no built in payment system. As a result there was a real scramble to find a way to make it work as a business. I've come to believe that if a business doesn't bake in a viable and honest business model from day zero, it will eventually be forced to adopt a sketchy one. All the companies that have most aggressively followed the "build a giant user base, then monetize" formula have turned to total shit.
Ironically, to take it full circle, I think that the thing that led to mobile being so user-hostile was the lack of sideloading of apps.
I remember sites on the early web like Hampster Dance, where monetization happened as an afterthought. But if you have to pay $99 annually and jump through hoops just to get your software even testable on the devices of a large number of consenting users, the vast majority of software is going to be developed by people who seek an ROI on that $99 investment - which wasn't cheap then and isn't cheap now. Hampster Dance doesn't and wouldn't exist as an app, because Hampster Dance isn't made as a business opportunity.
Similarly, outside of a few bright lights like CocoaPods, you don't get an open-source ecosystem for iOS that celebrates people making applications for fun. And Apple doesn't want hobbyist apps on its store, because Apple makes more money when every tap has a chance of being monetized. Killing Flash, too, was part of this strategy.
Apple certainly could have said "developers developers developers" and made its SDK free. But it realized it had an opportunity to change the culture of software in a way where it could profit from having the culture self-select for user-hostility, and it absolutely took that opportunity.
It's not a bad place, the environment we live in. But IMO, if Apple had just made a principled decision years ago to democratize development on its platforms, and embraced this utopian vision of "anyone can become a programmer"... it could have been a much brighter world.
> I'm not sure why this is
I think a big reason was customers' ignorance. The manufacturers can come up with whatever they want, if no one buys it it does not matter. People accepted locked-down smartphones because they saw them a phones first and foremost. If I recall correctly the iPhone released without any app store, so it was really not that different from a dumb cell phone. If you had offered those same people a desktop PC or laptop that you could not install your own programs on, that had no file explorer, that could barely connect to anything else no one would have bought it. But because they say smart phones as telephones first it flew over their head. How many of the people who are upgrading to Windows 11 now because of lack of security support are still running an outdated smartphone? The phone probably has more sensitive data on it than the PC by now.
People are willing to accept restrictions when they come with newer technology. Why is that? I don't know, I'm just reporting on what I see.
I suspect the average computer user is significantly smarter than the average phone user. The reason is that I've never seen a really dumb person using a computer, but I've seen plenty using phones. That might (or might not) be related to why the phone ecosystem evolved the way it did and computers didn't end up like that.
It was mobile. The mobile ecosystem has always been user-hostile and built around the exploitation of the customer rather than serving the customer.
Right. It was infuriating when those of us criticizing the iPhone's restrictions were told "it's just a phone, who cares", when it was clear that mobile computing was going to take over quickly.
If you want a real blackpill (I think this is the right word), consider the famous Cathedral and the Bazaar.
I recently had a realization: I can name Cathedrals, that are 800 years old, and still standing. I can't name a single Bazaar stall more than 50 years old around any Cathedral that's still standing. The Cathedral's builders no doubt bought countless stone and food from the Bazaar, making the Bazaar very useful for building Cathedrals with, but the Bazaar was historically ephemeral.
The very title of the essay predicts failure. The very metaphor for the philosophy was broken from the start. Or, in a twisted accidentally correct way, it was the perfect metaphor for how open-source ends up as Cathedral supplies.
There are definitely bazaars which have a very old history. Being that the word "bazaar" has middle-eastern origins it feels appropriate to highlight middle eastern bazaars. Al-Madina Souq in Aleppo is one such bazaar with quite a few shops/stalls/"souqs" dating back to the 1300's or 1400's, such as Khan al-Qadi (est. 1450). Khan el-Khalili in Cairo has its economic marketplace origins rooted in the 1100's-1300's.
4 replies →
I fail to see the link, businesses come and go. Their software dies with them.
8 replies →
The title also correctly describes the relationship between FOSS and cloud SaaS. FOSS is the bone yard and parts catalog that devs go to when building closed platforms to lock in users. It largely exists today to be free labor for SaaS and training data for AI.
I'm not there yet, but I am perilously close to tipping over into believing that making open source software today is actually doing harm by giving more free labor to an exploitative ecosystem. Instead you should charge for your software and try to build an ecosystem where the customer is the customer and not the product.
I stress today because this was not true pre-SaaS or pre-mobile. FOSS was indeed liberating in the PC and early web eras.
I always found this term utterly bizarre. It first showed up in the early days of the mobile "revolution" and felt astroturfed, since no developer would think we need a fundamentally new term for downloading software. It felt like something some dark patterns team came up with to discourage free installation of software on your own device.
Of course maybe I'm overthinking it. It's common for people deep in the bowels of an industry to invent pointless jargon, like "deplane" for getting off an airplane. Anyone know where the term "sideload" was coined or by whom?
No I don't know.
But: "side talking" Is a worthwhile distraction to Google and look at Nokia N-gage memes.
I prefer the term "unlocked install". Consumers are already familiar with the terms: locked phones and unlocked phones.
I call "running unsigned binaries"
They are signed, though. Just not by Google.
“Running binaries signed either by yourself or by whoever wants to spy on you.”
That last part there is the problem.
6 replies →