wiredfool

There were serious thermal issues with the late 00's 24" iMacs. I had one that ate 3 hard drives, and then the display in about 6 years.

The killer is it's even dumber than that.

Nor small composites, apparently.

Take 1/4 tablet every other day, WARNING: don't drink alchohol while taking this medicine.

Daphne (The Cat) Lastname.

We've got to split a couple of pulls in quarters for the cat. One of them is super easy and works in a pill splitter, the other one doesn't break easily. The easiest way to accurately split it is with a cutting board and chef's knife.

Amazon will be able to run large models for a fee, and make money on it. It's not a trillion dollar business, it may not even be a good business, but they'll be able to do it.

My 3 month old system is running about 20% above their numbers, not clear on where the difference is. From some other modeling using pvlib, I suspect that the panels are over producing, as that’s the easiest way to make the numbers work. It’s also possible that the measurements are miscalibrated, or we’ve just had weather that’s not in line with historical averages.

This isn't a great example, because they're effectively using a chart to show a handful of data points. The key with the data/ink ratio is to densify the amount of data shown so that the ink that is used can show additional dimensions or statistics -- such as using a 2 dimensional plot, turning the axes into box plot equivalents, or other relationships.

You might not need find due to advanced globs, but it's too easy to run into expansion limits when you match hundreds or thousands of files, so you're back to find for that.

IP blocks don't work, because they're using proxy networks so that you see an ip address 1 or 2 times within 10 minutes. They have effectively infinite ip addresses. (actually, looking at my data from today, I think this relationship holds over ~3 hours, where we're seeing ip address cardinality at about 1/2 of the hits.)

  * Sometimes there's a pattern to the country. Oftentimes, not. 
  * User-agent, rotated between common, valid, current web browsers.
  * Other headers, sec-*, accept, etc, generally valid and rotating. 
  * Bots will load the site to saturation in a denial of wallet attack.

The only thing that's specific is:

  * urls have a pattern.
  * it's obviously invalid traffic. 

(non-bot traffic on my sites does not go from 0 to 200r/sec on the search interface in seconds. It does not go away that fast either)

I’d love to, but I’m a bit limited in what I can do from a reputational damage POV. They’re my sites, in that I’m responsible, but they aren’t something where I can return incorrect responses.

Seeing the exact same thing on (somewhat high profile) open data sites I run.

The crawlers get stuck in a loop requesting the dataset listing page with every. single. combination. of. facets. At essentially as fast as it can be pumped out or blocked.

Had one bot super interested in a single organization to the tune of 1000 r/min for 24+ hours. Realistic rotating user agents, realistic sec-* headers, no ip address seen more than a couple times in 10 minutes. The only commonality was the route.

I don’t think I’ve noticed gym socks smells, but I can certainly smell kerosene basically every time when outdoors at the airport, and often in the plane.

When I did it, I closed the door at nautical twilight. The key is that you need to close the door after the chickens roost but before the nocturnal predators come out.