• 0 Posts
  • 125 Comments
Joined 10 months ago
cake
Cake day: December 16th, 2023

help-circle






  • Most data centers evaporative cooling from what I understand, and according to This

    Cooling towers use water evaporation to reject heat from the data center causing losses approximately equal to the latent heat of vaporization for water, along with some additional losses for drift and blowdown. In larger data centers this on site water consumption can be significant, with data centers that have 15 MW of IT capacity consuming between 80-130 million gallons annually. n this study, on-site water consumption is estimated at 1.8 liters (0.46 gallons) per kWh of total data center site energy use for all data centers except for closet and room data centers, which are assumed to use direct expansion (air-cooled chillers).

    And seeing as hyperscale data centers usually use between 20-50 megawatts per data center, and there’s three of them in Colon, that’s like at least 240 million gallons of water a year.

    Yikes.





  • Depends on the training and the output.

    Just like if you photographed the Mona Lisa in such a way as it recreated the piece as if it wasn’t a photograph, a model sufficiently trained that can reproduce the original training data, you have copyright issues.

    Problem is that many models can do this, but it’s a mathematically improbable occurrence.

    If I make a stamp that’s made of 1 billion exact copies of different copyrighted photos and cut it infinitesimally small, and mixed it up, the problem that it can produce the original work that it was made from still becomes a copyright issue.

    You’d have to prove the opposite, in fact. That it’s mathematically impossible for your model to reproduce the copyrighted content for it not to be an issue







  • Biggest issue I see is that these LLMs tend to repeat themselves after a surprisingly short number of times (unless they’re sufficiently bloated like ChatGPT).

    If you ask any of the users of Sillytavern or RisuAI they’ll tell you that these things have a long tail of not being very creative.




  • “releasing the modified version to the public” would cover them re-closing the source and then subsequently releasing that newly closed source, so they can’t relicense it and then release the built version of the code.

    At least not easily, this is where court history would likely need to be visited because the way it’s worded the interpretability of “modified” in this context would need to be examined.