• 0 Posts
  • 69 Comments
Joined 6 months ago
cake
Cake day: May 7th, 2026

help-circle


  • here’s a fifteen year old stack overflow thread where someone asks where a unique system identifier can be read and someone suggests machine-id.

    Lest that be considered old and bad information, I just checked /etc/machine-id on a new install of Debian 13 and the permissions were 444, readable by owner, group and everyone else.

    So programs can read machine-id. If programs can read it they can transmit it. I hope someone capable of writing a program that can id my machine doesn’t need a proof of that.

    Further, programs reading machine-id don’t necessarily fall into the spyware category by default like you say. There are plenty of perfectly good reasons to request a machine specific identifier.

    Getting rid of the literal “papers please!” “Okay officer!” File literally makes investigation more difficult and puts a barrier up to tracking where there was none before. Presenting a unique hashed output based on the systems machine-id prevents a tracking method that is currently as easy as read file -> get identifier.

    The fact that other methods of tracking exist doesn’t make preventing this method not worthwhile and you should be ashamed for suggesting that.









  • The point of different licenses is the thing you ought to be looking at.

    The point of mit is to get the licensed thing used as widely as possible. It breaks down any barriers to use. A good example of something that should be mit licensed is an encryption algorithm. A good example of something that shouldn’t be mit licensed is anything else.

    The point of bsd3-clause is to prevent the licensed likeness from being used to imply the creator shares some view or idea. A good example of something that should be bsd3-clause licensed is the royalty free music on youtube. A good example of something that shouldn’t be bsd3-clause licensed is a creative work the author wants to have their name known for.

    The point of the various gpl licenses is to create a digital commons that all people can access. A good example of something that ought to be gpl licensed is a game engine you want people to be able to freely use and modify but never make secret changes to sell. A good example of something that shouldn’t be gpl is a game engine you want to eventually sell the code of or make secret changes and sell the code of those.

    If my language sounds biased, it is because I have a bias.




  • Another person already wrote this itt, but the cost in time and money of building something that “works” is very low. That cost increases every time you need to fix something. It’s why I’ve switched to deepseek flash instead of the bigger, better coding models. For the same price as a million tokens of Claude for example I can get a hundred million tokens on flash. It takes three times as long and needs a little prodding but it’s thirty times cheaper.

    Even if you’re not dealing with ballooning costs when it comes to upkeep, the present environment around ai programming is filled with perverse incentives that reduce the chance something is open sourced. Why preserve the old work and try to carry it into the future when you can just rewrite it? Why create standardized libraries and approaches to specific problems when it’s only gonna be used once? Why make it open when you don’t have time to deal with requests and bug reports you don’t care about? Why use gpl when you don’t intend to make it public anyway?

    Those were all arguments against gpl and open sourcing parts of the Unix codebase too, btw.

    Harnesses or agents try to address some of this by sharing improvements but that’s three layers removed from directly turning fossil fuels into cpu cycles to make the same program a thousand times slightly different for a thousand different people.

    I tend to see the ai programming defense in the same way you described yourself and the “ai is bullshit” crowd. People defending this stuff generally either aren’t looking where they’re walking or haven’t had to use it long.

    As a decently prolific user of ai programming, it’s turned computer code into disposable plastic wrappers. Even if they don’t persist and make a giant garbage raft in the ocean or calcify our pineal glands we still wasted a bunch of energy on them.



  • Probably unplug three of those fans and block off the case openings to get some sort of laminar flow.

    Switch to a more efficient power supply. Yours is platinum but it may be worth it to look into a list of low standby power units.

    Maybe take out half your ram. It probably doesn’t matter though, I’m thinking about the need for lpddr to get past the 1tb barrier on old servers.

    The b850 boards will have efficiency settings in the bios that will make the biggest difference.

    Before you change anything though I would recommend first putting a watt meter inline and measuring.

    Theres a bunch of stuff you can manually do in software but its fractions of a percent and makes your experience very nonstandard.

    The biggest thing is probably gonna be turning off the computer when you’re not using it. It’s not like you’re gonna be spinning down a bunch of hdds…


  • A datacenter on land that relies on water for cooling is using fresh water. Aside from the insane and undesirable use of fossil water or groundwater, fresh water has a much higher ratio of surface area exposed to air and volume than the ocean does.

    That ratio is important because you can only evaporate off the surface, so the same volume of water would evaporate faster in a frying pan than it would in a saucepan given the same conditions.

    Freshwater is also smaller than the ocean by many orders of magnitude. That’s important because a smaller body of water will heat up more than a larger one given the same conditions.

    Freshwater is also generally speaking moving towards the ocean somehow in a complex process called the water cycle. It might flow down a hill into the ocean, it might drip through aquifers to the ocean and it might evaporate and fall as rain either in the ocean or somewhere else where it takes some other path towards sea level.

    That last part is important because in America rivers like the ones in Colorado and California have been reduced in volume so much due to of a bunch of manmade events and earthworks that they now lose a higher portion of their volume to evaporation as opposed to flow. That’s a big deal because the Colorado for example flows south but water vapor that comes off of it is blown east. So now much more of the rivers water is going into the desert as opposed to reaching the ocean. The water cycle has been disrupted.

    Freshwater is also comparatively super rare and necessary for life on land.

    So if you were water cooling a datacenter it would be better to use the huge ocean with much lower surface area to volume ratio and much more volume than to use the rare freshwater that will get heated up much more by the same energy, evaporate faster, we already know can have its water cycle disrupted and all life on land relies on.

    Now a person might ask “what about the sea life, doesn’t it matter?” Of course sea life matters, but the way that sea life handles an increase in temperature that’s localized to one specific area is to just go away from there, like it does when undersea magma vents pop up. When the freshwater gets too hot it all evaporates away, there’s no water and the land animals die.

    A person might say: “well don’t animals die when the oceans get hot too?” And they’re right! An average increase of .5 degrees c in sea surface temperatures would lead to massive coral bleaching. But enough energy to raise the sea surface temperatures .5c is phenomenally huge. Like getting more sun huge. Because that’s what’s raising it, getting more sun. Datacenters produce so little heat energy in comparison to that level of power that it’s not a concern.