He / They

  • 0 Posts
  • 53 Comments
Joined 3 years ago
cake
Cake day: June 16th, 2023

help-circle
  • I don’t think the primary counterargument is tech progression, I think the primary counterargument is that decoherence as defined here, and tech debt in general, are usually a function of humans balancing work time vs deliverable demand (for coding), and making tradeoffs like those adhoc patches vs rebuilds-to-maintain-coherence… but that is not intrinsic to coding, and is much less relevant to an agent swarm who could feasibly decide that a full rebuild using the lessons gleaned about design, but without the actual code debt, is warranted and possible within a short time window.

    If a cyclical process of n iterative updates > rebuild back to coherence > n iterative updates > rebuild back to coherence etc is used, you could mitigate the exponential loss of coherence, provided you set some kind of baseline for what rebuilds produce.



  • You’ve grouped together a couple different classes of software, with different purposes.

    “Bossware”: this is the BS one, that is used for monitoring employees. Remote screenshots, activity times, application use clocks, etc. No one should ever put up with having this.

    MDM (Mobile device management): This is IT software for managing device settings across a fleet (used to mostly mean smartphones, but now it actually means laptops), like enabling disk encryption, enabling the firewall, installing software and security updates, etc. It is also what you use for e.g. remotely wiping devices (e.g. when they’re stolen). It doesn’t usually monitor user activity.

    EDR (endpoint detection and response): this is security software for detecting malicious activity, meaning malware or adversarial actors (I.e. hackers). It often also enforces security settings like USB disablement and software allow/blocklists. This is a 90% automated, and a device that’s not doing or having done to it anything malicious is just a green checkmark.

    I run our security team, and I tell people up front that I’m not interested in what employees are doing as long as it’s not destructive or dangerous. I don’t and wouldn’t deploy bossware. I ain’t a cop, and I won’t roleplay one for my employer.





  • You’re looking for the populace as a whole to have some kind of sit-down, coordinated evaluation of what has maximal climate impact, but that’s not how protest movements work.

    Small groups can be tactical like that. Large protest movements have to seize on whatever momentum happens, when it happens.

    If people were out there protesting golf courses, I’d be there too, and I’d be encouraging it, but I’m not going to waste my breath as someone with zero meaningful platform trying to foment a mass protest movement out of thin air.

    And there’s something more important to this movement than just directly addressing the environmental impact of datacenters, which is the anti-large-corporation sentiment it’s feeding (both from, and into). That is very important for climate action. And I’m not sure if you’ve been going to any (climate) protests, but there are definitely signs at all of them protesting oil and gas companies.








  • Sadly, they exist irregardless of our little projects. Financially supporting them is one thing, and if your own ethics prevent you from using a weapon of the enemy, as it were, that’s fine, but abstention is not actually doing anything to oppose them.

    The water consumption of any LLM compute time I’ve used is almost assuredly less than a single bath, and I’ve certainly skipped more baths in my life than I probably should have. :P

    And more importantly, an hour of Netflix uses SIGNIFICANTLY more water than an hour of text LLM generation, so most people are not actually having the impacts on water consumption they likely think they are.



  • As someone who works in security, you should be extremely skeptical of their stated reasons, or even the validity of the data.

    There were a LOT of divorces following that leak, citing the hack as proof of infidelity, but the reality is that the leakers could have added people to the data explicitly to facilitate uneven divorce settlements (e.g. adding a woman to the site in order to give the husband a means to demand no split of assets).

    As much as it would be great to imagine hacktivist crusaders going after cheaters, there was a lot of money moved on the back of that leak, and in fact one of the problems with Ashley Madison was that prior to the hack it was used to essentially extort non-users, because anyone could create a profile with any email, but if someone created a profile of you, you had to both verify yourself with your ID (which they saved), and pay them money to delete it (which the leak revealed they didn’t actually do anyways).