• 1 Post
  • 33 Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle
  • HakFoo@lemmy.sdf.orgtomemes@lemmy.worldFuck Tankies
    link
    fedilink
    arrow-up
    16
    ·
    3 months ago

    There are two issues with human rights.

    One is selective enforcement. There are a long list of countries with abysmal human rights records, but it’s too strategically convenient or economically essential to look the other way. Whrn was the last time they made a fuss about Jamal Khashoggi? Human rights only gets invoked when sabre-rattling is useful, not as a solid and consistent moral framework.

    The other is that it’s a “luxury product”. Can every country support a modern human-rights model, or does it require a certain level of economic and political stability? It’s hard to maintain rule of law amid active insurgency, or if you can’t even deploy the bureaucratic state. Once you’ve gotten past that threshold, will both leaders and the broader population be eager to switch from the system that got them where they are? You’ve got to convince people that being able to write an anti-government op-ed is more important than security, or the price of eggs. This is a long term soft sell: berating countries for not measuring up to Western standards isn’t going to get them to make that choice any faster.






  • A forced sale guarantees ByteDance gets a fire sale price. If there’s any way forward that allows them to sell not-under-duress, there’s a chance for far more upside.

    That works even for pure economics game theory, aside from wanting to continue in what they built on principle/commitment/interest in the project.

    Would Zuck give up Facebook for the right price? Would he give it up for a highly discounted price of a rush sale?




  • HakFoo@lemmy.sdf.orgtoMemes@lemmy.mlJerkoff
    link
    fedilink
    arrow-up
    16
    ·
    6 months ago

    I wonder if that’s a limit of storytelling. Grand social change is hard to film. Even team effort cohesion requires a lot of actors and writing to pull off.

    No matter how sound the morals and story, if it’s not entertaining, it might fail as mass media.




  • I didn’t. It just looks like the fair number of Cisco (and the occasional Dell) 10/100/sometimes Gigabit switches I’ve seen in junk shops.

    I bought a nifty blue Netgear 24-port one mostly because I’m more willing to buy junk from the Humane Society shop, but then decided it was too loud (40mm fans) and went to 2.5G (with smaller fanless switches) instead.



  • I guess the assumption is more that for me, a fresh install is often about decluttering as much as anything-- the five Wayland compositors, three music players, and six pseudo-IDEs I tried and didn’t like don’t need to follow me to the next build.

    In a conventional install, that just means “don’t check the checkbox in the installer next time”. In a Nix-style system, this is a conscious process of actively deciding to remove things from the stored configuration, no?

    I suppose the closest I’ve gotten was recently migrating my setup from a desktop to a new laptop. Mostly copying over some config from my home directory, but even then, I wanted enough different stuff-- removing tools I don’t use on the laptop, adding things like battery monitoring and Wi-Fi control-- that it involved some reconfiguration.


  • I suspect the tooling isn’t quite there yet for desktop use cases.

    If I were to try to replicate my current desktop in an immutable model, it would involve a lot of manual labour in scripting or checkpointing every time I installed or configured something, to save a few hours of labour in 2 years time when I get a new drive or do a full install.

    The case is easier for defined workload servers and dev environments that are regularly spun up fresh.


  • No, this is a general practice-- I see it a lot with third-party vendors who want you to integrate with their services. They’ll expire the documentation portal password after 90 days, but the actual user facing service still accepts the same “password123” that’s been set since 2004.

    I suspect the pattern is to protect the vendors from developer scrutiny: by the time you’ve jumped through enough hoops to read the docs and realize it’s trash, the execs have signed the contracts and the sunk costs are too high to bail out.

    Also add another 6 months to actually get the credentials for the test environment.