Oh See Paren Left Brace Whatmark
For loads of alternatives, see the Jargon File
Oh See Paren Left Brace Whatmark
For loads of alternatives, see the Jargon File
Yes, it’s legal in much of the US. Many states require a permit for concealed carry, but not for open carry. WalMart has signs at the front of the store “requesting” people not to open carry, but apparently not prohibiting it.
Pornography is
close tofull sex work
FTFY
That is not accurate.
Nah. This has happened with every major corporate antivirus product. Multiple times. And the top IT people advising on purchasing decisions know this.
No - it was the language that I said was transphobic, not the author. Given that there were two different word choices (“transsexual” and “perceived gender”) that reinforced each other, it seems more likely than not that they reflected the mindset of the author, but not having looked further for their other writings I was not sure. That’s why I said " transphobic language" and not “transphobic author”.
More, but there’s an even simpler solution. In the context, the author is distinguishing between “sex assigned at birth” and “perceived gender.” The equivocating word " perceived" could simply be dropped with no loss of clarity.
A well argued point. Could have done without the random transphobic comments about “transsexuals” and “perceived gender”.
And that assumes no second hand
Exactly.
Good point. That was in the “static IP” category and not counted in the 200+ million install “malicious code” category, though. It could be a warning sign of false positives, but the example was such a small snippet it could also be opening after a VPN is established. That example was supposedly part of code that opens a connection for shell access from the other end, but without more details it’s not really possible to say.
The researchers are releasing the scanning tool they created for people to be able to run against their own installs.
Except their summary is wrong. The researchers went on to search other extensions for known malicious code, and found it in thousands of extensions with tens of millions of total installs.
Having known multiple trans people and heard them talk about the arguments for and against early disclosure: Fear.
They may not be public about their status, and fear exposure to family or coworkers seeing their public profile.
They may fear harassment from transphobes. This could range from DM accusations of pedophilia to religious screeds to doxxing to death threats.
They may be trying to avoid “chasers.” There are some people for whom a trans body (particularly a transfem body) is a fetish, who don’t actually care about the person inside. Plenty of transpeople don’t appreciate that kind of attention.
Fear of rejection. They may believe that nobody will respond if they’re open about not being cis.
Also two less fear-related (and less common) possibilities:
Ideology. To some people, specifying “transman” or “transwoman” reinforces a social distinction they find invalidating or don’t accept. How many profiles have you seen that specify themselves as “cisman” or “ciswoman”? For these people, it’s a way of rejecting cisgender normativity.
Maybe they just aren’t ready to talk about their genitals yet, or have their first conversation be about their surgical plans or history. Not only can get really repetitive having that be the first conversation with every single match, it means they don’t get any of the information they’re looking for about a potential partner until much later in the process and have to invest a lot of their own time up front. Just like you want the salient information you care about early on, so do they.
Sweat. When it’s hot and humid in particular, a little bit of lift prevents uncomfortable sweat buildup where the scrotum meets the legs.
But she has no way to know that, and a lifetime of evidence to suggest that your attitude isn’t the universal male perspective. Since she doesn’t know you personally, the risk outweighs whatever benefit she gets from the high five.
Absolutely. My partner and I have traded those roles more than once.
Not true.
He can’t prevent anyone that received the code under the GPL from using (and distributing it) under the old license. He also can’t relicense code that he received under the GPL only under the new license.
If he receives a new license from the other contributors to distribute under a more restrictive license, he can do that because he has a dual license to the code and is not relying on the GPL for his right to distribute.