Praising a murderer for committing a murder is not incitement and is protected speech. Under Brandenburg v. Ohio (1969), speech loses protection only if it is directed at inciting or producing imminent lawless action and is likely to produce it. A comment on a murder after the fact can’t meet this standard unless the comment is “go do another murder right now!”
Kimmel also did not praise the murderer. He implied (incorrectly as it turns out) that the killer was right-wing.
Your misstatements of the well-known facts and law in this case cast doubt on the effort you put into researching the other issues mentioned.
He did more than imply the falsehood. He implied that people had no good reason to disbelieve the falsehood, and that the right wing was seeking to deceive on this basis for political gain. In doing so, he (perhaps inadvertently) ran cover for the ideology that was actually responsible.
Right-wingers have lost their jobs in the US many times for far less, even when their comments were on social media accounts unrelated to the job. When these responses are described as unjust or disproportionate, American left-wingers have consistently and repeatedly (across a span of many years) told me the same line about how 1A only applies to government and not corporations. Which is correct, but also entirely missing the point about bias.
They were only "an embarrassment to their company" because of the aggressive doxxing and harassing actions of people who refused to tolerate entirely reasonable statements that they happened to disagree with.
For that matter, one time someone who wasn't even noted as right wing got "cancelled" for wearing clothing with a print that some feminists found objectionable. Clothing that was gifted to him by a woman.
Opposing modern feminism is perfectly compatible with retaining the franchise. Not that that has anything to do with anything. There objectively was no remotely reasonable basis to object to the shirt.
Why do you talk about free speech in one place and whine and cry about free speech of others elsewhere? Who cares? Cancellation was an exercise of free speech.
How is right wingers losing their jobs which is a private transaction between free private entities related to a government whining and trying to misuse regulation against a company?
That article doesn’t explain why acupuncture works, just gives a hint of a possible mechanism. It also doesn’t contain any evidence that acupuncture works at all (other than as a placebo).
- and + operators have the same precedence. And a similar bug is possible if the operators were the same (both -). So I’m not sure it’s right to blame this on operator precedence or mixed operators. It’s just that, ultimately, the “consume” needs to be subtracted, not added.
Non-mixed always goes strictly left to right, regardless of the operator, which I haven't seen anywhere near as much struggling with.
But yes, I personally parenthesize `a-b-c` explicitly, because it's not worth it for me to read and wonder if parenthesizing order matters later. Costs less than a second to write, saves a second or ten each time I read it - that's an excellent tradeoff imo, and is a trivial pattern to follow.
I agree with explicit parentheses but please be careful about assuming associativity! The risk when handling floating-point arithmetic in particular is that associativity breaks, and suddenly a + (b + c) does NOT equal (a + b) + c. Not only can these lead to unexpected and hard-to-trace failure patterns, but depending on the details, they also can introduce memory overflow/underflow vulnerabilities.
If you're going for bit-for-bit equivalence of float values, then even with a single operation you're relying on compiler flags, architecture, the phase of the moon... I'm hard-pressed to think of any memory safety issues though.
Yea, you're in a fairly special niche of programming if you're somewhere that truly matters, and you can't accept any valid order's output. In most general code, if that kind of precision matters, float is the wrong choice: use a bignum object and be exactly correct regardless of how you organized your code.
Which is a niche that exists, obviously. So it is absolutely true for some cases. But I would hope that any code that requires this is extremely clear about requiring it.
The codec is compiled in, enabled by default, and auto detected through file magic, so the fact that it is an obscure 1990s hobby codec does not in any way make the vulnerability less exploitable. At this point I think FFmpeg is being intentionally deceptive by constantly mentioning only the ancient obscure hobby status and not the fact that it’s on by default and autodetected. They have also rejected suggestions to turn obscure hobby codecs off by default, giving more priority to their goal of playing every media format ever than to security.
Yeah, ffmpeg's responses is really giving me a disingenuous vibe as their argument is completely misleading (and it seems to be working on a decent amount of people who don't try to read further into it). IMO it really damages their reputation in my eyes. If they handled it maturely I think I would have had a bit more respect for them.
As a user this is making me wary of running it tbh.
In this world and the alternate universe both, attackers can also use _un_published vulnerabilities because they have high incentive to do research. Keeping a bug secret does not prevent it from existing or from being exploited.
It doesn’t scale well to content that changes dynamically on the client side very well. Dynamic manipulation of the post transform XSL-FO is confusing and difficult, retransforming the whole document from source is too slow and loses state. This is a big part of why CSS won.
Fetch API is a pretty recent addition to the web platform. Back in the day, you could absolutely embed images of stylesheets from ftp: URLs. You could even use it with XMLHttpRequest (predecessor of Fetch). Even further back, gopher: was integrated with the web. URL schemes were invented for the web with the idea that http: is not the only one. These other protocols were really part of the web until they weren’t.
reply