191–200 of 240 posts
Earlier quoted context omitted.
Not parent commenter, but my answer is "no to all".
...then I guess my next question would be, why? How do you feel about spellcheck? Should mobile users turn off autocorrect unless they disclose that it's turned on? I don't really understand your philosophy if you're opposed to an LLM pointing out when someone got the tense wrong.
Afaik ".internal" isn't reserved/defined anywhere, it's just a convention some people/devices use, and doesn't have anything to do with the root cause here (a custom resolve.conf or whatever it is called in macos changing after an update), no?
https://www.icann.org/en/board-activities-and-meetings/mater...
A look on Google or Wikipedia would also clear that up faster than I can type this response https://en.wikipedia.org/wiki/.internal
Earlier quoted context omitted.
It is not too difficult to allow your PiHole to serve you globally (but does requiring opening some ports in your firewall == additional security risk). There is a simple checkbox within the DNS's web interface to `Allow WAN Requests`. You'd then only run into issues of accessing your local IP addresses if those hosts aren't configured correctly within your network rulesets . ---- I am a user , not an expert ; by tra…
Yeah that can work, though at that point I start to consider just exposing my "internal" DNS to the world at large - who cares if secret_service.mydomain.net can be seen by everyone to resolve to 192.168.88.4? You can also do VPN tricks, too.
I think my major concern here would be if people were going to websites which might be considered illegal within their jurisdiction (e.g. guest_DNS_user searches for out of state abortion providers — while you[r DNS] live[s] in Texas).
Perhaps the State sees guest_DNS_user's query to plannedparenthood.com, then decides your vehicle tag is worth tracking for potential out-of-state (via e.g. Flock cameræ)... or that you are guilty of facilitating an abortion for someone else... all because your DNS server provided IP resolution for guest_DNS_user to Planned Parenthood Colorado (et.al).
----
This would have been too far-fetched for me to have considered/written, even just a few years ago. It's all reality, now. Are you targetable enough?
DNS leaks are another reason I don't care for LittleSnitch (which pre-resolves IP address before the accept/deny pop-up even appears.
Earlier quoted context omitted.
...then I guess my next question would be, why? How do you feel about spellcheck? Should mobile users turn off autocorrect unless they disclose that it's turned on? I don't really understand your philosophy if you're opposed to an LLM pointing out when someone got the tense wrong.
Who said anything about spellcheck?
Earlier quoted context omitted.
Good tip, I didn't realize the browser would automatically resolve any subdomain of localhost to 127.0.0.1/::1 as well these days. I tested on Chrome but I assume this is true for Safari as well?
Just tried it on my Mac and sadly it doesn’t seem like it. I’m still on Sequoia, so possibly it does it on Tahoe, but probably unlikely. That’s a shame. It’d be nice if someone on the Safari team added this though to match Chrome and Firefox!
It's not quite the same, but I've moved to using *.localhost for all my local web dev work. All modern browsers will resolve *.localhost to 127.0.0.1 internally. No need to setup any DNS resolvers or edit your hosts file. But that only really helps you when you're dealing with websites in a browser, and when you want the address to resolve back to your local machine. So it wont help you with other programs like pytho…
It works for me on Tahoe.
Earlier 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…
In general, I think those use cases are fine. 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.
Earlier 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…
I think that's a good rule of thumb for AI-generated output.