Aussie living in the San Francisco Bay Area.
Coding since 1998.
.NET Foundation member. C# fan
https://d.sb/
Mastodon: @dan@d.sb

  • 2 Posts
  • 204 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle


  • the fediverse seems to be far more resilient against bots, since we can defederate from an instance that gets taken over,

    It’s very easy to spin up a new instance though, so I’m surprised there’s not a lot of spam. AFAIK most servers still federate with any new servers by default as soon as a user on the new server subscribes to a person/community on an existing server. That’s important to ensure equal treatment and that new servers are not disadvantaged, but it can also have issues.








  • For DNS challenges, I personally prefer using acme-dns. It’s a separate DNS server that only serves ACME DNS challenges. I felt a bit uneasy using an access token for my actual DNS host since it grants full read/write access to every record. acme-dns reduces the attack surface.

    Let’s Encrypt follows CNAMEs and supports IPv6-only DNS servers, so you could just run acme-dns on a spare IPv6 address (assuming your internet provider has a static IPv6 range, or you have a VPS with IPv6).









  • mostly a wrapper around their proprietary library

    I’m not familiar with exactly what Bitwarden are doing, but Nvidia are doing something similar to what you described with their Linux GPU drivers. They launched new open-source drivers (not nouveau) for Turing (GTX 16 and RTX 20 series) and newer GPUs. What they’re actually doing is moving more and more functionality out of the drivers into the closed-source firmware, reducing the amount of code they need to open source. Maybe that’s okay? I’m not sure how I feel about it.