Water is such a good radiation insulator that you need to be a few meters from the nuclear waste to be able to detect any radiation, the issue usually is the effect to wild life, that absorbs radioactive heavy metals, but so deep in the ocean, it’s not much of an issue.
So they looked at a known nuclear waste disposal location and they are surprised they found leaking nuclear waste.
At least nowadays the nuclear waste is stored in nearly indestructible stainless steel and concrete canisters and not some unsuitable steel barrels, thrown in the ocean.
One thing to note, CORS only makes sense if your API uses cookies for authentication, most APIs use custom headers, the Authentication header, or even url tokens, they don’t rely on cookies, so most of the time, APIs don’t care about CORS. People keep blindly repeating that accepting all origins “*”, is bad for security, but the situations where this is relevant are really uncommon.
Thats an issue with the time library, not with timestamps. Actually timestamps are always in UTC, you need to do the conversion to your local time when displaying the value. There should be no possible off-by-one errors, unless you are doing something really wrong.
My hypothesis is that those scrappers run on botnets hosted on infected servers, so they want to get the info as fast as possible, since you don’t know how long it will last before they are detected and removed.
Another option is that so many servers are scrapping the same web that one server may send only a request every a few seconds, but the whole fleet could be sending thousands of requests per second, some big websites can handle the load, but most small to medium size sites get overwhelmed.