

What took them so long?


What took them so long?


Please do spam this feed, actually.


Known to the State of California.


If you believe this article, commercial airlines are much much safer than passenger rail. There was another article that I don’t feel like citing that suggested that, in the US, trains didn’t even have a carbon advantage.
There’s something I call a “pill stick”, into which you put it in the barrel, jam it into the cats mouth while holding their jaw and then push the trigger. Requires a little finesse but easier than other methods.


Progressives work against progressive agendas by naming pro-safety policies like “don’t have police respond to mental health patients” as the Fox-news like “defund the police”.


Harris overtook Biden’s polling numbers quite quickly. Also, I find that Biden’s pardoning of the “kids4cash” judge demonstrates some extreme incompetence and tone deafness".


It’s making reference to logistic curves and how rabbit populations, which can grow exponentially, will oscillate between a low and high population size.
In short, it explains why some years there are a shit ton of rabbits, and other years, very few.


Some species of American false wolf spider


Electrical grounding rod

I’m seeing it as “This season’s updated vaccine” or “2023/2024”


FunFact™: world is derived from “wer” meaning man (like the “were” in werewolf) and “old” in the same sense as “age”.
Therefor it means “Age of Man”, which means that there weren’t ever any dinosaurs in the world.


What is the hypothesized mechanism?
This is why I come to Lemmy! :)


I would have probably bought and imported this already if it weren’t for the lack of headphone jack. :(


Not sure what you mean by OS-level
By OS-level, I mean Linux terminated the process because the process tried to do an instruction it wasn’t allowed to do, specifically, trying to access a memory location it wasn’t allowed to. That leads to a segmentation fault, on Linux.
It’s pretty much a DoS at this point.
Calling it a DoS is missing a lot of nuance because you’re blaming Google’s script, not Firefox. Having 20000 variables in a single frame is something a javascript program is allowed to do; it’s a well-formed program that doesn’t violate any rules of Javascript, so the fault is not in google’s script, but in Firefox’s JS interpreter. That doesn’t mean that Google’s script is good quality, but it’s still valid.
Finally, what makes this particularly bad? Any “undefined behavior” can be exploited as security holes [ § “Undefined Behavior and Security Don’t Mix Well”].
Now, it is possible to get a segmentation fault without having gone through a undefined behavior: by allocating memory, and then asking linux to make that memory inaccessible.
It’s also possible to have undefined behavior and not get a segmentation fault: by chance you go past the end of a memory allocation into another valid allocation. This would be very bad because then your program definitely has a security hole.
So, if we decide that “google’s JS is so bad that we shouldn’t run it”, the script should stop running because Firefox’s JS interpreter stops running it. Firefox should pop up a window saying “the Javascript on this page was cancelled because Google sucks”. I think this is incorrect, because the script is valid, but it’s not bad because at least there’s no exploitable security hole.
Or, you could have Firefox force itself to exit without triggered undefined behavior. That would actually would be a DoS, but at least you can’t steal encryption keys or whatever off the system.


Any os-level crash in a js interpreter is by definition a bug in the js interpreter and not the javascript.

Sputnikglobe.com is headquartered in Moscow according to their about page.
That particular use of grammar is normal in US English.