• 0 Posts
  • 12 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle


  • In my mind, introducing Rust would only make sense if:

    1. There was a serious lack of current kernel developers (which I don’t think there is)
    2. New hardware and tech was evolving at a rate that the Linux Kernel could not keep up (again, I don’t think this is am issue)
    3. The end goal is to migrate the entire Kernel to Rust.

    Regarding point 3, having both C and Rust really only makes sense as a transition phase (measured in years) - as it would require kernel developers to be savvy in both C and Rust, or would force developers to stay within whatever domains were implemented in C or Rust.



  • LedgeDrop@lemm.eetoAsklemmy@lemmy.mlPassword Managers
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    10 days ago

    I’d used KeepassXC + Nextcloud to sync for ~4 years.

    Then I switched to Bitwarden client + self-hosted Bitwarden Server/Vaultwarden for ~2 years and I haven’t looked back.

    The problem you’ll face with KeepassXC + any syncing mechanism is that conflicts will happen. Meaning, you’ll make a change on your cellphone, your internet has a hiccup or stops working. Then you make a different change on you desktop. When everything is synced, you’ll be left with a KeePass conflict file that you need to fix. This might be fine if you immediately notice it, but if you stumble upon a conflict file from a month ago - good luck merging the differences.

    Bitwarden client + Vaultwarden has improved my password experience radically. I have phones, laptops, browsers, etc all talking to Vaultwarden. Any conflicts are handled automagically by the clients. Everything “just works” in offline mode (meaning I can add/update credentials while offline and it’ll update the server whenever it can - without needing to do any mental gymnastics).

    I can share passwords with friends and family without needing to share everything. Plus, as my instance is self-hosted, my family can get “emergency access” (would be a “premium feature”) to my passwords if something unfortunate happens to me. Plus, requesting emergency access is pretty easy to do, for non-tech people.

    edit: a word


  • Whatever they’ve been doing the last decade hasn’t been right.

    That depends on which side of the wealth gap you’re on, right?

    The old guard has to die off or step aside first.

    I don’t think “dieing off” or “stepping aside” is going to be the catalyst for change.

    What will happen is that the old guards will groom the next generation in the playbook’s they’ve been (successfully) using and refining for the last decade. Those groomed players will then be their successors.

    The only way we’ll get the “change and improvement” is if we (as a society) say “this is enough, you’ve gone too far”. However, given the levels of apathy and the recent election outcome, I’d say the American People will need to suffer more, before they’re shaken out of their apathetic stupor.


  • It’s more than needing a reminder: Let’s Encrypt Certs are valid for a maximum of 90 days before they need to be reissued. Doing this 4 times (or more) a year, for years on end will be tedious and error prone.

    Most tools that request and install Let’s Encrypt Certs automatically do this without the need for human interaction (30 days prior to the expiration) . Actually, they work so well you don’t notice the “behind the scenes work” that’s happening.

    The problem is when this renewal process “stop working”. I’d been using Let’s Encrypt for years w/o problems, but eventually the client I was using wasn’t updating and it was using a deprecated Let’s Encrypt API. Ultimately, the cert stopped updating, but I got the email reminder from Let’s Encrypt and I was able to fix it w/o a disruption.

    Now, this was just a server for personal use. So if the SSL cert expired, it would not be the end of the world. Plus, I would have gotten a bunch of SSL errors the next time my client was trying to sync data, and I probably would have dropped everything to fix it. But the email reminder was a convenient feature, which allowed me to fix it whenever I had time.

    That said, if Let’s Encrypt wants to save some money for their free service, I’m certainly not going to complain (although I will miss it).


  • Fantastic! Thank you for sharing this.

    I have it installed, I’m curious how effective it will be.

    Lately, I’ve been reporting AI generated cruft as “spam” to duckduckgo. In fact, it’s not really spam - as there are some nuggets of useful information, but so sparse, I’d rather of skipped the article/website entirely. I hope these kind of Blocklists will evolve to include this kind of quasi-spam.



  • Lemm.ee: It’s the Switzerland of the fediverse. ;)

    The Operations Team are a stand-up group. Their focus is on delivering stability.

    You’ll basically get access to all content (and all “features”, like up-vote and down-vote - I’m looking at you beehaw).

    What I’ve heard from other people is that they want automagic curated content… so you won’t find that a lemm.ee, but for me - I’m happy to find the content that’s meaningful to me.