I can't believe how much BS we have to hear about consensual sex these days to the point people are suggesting contract before making love, and yet the virtual signalers in the valley can't still see the problem with forcing people to be spied upon even when told to piss off.
Maybe too many new web framework turn over also burnt out their common sense?
Silicon Valley still seems to have a huge problem with the concept of user consent and giving users meaningful choices. If "Silicon Valley" was a human being, it would be that creepy guy in the club hitting on everyone, saying "Do you want to be my girlfriend? [YES] [Ask Me Again Later]"
You could also show the same person, 10 minutes prior, telling their locksmith they should say "main-key" instead of "master-key" because that's inappropriate, otherwise they won't call them for more gigs.
>people are suggesting contract before making love
I would unironically require this simply because the legal liability risks are too bloody high otherwise.
Not that I would get myself into such a situation in the first place. In this day and age there are many other avenues of entertaining oneself without the ridiculous liability risks.
GDPR deals with user identifiable data or that can be tied to the identity of a user through partially anonymous data.
It should be fine to collect "telemetry" as long as the data itself isn't personal and that it also cannot be tied in any way to a particular user.
At least, this is how I've interpreted the GDPR rules.
On the other hand if you tie telemetry to a user ID, fingerprint, unique device identifier, etc, then all the data is personal, and since it's not obvious and necessary, you also cannot argue its a legitimate interest (note that most GDPR popups arguing legitimate interest are absolutely not valid).
Well, tracking users by cookies or fingerprinting or whatever can tell you that by combining data from different sources. Now we've looped back around to being in favor of the most intrusive methods.
As I said that is a "piece of information", not the whole story. Making an axing decision with ONLY that information would be outright idiotic.
Telemetry has to be designed as well, to piece as much as you can, and then you complete the full picture with other sources. Maybe not everybody does this, but I don't think that this practice should be "shocking" for anybody.
yea you sound like someone who is competent and will actually thing things through and make a rational decision. Many people are not and will latch on to the information "only 1% of people use it!" and refuse to listen to why that may not matter"
Well, in Europe, if you want to know how much a user pays, you need to tie telemetry to their account containing personal information, which is forbidden by GPRD unless they give their explicit consent and they have a process to delete/rectify/download all of it.
Since most telemetry are optout and don't bother about giving users access to their data, they can't legally do it.
That's my point really: useful telemetry is really, really invasive. So just ask consent, and accept most users will tell you no.
If you chose what's convenient instead, you will not only have a mixed bag of data, but also you have decide to basically force yourself on people, in an age where a part of your userbase is getting upset over things like using the wrong pronoun on them.
I tell yes to Firefox and VLC to report on my usage. It tell no to Google and Microsoft. They want their cake and it it: behave badly, and then have we trust them.
Right. A mention in the ToS does not equal real consent. I would only add that it also has to be informed consent. Saying something like "can we collect data from you to improve our products and services?" is also not soliciting real consent, because it tells the user basically nothing about what is being asked of them and how it will be used.
You think that keeping track of "This paying user uses this and that feature, and is thus on the correct price plan" is a violation of the GDPR, assuming it's mentioned in the privacy police and maybe ToS?
I don't know what does or does not violate the GDPR, and I'm not talking about metering services. I'm talking about telemetry for installed software.
I'm not even talking about what the law says, because the law is very inadequate on these matters (in the US, anyway). I'm talking about, from a common-sense point of view, what "consent" is.
In my view, it can only be counted as "consent" if I have been informed exactly what it is that I'm consenting to, and I am asked for that consent.
ToS don't count for a number of reasons, starting with the fact that nobody reads them, it's unrealistic to expect people to read them (because everything comes with lengthy ToS documents and if you really read them all, little time would be left to do anything else), they are generally difficult to properly understand if you're not a lawyer, and they are are usually intentionally vague of this issue -- which means the "informed" part of "informed consent" isn't satisfied even if you do read them.
I think the Principle of Least Surprise should apply here. If software is going to do something that users won't notice happening, is intrusive, and isn't pretty obvious from the nature of the software, the right thing to do is to tell the user about it and ask for permission.
Software that doesn't do this is adversarial to the user.
That seems interesting, when thinking about pro rated subscription fees -- if a feature isn't being used, it'd cost nothing. But with telemetry disabled by default, the company couldn't detect that the feature wasn't being used, and thus the customer would pay more. And if opting in to telemetry, the customer pays less and the company gets telemetry.
The first one is French dubbed in russian. If you speak russian, I would recommend it as it as the slides clearly in view.
However, the second one, in English doesn't show most of the slides, and they are really necessary to get the full picture. However, it's a playlist, and there are better ones in there.
If you don't mind, I will update my comment to include one of them.
It's been the case for python for a while and nothing bad happened. Nobody started to use accentuated variables. But I finally could put my name in comments without having to put a # coding header, which is nice.
Genepi production is pretty limited itself because of the heavy restrictions on the plant harvest, espacially since it grows mainly in the Alps. And the Mercantour rangers are not tolerant of people picking more than their share.
That's basically what the Academie Francaise have been doing all along for French and why we have words like "courriel" instead of email in the dictionary despite the fact most people never use them.
A bit of consistency is good, I find, but not actually in actual words.
The real consistency you should aim for is pronunciation. Especially for loanwords. Yes, the first time you encounter "CD" spelled out in your native language, it's jarring, but over time the benefits of this add up.
If you aim to make your language as phonetic as possible, suddenly acquiring the language is much easier. Still very hard, but a degree of difficulty easier.
I can't believe how much BS we have to hear about consensual sex these days to the point people are suggesting contract before making love, and yet the virtual signalers in the valley can't still see the problem with forcing people to be spied upon even when told to piss off.
Maybe too many new web framework turn over also burnt out their common sense?