• 1 Post
  • 234 Comments
Joined 3 years ago
cake
Cake day: June 14th, 2023

help-circle




  • I don’t disagree with anything here.

    But my point wasn’t “there’s nothing to worry about”, it was “an age field is the minimum they can do, and blaming them for it is pointless”.

    My point is that this law is already there, and the fight needs to be brought where it matters, and the code of linux systems is not what is going to change politics. When someone is held at gunpoint, you don’t yell at them to fight back and curse them when they don’t, but you attack the attacker.


  • As I said, it’s a loss. It is not going to bring anything good, and can only bring bad stuff.

    But my point is that the alternative of ignoring this law would just worsen the situation.

    If you want to fight a law, you need to do it with meaningful measures. You find flaws, you revolt, but you don’t just ignore the law and hope to not be attacked for it.

    If a big linux distro does it, it will lead them to endless legal battles that will ruin them, and then what?

    The strategy here is to accept the loss, mitigate it as much as possible, and attack the source, which is politics, governments, and popular support and understanding.

    Explain to people why it’s bad, burn down the government, and fix the system. If we only fight the symptoms when they target us, we’ve already lost.


  • And what would refusing a field do?

    What needs to be done is basically a revolt against current governments and capitalism, not nitpicking every privacy-invading law that comes, and then waiting patiently for the next one to come.

    You’d rather put a big target on linux systems for stupid fucks to label it as “the big danger for our kids” which would just bring nothing good.

    You want to stop taking hits, then stop waiting for them and then pretend that dodging is the only solution.


  • It could be a slippery slope. That’s why the point is not to just accept it and move on, but to comply while pushing back against it.

    And complying right away, but with a bullshit field, is a good way to signal “we do not agree, and we’re going to always find a way to fight back”.

    Taking a hit to avoid defeat, does not mean surrendering. It just means that you need to recognise when a battle is lost. In a way, the other side of the slippery slope is the sunk cost fallacy, where you refuse to admit that something is a lost cause and you keep on pushing, making things worse.

    It’s a matter of balance and reason, which people nowadays reaaaally struggle with.



  • I don’t know what people expect.

    All big linux distros are going to be quickly a target, because the people who like age verification laws like that hate the idea of free software.

    Putting a dummy, useless age input, is a good way to comply maliciously, and can be easily reverted if these stupid laws ever get removed.

    It wouldn’t surprise me if obvious ways to bypass it appear a few seconds after the changes are validated.

    The alternative is that these systems could be outawed in a lot of places, which would have a much more negative impact than an age field.

    War is about knowing to take a hit to avoid defeat, sometimes.







  • I have no idea what you’re talking about.

    For a book, there are per-unit costs of the materials, ink, paper, manufacturing, etc.

    For an ebook, these are void. So the cost should be, at the very least, much lower than a physical book. Even if you take into account the effort of writing the book and such, it’s an initial cost, so it doesn’t justify a high price.

    The point being, physical items have costs related to their physicality, digital items don’t, so they shouldn’t cost as much. It’s pretty straightforward.

    And to loop back to my initial comment: that’s why it’s absurd to compare AIs, which are just bullshit for lazy sloppy people, and manufacturing processes, which come from the need to reduce the manufacturing costs of physical items. There is no manufacturing cost of software, so there is no need to mass-produce as fast as possible, and so there is just no reason to let devs throw up slop garbage to go “faster”

    Also, on a side note: programming with AIs don’t make you code faster, it just increases the amount of bugs and problems with your code. Obviously, since you’re just using a nonsense generator to try to produce a complex piece of digital machinery.