🧵 11/11 This is a thorny situation.

I'm not anti-efficiency or economies of scale. I'm not against complicated clean energy on the Columbia if it's already in place. I'm not saying Big Data shouldn't operate.

What I am saying is that this is absurd and took way too long to start getting sorted.

🧵 10/11 These charts show the rapid rise of an already bad situation after AWS and other data centers moved in after 2008.

🧵 9/11 Here's a side-by-side of data centers and unsafe wells.

🧵 8/11 And where did almost all of that money come from?

• 𝗥𝗲𝗽𝘂𝗿𝗽𝗼𝘀𝗲𝗱 𝗳𝗿𝗼𝗺 𝗗𝗘𝗤 𝗳𝗶𝗻𝗲𝘀
• 𝗪𝗜𝗙𝗜𝗔 𝗔𝗰𝘁 𝗴𝗿𝗮𝗻𝘁𝘀 𝗳𝗿𝗼𝗺 𝘁𝗵𝗲 𝗘𝗣𝗔

So basically you, the taxpayer.

🧵 7/11 Finally, though, winter irrigation is about to stop because of new wastewater lagoons that can hold >1.5 billion gallons at a time.

And nitrogen removal is now part of the flow.

All told these processing facilities cost ~$500 million.

🧵 6/11 The nitrate levels are already absurdly high and folks get cancer or miscarry routinely.

Of course this disproportionately affects the working poor Hispanics who live in the area, mostly in mobile homes, and with wells that draw water at 1-8x the EPA nitrate limit of 10 ppm.

🧵 5/11 And it has elevated a situation from bad to worse.

Ag waste + fertilizer have been seeping into the aquifer for 40 years.

Now with tens of millions of gallons of water discharge from the data centers each year and not enough storage, nitrates are accumulating and spreading even faster.

🧵 4/11 ~15 years or so ago AWS moved in because of the

• 𝗰𝗵𝗲𝗮𝗽 𝗹𝗮𝗻𝗱
• 𝗰𝗼𝗼𝗹𝗲𝗿 𝗰𝗹𝗶𝗺𝗮𝘁𝗲
• 𝗮𝗯𝘂𝗻𝗱𝗮𝗻𝘁 𝘄𝗮𝘁𝗲𝗿
• 𝗿𝗲𝗻𝗲𝘄𝗮𝗯𝗹𝗲 𝗲𝗻𝗲𝗿𝗴𝘆
• 𝗹𝗮𝗰𝗸 𝗼𝗳 𝗻𝗲𝗶𝗴𝗵𝗯𝗼𝗿𝘀
• 𝗰𝗼𝗽𝗶𝗼𝘂𝘀 𝘁𝗮𝘅 𝗶𝗻𝗰𝗲𝗻𝘁𝗶𝘃𝗲𝘀

🧵 3/11 It's also a place where greenwashing wins--here's looking at you Tillamook--and corporations construct museums like the Sustainable Agriculture and Energy (SAGE) Center.

🧵 2/11 Anyone driving between Boise and PDX on I-84 knows the stench surrounding Boardman.

It's definitely a place you have to roll your windows up and put the recirc on because of all the methane and ammonia from CAFOs.

Get Bo to perform

Gmail signatures are pretty weird. They're HTML. Kinda?

You have to copy/paste rendered HTML and can't work with code directly.

Remote images are not respected unless you email your signature to yourself first.

And you cannot easily resize the window which is a pane. Sorry, pain. It's a pain.

Did this project die? Their linked repo 404s and it's been 6+ months since a package has been published :/

www.npmjs.com/package/mdsx...

Ah yea, I need to do this more--I say I will, but with a 10% completion rate 🥴

Very cool! Thanks for making + sharing.

Do you think you'll use LayerChart, SveltePlot, or something else?

I know it's cliche, but what about self-hosting? Could be a happy compromise where it's up + running, plus expenditure is capped.

Just make sure dbs have limits, too.

And you always learn more when self-hosting :)

If you did, and no data were present, dividing by 100 yields:

• d?.percentUnder18 → undefined
• undefined / 100 → NaN
• NaN ?? 0 → NaN

So ended up defaulting to a ternary operator instead.

In this case both the intent and error were clear: the data should be cut by 100 but the math was not being executed properly because it was on the wrong side of the operator.

The fix wasn't as easy as moving the /100 part back over to the left side though!