• 0 Posts
  • 36 Comments
Joined 1 year ago
cake
Cake day: August 18th, 2023

help-circle




  • efstajas@lemmy.worldtoProgrammer Humor@programming.devCoomitter be like
    link
    fedilink
    arrow-up
    12
    arrow-down
    1
    ·
    edit-2
    5 months ago

    Honestly, I’ve worked with a few teams that use conventional commits, some even enforcing it through CI, and I don’t think I’ve ever thought “damn, I’m glad we’re doing this”. Granted, all the teams I’ve been on were working on user facing products with rolling release where main always = prod, and there was zero need for auto-generating changelogs, or analyzing the git history in any way. In my experience, trying to roughly follow 1 feature / change per PR and then just squash-merging PRs to main is really just … totally fine, if that’s what you’re doing.

    I guess what I’m trying to say is that while conv commits are neat and all, the overhead really isn’t really always worth it. If you’re developing an SDK or OSS package and you need changelogs, sure. Other than that, really, what’s the point?



  • How do you know this? Of course there are lots of reasons for why they’d want to enforce minimum browser versions. But security might very well be one of them. Especially if you’re a bank you probably feel bad about sending session tokens to a browser that potentially has known security vulnerabilities.

    And sure, the user agent isn’t a sure way to tell whether a browser is outdated, but in 95% of cases it’s good enough, and people that know enough to understand the block shouldn’t apply to them can bypass it easily anyway.


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

    There are a lot of valid reasons, other than security, for why you wouldn’t want that though. You don’t necessarily want to allow any client’s activity to be traceable on an individual level, nor do you want to allow people to do things like count the number of clients at a particular location. Information like that is just unnecessary to expose, even if hiding it doesn’t make anything more secure per se.





  • efstajas@lemmy.worldtoLinux@lemmy.ml“Systemd is the future”
    link
    fedilink
    arrow-up
    24
    arrow-down
    2
    ·
    edit-2
    5 months ago

    Oof, that quote is the exact brand of nerd bullshit that makes my blood boil. “Sure, it may be horribly designed, complicated, hard to understand, unnecessarily dangerous and / or extremely misleading, but you have nOT rEAd ThE dOCUmeNtATiON, therefore it’s your fault and I’m immune to your criticism”. Except this instance is even worse than that, because the documentation for that command sounds just as innocent as the command itself. But I guess obviously something called “tmpfiles” is responsible for your home folder, how couldn’t you know that?








  • Please explain how Google would get my location if I don’t run a phone with Google location services and / or don’t allow Google services and apps to access my location. Sure, they may know where you are roughly based on your IP, but that’s just within a very broad region, and can easily be obfuscated by a VPN. Google siphons a shitton of information from everywhere they can, but it’s not like they’ve secretly implanted everyone with a tracking chip either… And neither can they get around any device’s OS-level location permission system.