The much more noticeable factor will be reducing how many people even care about gas prices in the first place.
13,439 karma · joined January 5, 2015
The much more noticeable factor will be reducing how many people even care about gas prices in the first place.
They would still exist, just not in any country insane enough to pass a ridiculous law like this.
This sort of personal liability OP is proposing would just ensure the security industry is dominated by highly compensated compulsive gamblers because nobody else is insane enough to take the risk. It's an absolutely ridiculous idea.
I think if you want to be able to block your neighbors from building denser housing on their property then that should only be enforceable if it was agreed to by everybody in advance when they bought the place (e.g. via an HOA contract or some similar type of restriction on the property deed). Otherwise this is tantamount to allowing Walmart to get a vote on whether to allow Target to set up next door.
Yeah, by definition this is pretty much always true, no? No matter how scarce local workers are, if you were willing to offer double the market rate you could probably find someone. Scarcity and price are two sides of the same coin, that's how markets work. Bringing in labor from another country when local talent is scarce both reduces costs/wages and reduces scarcity.
Just to be clear, the conversation so far:
> beloch: It's also completely fine to say, "I don't want to deal with moral grey zones" and refuse to work for companies that do military work.
> JumpCrisscross: Idk, there's something unethical in outsourcing ethical grey areas [working for defense contractors] to other people while reaping the benefits of the peace (or war far from your home) it brings.
> sophacles: "someone else will do it if i don't".... (aka your argument)
> me: That's not the argument. It's more like "if I don't [work for defense contractors] then I better hope somebody else will. [Because strict pacifism isn't tenable.]
You then somehow interpreted this comment as me saying "a nation taking actions off the table "will inevitably become subservient to a despotic regime"", which wasn't at all what I said, so I jumped back in correct that. Then the whole conversation went off the rails.
> Serious question: should companies not participate in contracts from their country's defense department?
I contend that unless you want your government to be toppled by a foreign invader, companies contributing to your nation's military capabilities is something you should generally be in favor of.
That's not the argument. It's more like "if I don't do it then I better hope somebody else will, otherwise my whole country will inevitably become subservient to a despotic regime". Basically, the question is whether strict pacifism is a tenable national policy in the real world. All of modern and ancient history up to this point seems to suggest it is not.
Because yes, this nonsense would never fly in a world where Software Freedom enabled a competitive market for TV operating systems.
> You're just whining because you wish you could have root access on your system
This is false, and I think it's intellectually unhealthy to use your perception of a person's motives as an excuse to avoid mentally engaging with the substance of their argument.
Yes, GrapheneOS is free, but it has implemented features that are designed to make it harder to exercise that freedom, namely secure boot which puts it one short step (of baking their key in hardware) away from being exactly what that paragraph describes as not free.
(And I think you are the one misunderstanding the FSF's quote. They're mocking "secure boot" as perverse terminology for what the FSF calls "tivoization" or "lockdown". They're saying those things are one in the same. I personally wouldn't go that far, as I agree with you the software is still free as long as the key used for secure boot is not baked in to the hardware, and I think the security benefits of secure boot are real and not perverse. But the FSF itself is arguing against the whole idea, at least in this article.)
To re-iterate:
> If the program is delivered in a product designed to run someone else's modified versions but refuse to run yours—a practice known [...] in its practitioners' perverse terminology as “secure boot”—freedom 1 becomes an empty pretense
GrapheneOS literally implements secure boot, using a key you do not control. So if you install GrapheneOS, the Graphene devs have the ability to push updates to the code running on your phone but you yourself do not unless you completely uninstall GrapheneOS and wipe all data on the phone.
The only thing preventing this from being actually anti-freedom rather than merely borderline anti-freedom is that if you choose to completely un-install Graphene and wipe your phone there's currently nothing that will prevent you from installing another OS built with a different signing key (aside from the inconvenience and technical difficulty of doing so). If there were, then this would be a textbook example of what the FSF explicitly calls "not free software" in that quote.
> Freedom 1 includes the freedom to use your changed version in place of the original. If the program is delivered in a product designed to run someone else's modified versions but refuse to run yours—a practice known as “tivoization” or “lockdown,” or (in its practitioners' perverse terminology) as “secure boot”—freedom 1 becomes an empty pretense rather than a practical reality. These binaries are not free software even if the source code they are compiled from is free.
[1]: https://www.gnu.org/philosophy/free-sw.html#make-changes:~:t...
I didn't say anything about what GrapheneOS devs must do. They don't have to do anything. I just think that some of what they are doing comes close to impinging on software freedom in the same way proprietary software does regularly (though again, Graphene doesn't quite cross that line, in my opinion).
I think I have a broader definition of software freedom than you do. In this hypothetical scenario, GrapheneOS itself may technically be "free software" in the sense that the source code is open, but it would still be cooperating in a intentional scheme to prevent you, the user, from modifying it to work the way you want. Same deal if they started selling locked hardware with their signing key hard coded so you can't install a fork. You would legally have the ability to fork the software, but technical measures would be preventing you from running it.
Granted, they're not doing that, but it's one short step away. That's why I say it's borderline anti-freedom, not that it actually is.
I don't think it makes a difference whether the means employed to make a piece of software non-free are legal (copyright law) or technical (DRM, remote attestation, hardware locks). It's still restricting your freedom.
You can't use the software in the way you want if it uses hardware backed cryptography to block you from doing so.
> you get access to the sources, you modify them, build them and run them
This is completely infeasible for 99% of the population. If you technically have a freedom but have no practical way to exercise it, it may as well not exist.
You could argue "but someone else could modify it for you, build it, and make an easy way for you to install it", and normally I'd accept that, but given that installing that modified version would require you to completely reset your phone and install the new modified OS from scratch, I think it's debatable at that point whether you'd still be running Graphene, rather than a fork. And if exercising your freedom requires you to stop running Graphene and start running something else, is it really fair to say Graphene itself supports that freedom? Like I said, borderline.
If you're still not convinced, consider what would happen if companies started using remote attestation to verify you're running the official GrapheneOS build and block forks...
I think it's fair to say that that's at least borderline anti software freedom, even if it's true they have good security reasons for doing things that way.
Looking at their public statements on the matter, it seems like the problem isn't exactly that they treat the user as a potentially hostile actor so much as that they treat the system UI and persistent storage as a potentially hostile actor (though I admit from a practical perspective that's nearly the same thing): https://www.reddit.com/r/GrapheneOS/comments/13264di/is_root...
I wonder how they'd feel about something like protected confirmation to enable sudo: https://source.android.com/docs/security/features/protected-...
In this analogy, the alternative shop that is preventing you from buying stuff from its competitors without a 24 hour wait is the Play Store monopoly.
> but there could easily be a world in which your 'alternative' verifier would still make you wait 24h (or longer).
Then in this hypothetical world where there were a free market for verifiers rather than a single, monopolistic choice, I would choose another alternative verifier that doesn't make me wait 24 hours, or no verifier at all.