![Avatar](/_next/image?url=%2Flemmy-icon-96x96.webp&w=3840&q=75)
cbarrick
Phone cameras tend to ramp up the saturation.
It gives the photo a more vibrant look, which many people prefer, at the expense of color accuracy.
But generally with artistic photography, you’re going more for a style than for accuracy, so I wouldn’t say it’s always a bad thing (though sometimes it is).
In this example I would have committed both crimes.
It’s copyright infringement for me to republish and profit from your work without your consent (while that work is not in the public domain).
It’s plagiarism for me to pass that work off as my own.
So it was a bad example.
Let’s say you write a novel. It’s really really good. But no one reads it because no one ever hears about it.
Later, I stumble upon your novel and recognize how great it is. Then I republish it verbatim, except with my name as the author. I am much better at business and marketing than you, so it goes viral. I receive millions in sales, am tapped to produce a movie version, and win a Pulitzer for it.
Is that fair? Or should you have some rights in all of this since it was your copy?
TL;DR - We can now control swappiness per cgroup instead of just globally. This is something that userspace oom killers will want to use.
Or surveillance.
It’s all “privacy, privacy, privacy” when it comes to private companies. But the EU themselves wants all of that data to create a surveillance state.
Not that the US government doesn’t pull the same shit, but it does feel less hypocritical when they do it, because they’re not even pretending to be concerned with privacy.
You don’t need to provide root access just because you used GPL code, you just have to follow the GPL.
Well, to follow version 3 of the GPL, you do actually need to provide effective root access.
Specifically, version 3 of the GPL adds language to prevent Tivoization.
It’s not enough to just provide the user with the code. The user is entitled to the freedom to modify that code and to use their modifications.
In other words, in addition to providing access to the source code, you must actually provide a mechanism to allow the user to change the code on the device.
The name “Tivoization” comes from the practice of the company TiVo, which sold set-top boxes based on GPL code, but employed DRM to prevent the user from applying custom patches. V3 of the GPL remedies this bug.