"Also in this update:
We now have a cpuidle driver, which significantly lowers idle power consumption by enabling deep CPU sleep. You should also get better battery runtime both idle and during sleep, especially on M1 Pro/Max machines.
Thanks to the cpuidle driver, s2idle now works properly, which should fix timekeeping issues causing journald to crash.
Also thanks to the cpuidle driver, CPU boost states are now enabled for single- and low-threaded workloads, noticeably increasing single-core performance.
Thermal throttling is now enabled, which should keep thermals in check on fanless (Air) models. There was never a risk of overheating (as there are hard cutoffs), but the behavior should now more closely match how macOS works, and avoid things getting too toasty on your lap.
Random touchpad instability woes should now finally be gone, thanks to bugfixes in both the M1 (SPI) and M2 (MTP) touchpad drivers.
A bugfix to the audio subsystem that fixes stability issues with the headphone jack codec.
New firmware-based battery charge control, which offers fixed a 75%/80% threshold setting. To use this, you need to update your system firmware to at least version 13.0, which you can do by simply updating your macOS partition to at least that version or newer. This new charge control method also works in sleep mode.
U-Boot now supports the Type A USB ports (and non-TB ports on the iMac), so you can use a keyboard connected to any port to control your bootloader.
And last but not least, this kernel release includes base support for the M2 Pro/Max/Ultra SoCs! We are not enabling installs on these machines yet as we still have some loose ends to tie, but you can expect to see support for this year's new hardware soon."
I find it pretty tasteless for HN to do that.
For one, I don't believe this place fosters a hostile environment, although it's definitely a place where people love to tell you how you're technically wrong about something.
For another, I would guess that there are a very limited number of websites that would opt into this sort of anti-traffic behavior. Hacker news could certainly choose to honor it, but it also feels within their right to bypass the block.
I wonder if there's a sort of middle ground, where HN alerts the user of the redirect that would have occurred, but still shoots the user to the desired location.
But now you're getting into user flows and begging the question as to why the redirect is there in the first place.
I'd love to know more about the perceived hostility, even reading up on Mastodon left me with more questions than answers.
It’s not limited to the Asahi project, either. The site isn’t safe for queer folks.
Could you be so kind as to link me to an example?
People have discussed Marcan's anime alter ego, certainly, but I've never seen anything transphobic in the slightest. Maybe it's all flagged before I get to see it, but I honestly can't figure out what you might even be referring to. I enjoy reading Asahi updates when they come up, so I am unsure how I could be missing something so 'constant'.
> It’s not limited to the Asahi project, either. The site isn’t safe for queer folks.
As a 'queer person' myself, I find that statement utterly ludicrous and I reject it completely.
This is pure and poor conjecture, just like the rumor (originating on chan boards and KF) that a person close to marcan had faked suicide. Exactly this sort of rumor mill is what is wrong with HN linking to Asahi developers.
> As a 'queer person' myself, I find that statement utterly ludicrous and I reject it completely.
Are you a cis gay? I remember a few cases where people reached out to have information redacted to dang and it took weeks. While the people mentioned above were digging into private lives. This site absolutely requires you to shut the fuck up about your own life if you are at risk of being turned into a "lolcow" or pedojacked or whatever else these people will come up with. I understand that's not a consideration yet for 'queer people' currently not conscripted to the front of the culture war.
Some of my most upvoted comments on here have been from a 'queer' perspective. It helps to assume good intentions and engage with others constructively and in good faith.
I must admit, I feel saddened by your dismissiveness of certain 'queer people'. You have no idea who I am, what my identity is, and yet you so casually dismiss members of the marginalised group you purport to be defending. How callous of you.
Perhaps the reason I can so easily dismiss your hysterical claim that HN is unsafe is that - in my day - 'unsafe for queer people' meant 'reasonable likelihood of getting a brick to the face', and not 'seeing words online you don't agree with'.
hn is unsafe in the way that it provides zero control over what you have submitted and a perfect history of your posts, mostly set in stone unless you email an administrator. at least reddit lets you self-service delete posts.
those are perfect conditions for a certain kind of group that spend way too much time digging up and correlating info to then start harassment campaigns that exceed 'seeing words online you don't agree with' quite often.
you can of course now go on to scold me and others with this problem about how we need to up our opsec or shouldn't post in the first place. i find such arguments, if you were to make them, entirely unconvincing. being aware of your risk profile is one thing, shifting all the blame for making it harder to retroactively rectify little pieces of information (these people found a place from a blurry 500x500 picture of a parking lot out a window) on the user is just a bad excuse for shitty UX.