Except that the HTML spec explicitly states just before that regex that what it checks is not whether it's a valid e-mail address, and that it intentionally rejects valid e-mail address.
<local portion>@<destination portion> is how I seem to remember "email address validation".
The '@' is the only reserved visible character.
The local portion is ONLY to be interpreted by the destination host.
Destination portion does not have to follow any pattern except to specify something (such as a path or resource name) findable by the mail server.
Of course, if you specify a destination only understood by your local email server as a destination in your LAN/WAN/whatever when talking to somebody/something outside that, they won't be able to reach you.
Addresses tend to look a lot more orderly than they used to, but I think this would be a "valid" address (within a given system):
The US First Amendment does not say anything about libel or calls to violence. I am not aware of other amendments doing so either. What is the rationale for allowing these limitations on speech that cannot equally be applied to hate speech?
The right to free speech does not protect your right to commit crimes or civilly damage someone merely by speaking as part of the crime or tort. So if you and your friends plan to rob a bank together, the planning, or conspiracy, can be a separate charge in addition to the robbery. Libel is a tort because you lie (important) to damage someone's reputation and this could cost them money.
Hate speech is mostly just hurting peoples feelings. It neither helps cause physical damage nor costs the victims money. You cannot, in the US, ban the expression of a thought just because you think somewhere down the line it could result in damage to someone.
So three guys conspire to burn down a church- that could damage someone. A guy writing on the internet that churches are full of pedos and someone who reads that decides to burn down a church? The guy who burns the church only committed a crime.
There could be grey areas between those two situations and that is for law to decide. But the crime cannot be essentially the thoughts and ideas expressed
> The right to free speech does not protect your right to commit crimes or [...]
If hate speech were to be made a crime, your exact same argument "the right to free speech does not protect your right to commit crimes" could and would be used as an argument why the First Amendment supposedly does not apply.
> It neither helps cause physical damage nor costs the victims money. You cannot, in the US, ban the expression of a thought just because you think somewhere down the line it could result in damage to someone.
That is exactly what your example of planning to rob a bank is. The planning to rob a bank does not cause any damage. The planning to rob a bank does not cause any victims any money. Actually executing that plan does that, but the planning does not guarantee that the execution will happen. Yet if I were to say "You cannot, in the US, ban it just because you think somewhere down the line it could result in damage to someone" you would rightly dismiss it as nonsense.
> Hate speech is mostly just hurting peoples feelings.
We may disagree on the "mostly", but even you are acknowledging that it is not limited to that, so let's focus on cases that can't be considered that.
> Libel is a tort because you lie (important) to damage someone's reputation and this could cost them money.
Okay, now consider for instance well-known conspiracy theories that the world is controlled by (insert group here). They are lies, they damage the reputation of many if not most members of the group, and this could cost members of the group money. They are not libellous if not said about specific people, they are generally considered hate speech if based on any of a specific set of protected characteristics, but despite the exact same reasoning applying to both, libel would not be considered protected speech, and, as far as I understand, this particular form of hate speech would be.
It is also easy to think up scenarios where supposedly constitutionally protected hate speech "helps" cause physical damage: if without the hate speech, a group of people would be left alone, but with the hate speech, other people become convinced that it is morally defensible or even necessary to commit crimes against those people.
I can see no distinction in the constitution to justify this. I understand that this is how US courts interpret the constitution, but everything I can see tells me this is an arbitrary distinction drawn up by US courts with no actual basis in the constitution.
True. And that still doesn't mean the behaviour is undefined, that just means the construct is not useful except on two's complement implementations. Which, even before C23, was all of them: the C23 change to require two's complement wasn't really meant to invalidate existing implementations, it was meant to reflect the reality that there were no other implementations worth considering. See https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2218.htm, the only non-two's-complement implementation still in use that was found was very much a legacy-only thing for backwards compatibility where it was not expected that its users would want a modern C compiler anyway.
> You really just want the calculation to be settled with some well-behaved result like wrapping, or else to raise an exception.
Perhaps you do, but others don't. This compiler behaviour isn't done just for the hell of it, it's done because it's an unavoidable consequence of optimisations that some people rely on that improve performance of valid code. At the same time, other people have almost-valid/invalid code (call it what you will) that behaves as intended when less-optimised, but breaks under these more aggressive optimisations. Whether to prioritise the handling of valid or invalid code is something people will never agree on; everybody will say to prioritise the handling of the type of code that they themselves wrote. I think compilers made the right call in having this as an option so that people can choose what works best for them.
The assumption "construct X must have undefined behavior, so we are going to optimize following construct Y accordingly" is entirely avoidable. I believe that a professional engineer would avoid such a thing. That we have such a situation just reflects badly on our field.
> I thought trans was about changing gender, not changing sex.
Mostly true, but it's confusing. Historically, sex and gender have been used interchangeably. That is slowly changing. There are a lot of places that refer to "sex" where "biological sex", as you put it, is not what is meant. See e.g. how trans people can still get their "sex" updated on documents that refer to sex and not gender, and how many places described as single-sex are actually closer to single-gender.
> Historically, sex and gender have been used interchangeably.
This really isn't true. "Sex" was the only word anyone used for most of history; the idea that there's a distinction between "sex" and "gender" was invented by the sexologist John Money in 1955.
The Wikipedia article you link to also claims that the 1882 Oxford Etymological Dictionary of the English Language said that one meaning of gender was sex. Other dictionaries from well before 1955 also support this. In fact, the 1828 Webster's dictionary, available online, specifically says the meaning of sex came first, the meaning in grammar followed from that. The separation of sex and gender is recent, you're right about that and that's what I was saying too, but you're wrong that sex was the only term used before that.
I'm glad your experience was better than mine. I had to get a lawyer involved after the Dutch support told me I would be refunded if I returned an item, and then after I sent it back, denied the refund.
Well, my story didn’t end well, but at least they were nice and courteous. Maybe I just got lucky there but my experience with US support was random phone hang ups, infinite queues to ‘I will just fetch this info, moment sir’, people being short, blaming me, barking insults etc.
I guess you found out as well, like me, the US has the last say in any matter and they don’t really listen to their overseas colleagues if their flagging algo/AI says ‘nope’.
Did the lawyer work? If it did, I am happy that at least it seems possible to go against them. I will never touch them again though.
The script is for static analysis, so it only needs to run once against each code change, and in theory it shouldn't need to be portable code, unless the code under test is the static analysis code itself.
In other words, they control where this script runs and there is no need to run it on more than one platform, so it's okay for it to be non-portable.
That's fine if the script only runs on shells that behave the same way, but the script runs under bats, which runs on bash and appears to not change its xpg_echo shell option. This shell option controls echo's behaviour on bash and has a compile-time-configurable default; even scripts that are only meant to run on bash cannot assume either behaviour for echo, as different vendors use different defaults for the option.
