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…
Every OS has papercuts like this. Want me to write a story about Linux or Windows that is equally painful? Pick your poison .. i've dealt with it all.
macOS 26 breaks custom DNS settings including .internal
171–180 of 240 posts
Re: macOS 26 breaks custom DNS settings including .internal
#172Earlier quoted context omitted.
Its my strong belief that using AI in any capacity which does not upfront state "the following content was generated by artificial intelligence" is never acceptable. In most situations, allowing an AI to wield your name gives off the scent of "My time is more valuable than yours, so I've automated writing to you." It is quite disgraceful. If your use-case would be materially harmed by an upfront disclosure of AI gene…
How far do you take this policy? 1. Am I allowed to ask an AI to proofread a draft for grammatical errors? 2. Am I allowed to ask an AI to proofread a draft for technical errors? 3. In both #1 and #2, am I allowed to ask the AI to suggest revisions, or is it only allowed to point out what's wrong and why? 4. If I write a sentence like "Lucy's laughter ___ her underlying anxiety" and I'm having trouble coming up with…
Re: macOS 26 breaks custom DNS settings including .internal
#173Earlier quoted context omitted.
Every OS has papercuts like this. Want me to write a story about Linux or Windows that is equally painful? Pick your poison .. i've dealt with it all.
Sure, when was the last time a Linux update overwrote your DNS resolver settings?
I was unable to resolve it and ended up reinstalling.
Re: macOS 26 breaks custom DNS settings including .internal
#174macOS 26 has to be the most breaking version so far, its problems and intended breaking changes making my app dev life so hard this year. Just to name a few: - Reference Presets no longer allow setting arbitrary SDR nits, making it impossible to natively unlock 1600nits of brightness on MacBook Pros or 2000nits on Studio Display XDR which breaks my Lunar app [0] (this seems to be intended, no idea what hurt Apple tha…
As a hobbyist music producer with an interface always connected, that microphone indicator is so annoying and unnecessary. I can't believe it can't just be disabled outright. I like macOS but it's too opinionated and some of those opinions SUCK.
Re: macOS 26 breaks custom DNS settings including .internal
#175Earlier quoted context omitted.
How far do you take this policy? 1. Am I allowed to ask an AI to proofread a draft for grammatical errors? 2. Am I allowed to ask an AI to proofread a draft for technical errors? 3. In both #1 and #2, am I allowed to ask the AI to suggest revisions, or is it only allowed to point out what's wrong and why? 4. If I write a sentence like "Lucy's laughter ___ her underlying anxiety" and I'm having trouble coming up with…
Not parent commenter, but my answer is "no to all".
I don't really understand your philosophy if you're opposed to an LLM pointing out when someone got the tense wrong.
Re: macOS 26 breaks custom DNS settings including .internal
#176If 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
Re: macOS 26 breaks custom DNS settings including .internal
#177Bit off-topic. I mostly use Linux and I'm of the opinion that it's miles better than Windows, but I don't fully understand why people say MacOS looks bad? Ignoring the current Tahoe mess, MacOS felt relatively polished. I'm purely talking about UX here, as the OS is evidently buggy. The most popular Gnome themes are a re-impl of MacOS, so I can't be the only one.
"Your password is required to
log in"
Re: macOS 26 breaks custom DNS settings including .internal
#178Earlier quoted context omitted.
Its my strong belief that using AI in any capacity which does not upfront state "the following content was generated by artificial intelligence" is never acceptable. In most situations, allowing an AI to wield your name gives off the scent of "My time is more valuable than yours, so I've automated writing to you." It is quite disgraceful. If your use-case would be materially harmed by an upfront disclosure of AI gene…
How far do you take this policy? 1. Am I allowed to ask an AI to proofread a draft for grammatical errors? 2. Am I allowed to ask an AI to proofread a draft for technical errors? 3. In both #1 and #2, am I allowed to ask the AI to suggest revisions, or is it only allowed to point out what's wrong and why? 4. If I write a sentence like "Lucy's laughter ___ her underlying anxiety" and I'm having trouble coming up with…
But... AI generated content is a slippery slope. Someone earlier today asked me to "review" a 50 page document they had completely generated with AI yet obviously not reviewed themselves. It is embarrassing.
Re: macOS 26 breaks custom DNS settings including .internal
#179macOS 26 has to be the most breaking version so far, its problems and intended breaking changes making my app dev life so hard this year. Just to name a few: - Reference Presets no longer allow setting arbitrary SDR nits, making it impossible to natively unlock 1600nits of brightness on MacBook Pros or 2000nits on Studio Display XDR which breaks my Lunar app [0] (this seems to be intended, no idea what hurt Apple tha…
Re: macOS 26 breaks custom DNS settings including .internal
#180macOS 26 has to be the most breaking version so far, its problems and intended breaking changes making my app dev life so hard this year. Just to name a few: - Reference Presets no longer allow setting arbitrary SDR nits, making it impossible to natively unlock 1600nits of brightness on MacBook Pros or 2000nits on Studio Display XDR which breaks my Lunar app [0] (this seems to be intended, no idea what hurt Apple tha…
Not a macOS user, but I feel like that might still work.