8 ms·
This isn't just a problem with extensions, though. It's a problem with everything. Always has been and always will be. This is why people should be extremely c
by JohnFen 3y ago
This isn't just a problem with extensions, though. It's a problem with everything. Always has been and always will be.
This is why people should be extremely cautious about becoming too attached to (or, worse, dependent on) any particular product or service. It can change ownership (and therefore policies) at any time.
- sneak 3y agoThis is why people should be extremely cautious against self-modifying software (ie unattended autoupdate) - it grants remote code execution on your computer to remote parties.
- throwaway292939 3y agoAt the risk of pointing out the obvious, this is mostly referring to Internet enabled goods and services. As other commenters have pointed out, it doesn't apply as much to actual physical products. So this leads to reason, should any of this be accepted as the norm?
- anonymousab 3y agoIt's another prime example of why users should be wary of always choosing automatic software updates, and particularly wary of any company that uses security and "we know what's best for our dumb users" as an excuse for trying to stop users from using only a manual update process.
- willcipriano 3y agoBen Franklin on automatic updates: "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety."
- sockaddr 3y agoThis quote never made sense to me. My decision to prefer one of these over the other doesn't mean I don't deserve either. It's a decision I make with my own unique economic and threat parameters. Being "deserving" plays no role here.
- qohen 3y agoThe quote actually meant something rather different than people think and has been taken out of context. Here's a discussion about it[0]. First, here's the TL;DR: SIEGEL: So far from being a pro-privacy quotation, if anything, it's a pro-taxation and pro-defense spending quotation. WITTES: It is a quotation that defends the authority of a legislature to govern in the interests of collective security. It means, in context, not quite the opposite of what it's almost always quoted as saying but much closer to the opposite than to the thing that people think it means. And here's the detail, discussed just before the TL;DR (I put in some paragraph breaks): SIEGEL: And what was the context of this remark? WITTES: He was writing about a tax dispute between the Pennsylvania General Assembly and the family of the Penns, the proprietary family of the Pennsylvania colony who ruled it from afar. And the legislature was trying to tax the Penn family lands to pay for frontier defense during the French and Indian War. And the Penn family kept instructing the governor to veto. Franklin felt that this was a great affront to the ability of the legislature to govern. And so he actually meant purchase a little temporary safety very literally. The Penn family was trying to give a lump sum of money in exchange for the General Assembly's acknowledging that it did not have the authority to tax it. [0] https://www.npr.org/2015/03/02/390245038/ben-franklins-famous-liberty-safety-quote-lost-its-context-in-21st-century https://www.npr.org/2015/03/02/390245038/ben-franklins-famou...
- deleted 3y ago[deleted]
- JohnFen 3y agoI think what he was saying, in rather poetic language, is that if you give up liberty to gain safety, you won't get either of those things. I don't think he meant "deserves" in the literal sense.
- xNeil 3y agoThat's a good way to think about it. Way I saw it was - if you are foolish enough to give up liberty for safety, you don't deserve the safety anyways.
- deleted 3y ago
- pixl97 3y agoAlso Ben Franklin on turning off automatic updates: "Fuck, why are all my files encrypted"
- willcipriano 3y agoWho keeps anything important on a computer?
- trog 3y agoPeople
- willcipriano 3y agoThose people should enable automatic updates
- michaelteter 3y agoThe problem is that 99% of users will not be bothered with deciding anything regarding updates or any computer administration. So you either get automatic updates and situations like the current one, or you get out of date/exploited software.
- account42 3y agoToday where we need exploits in order to regain computing freedom I take the exploits please.
- JohnFen 3y agoTrue, but I don't think that justifies the practice at all. At the very least, software needs to do what it used to do: make security updates separate from all other updates so users can just get the security bits.
- nightpool 3y agoSecurity update: Changed old expired analytics domain to avast.com analytics to prevent user data exposure
- gravitronic 3y agoReminds me of the pending update to 1Password 7 that I keep declining because the change notes says all it does is adds a deprecation notice for 1password classic
- deleted 3y ago[deleted]
- asdff 3y agoI do this with git packages too. Sometimes I rely on something and the author then makes a move to go to a version 2.0 and ruin what I liked about the ux/ui or how the functionality behaved. I have a few privately forked packages now where I bugfix certain components alongside the author, but keep other legacy components, and even add my own functionality and behavior to my own needs. Of course, in a world of walled gardens versus git repos, none of this very powerful use of ideas and computation can be done. I can't go to the Apple app store and easily cobble together my own franken app from what I find there. It's like a step back for innovation for our species when we set up these stupid profit seeking moats and gardens.
- cubefox 3y agoWindows XP didn't have automatic updates in the beginning. So approximately nobody had the relevant security patches for Windows and IE. The result were Sasser and MyDoom.A on almost every Windows machine. It was a disaster. It seems less risky to continue automatic updates and just accept the possibility of malicious ownership change.
- LocalH 3y agoWhat? Yes it did. Windows 98 had the first version of MS's Automatic Updates, with the Critical Update Notifications. Windows ME came with actual Automatic Updates, and so did XP.
- hulitu 3y ago> Windows XP didn't have automatic updates in the beginning. So approximately nobody had the relevant security patches for Windows and IE. The result were Sasser and MyDoom.A on almost every Windows machine. It was a disaster. Except that this was due to a vulnerability in Windows which was fixed _after_ those worms ravaged the Windows users.
- account42 3y agoI don't recall the world ending because of a couple infected Windoze machines. Plus it made teenagers like myself a bit of cash for cleaning up friends'/relatives' computers.
- smolder 3y agoEarly always-connected computers with no NAT led to a lot of hard lessons. At this point many of those have been learned, and there's a lot more depth to network security. Operating systems and key tools like web browsers and ssh are hard enough that strictly necessary updates like heartbleed patches are few and far between, and are hard to miss. The majority of what gets pushed out now through automatic updates for OSs and key software is exploiting the update channel to deliver crap features that increase revenues or deepen the moats for the company pushing them. They want to ensure that they can collect maximum rent with the least effort for as long as possible. Hopefully that abuse will reach a point where the camels back breaks, and the pain of freeing yourself from vendor lock-in becomes worth it, prompting smart consumers and businesses in large numbers to use and support principled software projects through contributions of money, code and labor.
- nebula8804 3y agoIts too much effort to manage each app's update. In the age of smartphones they push an update once a day, sometimes it feels like every 5 secs. Plus if you look at the app store updates, most of the apps post nonsense in the release notes such as "fixed bugs", "Thank you for being a user of Lyft this update will make your experience even better!", or the worst kind: "You know how sometimes you just become aware of how much tension you're holding in your body, then take a deep breath and slowly let it out? This update is like that. It's still Slack, just with a tiny bit less friction." HOGWASH Slack, this update will likely cause friction! If only those people that write this crap got laid off, the world would be a tiny bit better :/ Maybe its time to declutter software that you don't control in your life just like how people declutter stuff. Every item is an additional tiny mental burden and the same goes for each closed source app installed on your phone. Maybe its better if we just forgo any "benefits" the app may provide and not bother anymore.
- WeylandYutani 3y agoAlways find it amusing I have to do a copy paste and search to find the patch notes of windows updates. It's pretty clear Microsoft seems to think nobody cares (and to be honest they're probably right).
- emaro 3y agoI don't think it's feasable to check the ownership before every update of every extension. Or what do you have in mind? Just delaying the update so there's at least a chance to catch the bad news?
- nazgulsenpai 3y agoCase in point -- I mortgaged my home with a local bank then without me knowing or being asked I became a Wells Fargo customer. At least you can uninstall the extensions :)
- JohnFen 3y agoI strongly believe that selling ongoing loans to other companies should just be flat out illegal. You entered into a contract with your local bank, not Wells Fargo. It should not be legal any party in the contract to unilaterally rope the others into a contractual relationship with someone who was not involved.
- ceejayoz 3y agoI certainly don't remember all the terms of my mortgage, but surely there's a "we can resell your mortgage" provision in the terms that we bilaterally agreed to.
- pixl97 3y agoIf you don't have the ability to strike that clause is it really bilateral?
- ceejayoz 3y agoYou are under no obligation to sign. They are under no obligation to accept a modified contract. Both sides can walk away. Both sides will be bummed, but the bank is likely to care a lot less.
- CatWChainsaw 3y agoThese kind of libertarian explanations always conveniently neglect to mention any power imbalances between the parties. When called on it the response is usually just a less polite version of "oh well".
- 3y ago
- fhd2 3y agoI think it's a particular problems with extensions because: 1. They usually mostly work in the background, don't need much interaction. It's almost like a built-in browser feature changing owners. 2. They are pretty difficult to find a business model for - as opposed to SaaS stuff and mobile apps, which people pay for rather commonly. So the choice is to a) Make no money b) Ask for donations (seems to only work if it's somewhat obnoxious) c) Make money in some creative (often shady) way d) Sell the thing.
- HWR_14 3y agoThat's a different issue. I can still run many old versions of software even if new versions are put out by some evil entity I no longer trust. Unless the software auto-updates. In which case I no longer have the old version. AFAIK, it is not easy (or maybe not possible) to opt out of extensions updates.
- jxramos 3y agoI was thinking about this is the food and personal products space. I dreamed up something like requiring some kind of notation to denote how many steps you are away from a parent company. Direct private companies with no parent would have no notation, once a parent company buys the company and its brands put a dot for every parent company above the company of the product you're now purchasing. Something to make this transfer visible.
- jxramos 3y agocome to think of it this would hide transfers between similar ranking networks where companies swapped things out.
- joveian 3y agoI think the thing to do there is to require that the controlling owner of the brand be mentioned in non-tiny print near the most prominent mention of the brand.
- account42 3y agoBetter yet, make it so each independent company only gets one trademark and companies owned by another get none. The entire purpose of trademarks is to protect consumers. Being able to use them to mislead consumers is the opposite of that.
- asdff 3y agoThis is why tools are always better than products or services. Your hammer in the drawer isn't going to one day update itself and change. Neither is some of the bash tooling that's been around for decades. And should these things change, you always have your old versions of these tools in your drawers and storage drives.
- woodruffw 3y agoI agree. I also don't think this is something that's formally solvable in the general case, at least not in a way that's practical for distracted and non-technical users. Instead, this is the kind of thing that needs to be solved on the policy level: Google and Mozilla have an interest in maintaining high-quality extension ecosystems, and ought to take a dim view of these kinds of ownership transfers.
- wongarsu 3y agoThis wasn't a big problem with software just 20 years ago. Sure, the software you used could be bought by someone else, but that just meant you might choose not to get the next version. Software didn't automatically update, and licenses were eternal and mostly tied to physical tokens, like a disk or a fancy sticker. At some point your beloved software might become obsolete, but that was because it was outpaced in improvements by other better software, not because yours got any worse.
- askvictor 3y agoBut the barriers to releasing and distributing software were much higher, as you had to work out to get it to people, and incremental release were basically impossible. So software was controlled by a handful of big companies.
- JohnFen 3y ago> So software was controlled by a handful of big companies. Not really, no. The software space was much, much richer and you could get along extremely well without using much software from the big guys.
- ipaddr 3y agoThe industry had more smaller players compared to today and a better chance to sell. The barriers were higher but expectations lower. Plus you had a fragmentation of computers and high margins. Trade shows and flea markets, magazines, shareware and asking store owners directly were accessible ways. Today we have the illusion of speaking globally but have been gatekept out by a handful of companies.
- JohnFen 3y agoAnd, to be honest, it doesn't even really have to be a problem now. I use almost entirely FSF or Open Source software. Of the proprietary software I use, it's still software that I have an installable copy of and I'll be able to keep using it for as long as I have a machine that can run it. I don't do automatic updates and actively prevent that from happening. Automatic updates are a plague that means you can't rely on the software anymore, if for no other reason than an update may (and likely will, eventually) remove or otherwise bork the very aspect that made it valuable to you. But I'm a weirdo and take care to ensure that I actually own and control the software I use. I see people getting burned because they're at the mercy of a company all too often.
- msla 3y agoThis is much less of a problem with open source software, although, admittedly, not completely unknown.
- grishka 3y agoThe problem is with automatic updates.
- rlpb 3y agoIt's not a problem with everything. Distributions tend to add editorial input here and try to do something they consider reasonable for their users, staking their own reputation on that without trying to pass it off to the component publisher. For example, I doubt that Debian would would take an update from an upstream that is detrimental to their users. They would follow a friendlier fork first. Debian maintainers follow their users' interests first. (I'm a Debian Developer) Edit: and that means you can generally trust automatic updates on Debian.
- account42 3y agoThis is why the push towards application sandboxing and distribution by the developers themselvs is IMO misguided. I'd much rather have my applications run unrestricted but vetted and if neccessary patched by a trusted third party (the distro) than lock whatever dark patters and anti-features developers come up with into a box ... where it still has access to all interactions with that box. In particular, I wouldn't trust a Firefox distributed by Mozilla without oversight but I still use the Firefox packaged by my distro.
- rlpb 3y ago> In particular, I wouldn't trust a Firefox distributed by Mozilla without oversight but I still use the Firefox packaged by my distro. But in the case of something like Firefox, distros are barely vetting anything, and are reluctant to patch because such patching rapidly becomes unmaintainable. Most dependencies don't end up unbundled, either. So distribution Firefox packages are really external packages in distribution package clothing, more so than any other package, really. This is why I want sandboxing anyway - because I understand the limits of what is practical. And sandboxing and limiting interaction through well-defined interfaces is better for security anyway, because security vulnerabilities happen regardless, and sandboxing does provide some level of mitigation. Finally, the distribution packaging model is insufficient for many users. Even if you are fine with it, most users want something newer than their distribution release, and we can see that they are prepared to give up security and system stability for it. This is a real need for these users, and sandboxed third party packaging mechanisms provide a real solution for them, even if you can manage without.
- hedora 3y agoAs a corollary, any private information that a publicly owned company has is for sale (since the company could be bought or merge), and any information any company has can be force-sold during bankruptcy proceedings. Any time a company has physical access to your data, and says they will not sell it, they are lying (unless it is privately held, and never takes on debt / pays after delivery). In particular, EULAs and other contracts do not protect your information in the above situations, since debt and shareholder obligations generally come before customer obligations, and the data is considered an asset.
- leke 3y agoI'm beginning to think Richard Stallman was correct about everything.