It doesn't cheapen the word. If discrimination is intentional and has the effect of minimizing and eventually eliminating the target ethnic group, then you have the same result as if you lined up everyone in that group and shot them.
The word is attached to the intended outcome, not the specific actions taken to achieve it.
Was, yes. That policy ended in 2017 I think, which I don't know if I call that recent. Post-2017 some evidence pieced together by a journalist suggested that IUDs and forced sterilizations were higher in Xinjiang than the rest of the country, and went up when the rest of the country went down. But you're right, their population has not evaporated.
My point about the assumption was to get you to agree that if these things are happening, we know that it constitutes genocide. At this point I don't care if you agree or not.
Well there are allegations of mass detentions, forced labor, destruction of religious sites, suppression of language, separation of children into Chinese-controlled boarding schools, coercive birth control, and sterilization.
You agreed with me that genocide is more expansive than "we're directly killing people". For the sake of argument, let's assume the allegations are true: what would you call that?
It's never meant only that, but that's not the argument. We decided that a long time ago.
Genocide refers to a People (race, kind, tribe, family, etc.), not individual people. The group is a concept, and 'killing' it doesn't have to involve the biological death of the group members. That's part of what the linked resolution is trying to say.
For example, you could go sterilize every member of an ethnic group, without killing - causing the biological death of - any of them. None of them will be able to have children, and as they die of old age, the group disappears. That's genocide.
Another example would be to forcibly separate all the members of the group and prevent them from engaging in the lifestyle associated with membership in the group (e.g. style of dress, music, food, language, worship, etc.). Over time, perhaps generations, the people basically give up trying to do any of these things if they even remember what they were. They have no group cohesion, so the group has essentially disappeared. No need to directly cause any biological death. The argument is that if this is done intentionally, it is also genocide.
Genocide as a concept is about ending the group, not specifically the individual members. It's definitely true that you can end a group by killing all its members, though.
It's overblown _right now_ because this information is not broadly available. The fear is that pervasive access to this data would lead to e.g. you or your partner not getting insurance to pay for anything fertility-related, or you not getting hired for a job you want despite being otherwise qualified, or even that <insert authority> is less inclined to take you seriously because their perception of what schizoaffective means makes them think your perception of reality can't be trusted.
Of course if you just go tell everyone you are or are at high risk of being schizoaffective, you've done it to yourself. Not having a bad outcome yet doesn't mean that a bad outcome is not now more likely.
If you are in a right-to-work state and you don't join the union, then union members know you're benefiting from the union without contributing back. Historically, this leads to an uncomfortable work situation for you.
If you are not in a right-to-work state, and the collectively-bargained contract involves a union membership requirement - which is typical? - then you have to join the union if you want the job.
This is where the gatekeeping concern comes from.
> I can't see any disadvantage for the employees in joining a union.
Unions have dues, so you're giving up part of your salary for membership in the union. If the union salary is equal or less than you would be able to negotiate on your own, it's a disadvantage for you.
We don't, but the entire world currently does, and the amount of equipment deployed that depends on it is substantial.
I would be willing to bet money that any "better call addressing system" would be a design by committee where this just gets litigated there. And we'd end up with either a system that requires KYC per-call, or has compromises similar to what we're complaining about now.
The default has the 'tang' slider at maximally tangy, which is where the yeast and wait come in. If you back off on that the recipe looks more like the standard quickbread I'm used to.
The yeast and ferment is going to make it more acidic, and more tender because the gluten will be weakened. I imagine you could use cake flour instead and get close to the same tenderness, but the flavor would be different.
You've covered dairy and acid ingredients, but I honestly have no idea what "Unrendered Berkshire pork fat" is or where I would get it. Is that bacon grease? Saltpork? Lard is common but rendered.
FODMAP stands for fermentable oligosaccharides, disaccharides, monosaccharides, and polyols. FODMAPs generate gas as side effect of being fermented in the gut. Most people just pass this gas, but for some people, usually people with irritable bowel syndrome (IBS), it can be very uncomfortable and amplify their other IBS problems.
People who are suffering from pain and bloating with no obvious cause may be advised to go on a low-FODMAP diet for a few weeks to see if their symptoms go away.
I've wondered about this. Do we really know enough about what the human brain is doing to make a statement like this? I feel like if we did, we would be able to model it faithfully and OpenAI, etc. would not be doing what they're doing with LLMs.
What if human cognition turns out to be the biological equivalent of a really well-tuned prediction machine, and LLMs are just a more rudimentary and less-efficient version of this?
So I'm not disputing this, but I set up a similar scheme to the author almost 8 years ago and conduct 90+% of my online business through the custom emails. Everything from Amazon to small local business.
In that time I have had 'leaks' twice: my State's Fish and Wildlife licensing organ, and GitHub. In both cases I assume it's more that the email ends up being public, not because of something like Apollo.
I guess it's possible that spam is getting filtered before it ever hits my inbox.
Edit: I was responding to the idea of it leading to spam, not that Apollo wasn't collecting information on me.
For those curious: I signed up with Apollo and looked at what they had on me (via the link in the flagged/dead post by fontain). The email address they have is technically correct, but it's a non-current work email. It's still active and I do get a lot of senseless/bizarre business sales inquiries on that address. The phone number they have is wrong and I don't recognize it. They have my LinkedIn byline; it's likely how I was 'found' so quickly, as my username is the same there. I'm listed as cold.
Does it solve anything? I don't see this as a GitHub problem, it's a "we built a dependency management system with untrusted publishers" problem.
GitLab's `include` feature has the same concern. They do offer an integrity check, but it's not any more capable than hash pinning to a commit.
Fundamentally, if you offer a way to extend your product with externally-provided components, and you can't control the external publishers, then you've left the door open to 'these issues'.
This boils down to a security via obscurity argument. Is obscurity a useful tool? Often, yes. Should you depend on it? Definitely not. Is it annoying to lose? Yes.
The word is attached to the intended outcome, not the specific actions taken to achieve it.