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?

Doing that would tell you nothing about whether the browser might have un-patched, known vulnerabilities elsewhere.

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.

simply reading the browser agent isnt really security

It’s not for their security, but for that of genuinely clueless people that are just running an actually outdated browser that might have known and exploitable security flaws.

Lol that’s ridiculous. There’s nothing about ipv6 that’d make it any slower

There’s a massive difference between what “usage data” refers to in this context and the kind of data stored and analyzed by Recall locally.

Maybe I’m out of the loop, but afaik they always said that none of the data would ever leave the device.

Tbf that analyzing was happening on-device… But yeah

It’s not the same and I wish people would stop pretending that it is. Does it do what most people need it to do though? Yeah, probably.

SteamOS has HDR support indeed, and it works really well with pretty much all HDR-enabled Windows games in Proton I’ve tried.

Assign a DNS name

I see this point a lot and I don’t get it at all. You can do something awesome, free and open-source but use tools that aren’t, especially when we’re talking about community building. Sure, you can do your outreach exclusively on Mastodon or Farcaster, but the most eyes just happen to be on closed platforms, so it’d just be self-sabotage. Doing the only thing that makes sense doesn’t make you a hypocrite.

Pretty funny how it says “Unauthorized access” right below screenshots of features clearly being enabled.

As opposed to “sacrifice child” which sounds … Good?

Right, because non-technical people would be expected to understand what an “out of memory” error means

macOS out of the box fucking sucks for monitor scaling with third party monitors. It’s honestly laughable for a modern OS. You can install some third party software that fixes it completely, but it really shouldn’t be necessary. I use an (admittedly pretty strange) LG DualUp monitor as a secondary, and out of the box macOS can only make everything either extremely tiny, extremely large, or blurry.

Other than that, I’ve had no problems at all, and the window scaling between different DPI monitors is a lot smoother than it was with Windows previously.

Google literally has an official list of IP ranges for their crawlers, complete with an API that returns the current IP ranges that you can use to automate a check. Hardly a moving target, and even if it is, it doesn’t matter if you know exactly where the target is at all times.