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

help-circle
  • Ah, I see how my wording was confusing. I mean planning in the sense of “How will we complete the work that we already committed to?” and “What will we do today to achieve our Sprint goal?”

    I arrived at the word planning because Scrum is sometimes described as a planning-planning-feedback-feedback cycle. You plan the Sprint, you plan daily (Daily Scrums), you get feedback on your work (Sprint Review), and you get feedback on your process (Sprint Retrospective).





  • snek_boi@lemmy.mltoOpen Source@lemmy.mlWhy is GrapheneOS against GNU?
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    1
    ·
    2 months 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?”





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