colde
Joined 9 years ago
Joined 9 years ago
If Google set up a subsidiary in Europe, that ran the service for european users and was the only entity that had access to the data, this would not be a problem. The problem here is Google's insistence that US entities will be allowed to access european data.
This should not be something that is allowed on public roads by end-users, but rather on closed tracks by specialists. If they want to test it out on public roads, run the analysis and look at whenever it diverges from the drivers decisionmaking instead.
It was heavily promoted by Exodus Cry, an organisation that seeks to completely ban porn, strip clubs and any type of sex work: https://en.wikipedia.org/wiki/Exodus_Cry
This whole thing has lead to a lot unintended consequences that has significantly hurt, or impacted sex workers negatively, such as the MasterCard changes that made Onlyfans try and get rid of sexual content.
"We have no bell curves or rankings or quotas such as “cut the bottom 10% every year.” That would be detrimental to fostering collaboration, and is a simplistic, rules-based approach we would never support" from https://jobs.netflix.com/culture
1. No personal information at all. It only says valid or not valid. 2. Name and date of birth 3. Foreign travel, with name, date of birth as well as information about test type or vaccination type etc.
For Media services, the supporter will almost always need to coordinate with an internal team, which there is no visibility over, and then it becomes a game of telephone to make the supporter relay the information in a way the internal team understands. I've had the same thing happen with peering/networking related questions.
For EC 2, VPC, DynamoDB kinda questions, they are indeed pretty good.