• 0 Posts
  • 668 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle

  • If only people actually read the ORIGINAL Rolling Stone article instead of just regurgitated secondary headlines for clicks.

    Because despite their own headline being similar, the actual article contents indicates that the cause is mostly from agriculture and drought. Measurements from the water leaving the datacenter are even lower than the measurements from some local wells a decade ago.

    Technically the headline is right, it’s not a lie, there is a link between the datacenter and adverse health effects… but the context surrounding it is dramatically different than what they want you to assume.


  • Cool, agreed. They don’t pay nearly their fair share.

    Yet here they’re being blamed for something that seems isn’t their fault. They’re not actively working to fix the issue, but considering they’re a tiny fraction (looks like only ~0.1% impact in the overall area according to some articles) of the cause, the articles attacking them seen a bit ridiculous. Amazon needs to pay for the things they do. Blaming them for shit that isn’t their fault just means losing credibility.

    The Amazon datacenter is concentrating the nitrates more in the water that they use, yes, that is the nature of how the water usage works and evaporates. But the nitrate concentration was already above Oregon state limits in 1992, and some wells in 2015 had ~20% higher readings than the water coming out of the datacenter now a decade after that. That certainly doesn’t seem to correspond to the datacenter being the major contributor. And the original article says as much, saying it’s primarily from agriculture and drought.


  • I just want to point out… From the original Rolling Stone article:

    In 1992, DEQ measured an average nitrate concentration of 9.2 ppm across a cluster of wells pulling from the basin. By 2015, that average had risen 46 percent, to 15.3 ppm. For some wells, DEQ found nitrate levels nearly** as high as 73 ppm**, more than 10 times the state limit of 7 ppm.

    When that tainted water moves through the data centers to absorb heat from the server systems, some of the water is evaporated, but the nitrates remain, increasing the concentration. That means that when the polluted water has moved through the data centers and back into the wastewater system, it’s even more contaminated, sometimes averaging as high as 56 ppm, eight times Oregon’s safety limit.

    So the average back in 1992 was already above Oregon’s safety limit, but barely below the national limit. The water coming out of the datacenter now is lower than some of the base levels detected in some wells back in 2015.

    Not saying Amazon isn’t a part of it. But it certainly seems like they’re not actually nearly as big a part as the article wants to make you believe. The Rolling Stone article is 90% about agriculture and drought adding to the increase in nitrate concentration, but that doesn’t get clicks.



  • As the comments at the provided link point out… this is disingenuous… at best.

    The original Rolling Stone article this is based on… says the vast majority of the increase in nitrate levels is from expanding agriculture in the area.

    The massive inputs of fertilizer to grow crops and feed for the animals came at a price: the contamination of the Lower Umatilla Basin. In 1992, DEQ measured an average nitrate concentration of 9.2 ppm across a cluster of wells pulling from the basin. By 2015, that average had risen 46 percent, to 15.3 ppm. For some wells, DEQ found nitrate levels nearly as high as 73 ppm, more than 10 times the state limit of 7 ppm.

    And…

    As the underground aquifer became tainted with more nitrates, even the ostensibly clean water that the Port pulled from the aquifer’s deepest wells — which it used to service its large industrial customers like Amazon — became polluted. Soon, Amazon was using water to cool its data warehouses with nitrates as high as 13 ppm — above the federal and state limits.

    When that tainted water moves through the data centers to absorb heat from the server systems, some of the water is evaporated, but the nitrates remain, increasing the concentration. That means that when the polluted water has moved through the data centers and back into the wastewater system, it’s even more contaminated, sometimes averaging as high as 56 ppm, eight times Oregon’s safety limit.

    So Amazon isn’t directly adding anything, the nitrates are more concentrated over time due to basic evaporation as the water is recycled through for a while before it is replaced.

    Amazon isn’t the source of the contaminants.

    So yes, it is “tied” to the spike, because they are using already contaminated water from the area and evaporation exists. Everyone’s water use is increasing this issue unless they’re actively filtering nitrates, which no one does. Normally that would be handled at a municipal level, but these are mostly local wells where that’s not part of the system. Amazon is just a big company, and uses a lot of water so it’s footprint is larger. But a fraction of the water use overall, and definitely compared to the agriculture adding the nitrates in the first place.




  • Not sure about a specific article for planes, but some forms of solar radiation can cause random bits to flip to the opposite when it crosses through computer hardware like memory.

    These randomly occur already just by us existing in the solar system, and error correction algorithms, hardware like ECC memory, and shielding helps to prevent and correct these issues when they do happen. The intense radiation recently, the same that caused the extended auroras, caused more and stronger occurrences though.

    One flight we know was affected despite systems that help prevent issues like that, so they’re having the software reloaded on every plane that might have been affected.




  • This comment tells me you’ve never had a good job at a good company.

    Quite the opposite, I haven’t experienced these hardships myself, but I’m able to recognize that tens of millions of people experience them every day. That it’s a reality we need to deal with as a society, and call out shitty executives that act like it doesn’t exist or that it’s the poor’s fault for not working harder (while they barely work, despite their claims). Did you mean to help prove the point that it’s extremely easy for people that don’t experience hardships like the inability to pay basic bills or afford food on a daily basis to fail empathizing with the workers that do? Because you did pretty spectacularly.

    I’m talking about a majority of the everyday workforce here. Like 99% of the 2.1 million people working at Walmart stores under this executive’s leadership. Talking about the inability of corporate executives to empathize with their employees being broadcast widely without any of them realizing the hypocrisy in articles like this with their tone deaf claims.