Papercuts like this are why I moved away from macOS.
I will say, I don't love the use of LLMs to write these bug reports. It's probably fine if reviewed, but at least review for things like "worked on macOS 25", which obviously didn't exist. If that wasn't caught, how sure are you that the rest of the report is accurate. We all want the bugs fixed, but people are going to start throwing out the obviously LLM written reports rather than have to validate each claim, since the author probably didn't.
duped 57 seconds ago [-]
Using LLMs for any kind of writing is unethical, with the narrow exception of translation. If you didn't take the time to compose your words thoughtfully then you aren't owed the time to read them.
neilsharma425 1 minutes ago [-]
Has anyone found a working workaround yet? I use dnsmasq for .local dev routing and held off updating after seeing this but curious if there is a viable path forward short of waiting for Apple to patch it.
himata4113 12 minutes ago [-]
Still wishing for the day apple is split into the hardware and the software company. I want their silicon, but I will never use their (arguably terrible) operating system. If I can't run my own kernel and kernel modules then it's a device that I don't own. Firmware is alright in some cases, but my laptop next to me is running core boot just to prove a point.
t-sauer 5 minutes ago [-]
But you can run your own kernel on Macs, no? Isn‘t driver support the issue?
binaryturtle 18 minutes ago [-]
I run a setup like that on my (outdated) Yosemite machine to provide multiple private TLDs for local deployment/development needs.
I set that up in like 2014? Even back then it was known already that the quick /etc/resolver way was the deprecated way to do things. So I guess they finally killed that feature off?
The proper (more awkward) way is to use scutil directly (which then stores the settings in some binary plist somewhere, I assume).
Maybe try this and see if it still works afterwards?
Congeec 28 minutes ago [-]
If you have ScreenTime turned on. Port :8080 is occupied and your ubuntu apt-get in a docker build gets hash mismatch because they obviously modified packets. Let alone I am having another issue of unable to delete a private key in Keychain Access.
The whole macOS thing is amateur
1718627440 24 seconds ago [-]
Why does macOS use ports above 1024 by default? There is a reason it is reserved to be used by OS services.
delduca 3 minutes ago [-]
Port 5000 is also ocupied on macOS.
24 minutes ago [-]
38 minutes ago [-]
adamamyl 1 hours ago [-]
Before others jump in: I already use Linux (and used to run FreeBSD as my desktop operating system).
bgentry 27 minutes ago [-]
Thanks for sharing your report, it's frustrating to see things like this break in minor patch updates. Small tip for GitHub Gist: set the file format to markdown (give it a .md extension) so that the markdown will be rendered and won't require horizontal scrolling :)
pissedoffadmin 6 minutes ago [-]
[dead]
1 hours ago [-]
Heer_J 41 minutes ago [-]
[dead]
Rendered at 16:12:14 GMT+0000 (Coordinated Universal Time) with Vercel.
I will say, I don't love the use of LLMs to write these bug reports. It's probably fine if reviewed, but at least review for things like "worked on macOS 25", which obviously didn't exist. If that wasn't caught, how sure are you that the rest of the report is accurate. We all want the bugs fixed, but people are going to start throwing out the obviously LLM written reports rather than have to validate each claim, since the author probably didn't.
I set that up in like 2014? Even back then it was known already that the quick /etc/resolver way was the deprecated way to do things. So I guess they finally killed that feature off?
The proper (more awkward) way is to use scutil directly (which then stores the settings in some binary plist somewhere, I assume).
Maybe try this and see if it still works afterwards?
The whole macOS thing is amateur