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

help-circle








  • I don’t think it would last long as a clean implementation.

    The problem with having a completely open algorithm for discovery, you give spammers an instruction manual for how to consistently get to the top of the rankings.

    Eventually these systems would always get abused and become completely filled with useless nonsense.

    An alternative is to have the discovery completely exist on the client side, but I’m not sure how that would even work given the way activitypub works.

    Personally I think any social media recommendation/discovery system is a dark pattern.


  • There’s a major section of mastodon users who like mastodon because it doesn’t have any recommendation algorithms. Both from the side of “I don’t want to be told what to click on” and the “I don’t want an algorithm surfacing my posts in a way I’m not in complete control of”

    This might curse it to forever be the platform with the smaller number of users, but the nice thing about activitypub is that there may be other services/clients that will be willing to take up that mantle for those that want it.







  • Active GuixSD user.

    Our application catalog is much smaller than many other distros simply because we don’t have the userbase large enough to surface the volunteers necessary to support it. So you will have to learn to write your own packages eventually

    That said, if you know your way around functional languages (in this case, scheme), it’s probably the easiest time I’ve ever had writing a package. Everything that goes into the script is known at the time the script is written, so weird extrinsic problems don’t really occur after you’ve written the package.

    Some stuff that you and the guix maintainers may not have the time to support will also get updated more slowly.

    Luckily flatpak exists, and is a godsend for the new wave of read-only (functional/ostree-based) OSs.

    Biggest appeal for me was having all my configuration in one place (and documented) so if I forget I did something in 6 months, it’s always staring at me in my home or system config file. You can accomplish the same thing by being diligent with say, script files, but it’s drop-dead easy to just maintain a system and home descriptor file and keep editing that.



  • 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.