Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)EC
Posts
0
Comments
80
Joined
2 yr. ago

  • From a UX perspective I disagree. 1password wins at UX hands down but Bitwarden is a very close second and IMO has better privacy guarantees.

    Security is useless if it's too difficult. Despite liking Bitwarden I am a 1Password subscriber and happy with my choice.

  • What excuses are you referring to?

    Are you also arguing that if a problem isn't in your immediate periphery then it doesn't exist? We are all human beings, living on the same planet.

    There's nothing wrong with feeling a modicum of empathy for those less fortunate by circumstance of geography or socioeconomic influence.

  • Sorry, all you get is images of a maxi pad to indicate enormous damage for what was likely a graze.

    An attempt on a former president's life is a big deal, whether I think he's a human dumpster fire or not.

    However, the way he played this up was and is ridiculous. He didn't need to prove anything. Someone shot at him and that's not in doubt. Instead he chose to milk it and I personally find that ludicrous given the circumstances.

  • I agree with most of these but there's another missing benefit. A lot of the time my colleagues will be iterating on a PR so commits of "fuck, that didn't work, maybe this" are common.

    I like meaningful commit messages. IMO "fixed the thing" is never good enough. I want to know your intent when I'm doing a blame in 18 months time. However, I don't expect anyone's in progress work to be good before it hits main. You don't want those comments in the final merge, but a squash or rebase is an easy way to rectify that.

  • Honestly, these days I have no idea. When I said "wouldn't recommend" that wasn't an assertion to avoid; just a lack of opinion. Most of my recent experience is with Cloud vendors wherein the problem domain is quite different.

    I've had experience with most of the big vendors and they've all had quirks etc. that you just have to deal with. Fundamentally it'll come down to a combination of price, support requirements, and internal competence with the kit. (Don't undermine the last item; it's far better if you can fix problems yourself.)

    Personally I'd actually argue that most corporates could get by with a GNU/Linux VM (or two) for most of their routing and firewalling and it would absolutely be good enough; functionally you can do the same and more. That's not to say dedicated machines for the task aren't valuable but I'd say it's the exception rather than rule that you need ASICs and the like.

  • I might be misunderstanding. It's definitely possible to have as many IPv4 aliases on an interface as you want with whatever routing preferences you want. Can you clarify?

    I agree with your stance on deployment.

  • Given how large the address space is, it's super easy to segregate out your networks to the nth degree and apply proper firewall rules.

    There's no reason your clients can't have public, world routeable IPs as well as security.

    Security via obfuscation isn't security. It's a crutch.