• 3 Posts
  • 38 Comments
Joined 3 years ago
cake
Cake day: July 18th, 2021

help-circle
  • snek_boi@lemmy.mltoOpen Source@lemmy.mlWhy is GrapheneOS against GNU?
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    1
    ·
    29 days ago

    I agree with you: the FSF can seem unwavering in their stance, even in the face of practicality. I’m really sorry for this incredibly nit-picky detail, but I think practicality is ideological too. For better or for worse, we can’t escape ideas or be free from them, so we have to choose which we value. For example, while I tend to choose software freedom over practicality, I also have, at times, chosen practicality over freedom.




  • I agree that we shouldn’t jump immediately to AI-enhancing it all. However, this survey is riddled with problems, from selection bias to external validity. Heck, even internal validity is a problem here! How does the survey account for social desirability bias, sunk cost fallacy, and anchoring bias? I’m so sorry if this sounds brutal or unfair, but I just hope to see less validity threats. I think I’d be less frustrated if the title could be something like “TechPowerUp survey shows 84% of 22,000 respondents don’t want AI-enhanced hardware”.


  • You’ve got a good point. I wonder if this an example of a trade-off between convenience and security. If you’re logging in and you get an MFA prompt, a Yubikey has to be physically searched, while Bitwarden or Proton Pass only have to be clicked. A Yubikey can only hold a limited amount of accounts, while Bitwarden or Proton Pass could hold many more. Of course, a Yubikey could be used as MFA for Bitwarden or Proton Pass, but that would create a single point of failure and reduce factor separation (which I think is your original point).

    While I posted a Bitwarden or Proton Pass recommendation of sorts, I genuinely wonder if it’s advisable to not use MFA at all if the factors will not be separated. Or, perhaps, the best security solution is the one you’ll actually use. I guess the answer is the good ol’ “What’s your security model?”




  • The article’s “valuing your time” argument is problematic in certain contexts. My brother has had so much trouble with his dual-boot (Windows and Linux). Yes, he could learn how to solve something in Linux every time a problem arises, but he also has to deliver his projects on time. Because of that, he mostly spends time on his Windows dual boot. Yeah, it sucks ethically and has its own pragmatic issues, but he has never had issues resolving dependencies or hunting down the most recent version that can actually be run in NixOS.

    I don’t doubt these will become issues that will not be as problematic in the future, but right now my brother cannot use Linux reliably for his assignments.

    Edit: My brother has tried what I use: Fedora and NixOS. He has also tried PopOS.

    In Fedora, he found some of his software didn’t exist as .deb, and struggled to make .tar files work smoothly for him.

    He tried NixOS afterward. He really liked the whole immutability thing, as well as the idea that apps would have their own dependencies.

    His dependency problem happened in PopOS. If I remember correctly, it was a code editor that required a version of something that was different to what a package he used in his software was.

    I think the order he tried was Fedora -> NixOS -> PopOS -> NixOS -> ? (Haven’t talked to him about it recently)











  • EDIT BEINGS HERE

    So I actually watched a talk by the person who coinded “enshittification”, Cory Doctorow, recently, and I have changed my perspective about Kagi. I no longer think Kagi is doomed to enshittify.

    Enshittification requires advertisers. As long as Kagi finances itself with money that does not come from advertisers, it will not enshittify.

    This does not mean that it’s not problematic that their code is closed-source.

    EDIT ENDS HERE

    I like what I hear about the user experience, but there are many problems I see with the service.

    For one, it’s based in the USA, so it is legally subject to the insane, antidemocratic, and awful state surveillance there.

    It is also a corporation, so it is subject to enshittification. Currently, it is giving users loads of stuff so that users use it, but sooner or later investors will want their money back and Kagi will enshittify.

    Finally, these two problems would be mitigated by open-sourcing and making libre their software. With that, alternatives in more sensible legislatures could open. Users could migrate to instances that are still libre and not enshittified.

    It is really unfortunate that Kagi is doing so many things well while doing some fundamental things terribly. As it stands, Kagi is doomed to enshittify.




  • I see how majority judgement could be seen as a subset of range or score voting.

    A crucial difference between range/score voting and majority judgement is that one uses numbers and the others judgements. A majority judgement ballot could list all the possible candidates or options, and for each of them, there’d be a list of possible judgements. You can say that you consider a candidate “terrible”, “bad”, “meh”, “good”, “amazing”.

    The idea is that humans tend to think in terms of judgements more readily than with numbers. A good ballot would find what words evoke useful judgements for candidates, as each group of voters has its own social language.

    For example, with my partner we have a list of movies that we vote on. We have judgements that include “I’ll leave the house if you play that sh*t”, or “Omg yes!”. It’s great to add a movie to the list and find that one of the judgements in our made up ballot matches our personal judgements so well!

    This is something I think majority judgement can do better than range/score voting: it can reflect human judgements better than with scores. In that way, it is more intuitive than range/score voting.

    One benefit of majority judgement is that leaders chosen through it would know the judgement that they came into power with. If someone is elected into a powerful role knowing that half of the voters think they’re “ideal” for the job, that’s quite different than knowing that they were elected with half the voters thinking they were “inadequate”. This means, ideally, that the legitimacy of incompetent leaders can be reduced.

    Note that the amount of possible judgements in a ballot can vary. To make things quick and easy, I’ve had silly elections with three judgements, such as “nope”, “ok”, “omg yes”. I’ve also had elections with nine judgements.

    If you want to reduce the probability of having multiple winners, more judgements are a good idea. In general, the amount of judgements should depend on what the stakes are (higher stakes should go beyond just a couple of judgements), how many options there are (few options require few judgements), and the amount of voters there are (few voters require many judgements).

    I think the reason for using the median is so that a judgement can be chosen as representative of each candidate. In the “nope”, “ok”, “omg yes” example above, if the median of the winning candidate is 3, you can tell the candidate that the score that they were chosen with was “omg yes”. If the average of the winning candidate is 2.4, you can’t really translate that as succintly, given that 2.4 is between “ok” and “omg yes”.

    I hope it’s clearer why I love this voting method!