Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
lapcat
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
lapcat
5d ago
> doing the test on the same computer wouldn't have caught this problem. Doing it on a second computer wouldn't have caught this problem either with macOS 26.3 and earlier, because it was introduced in 26.4.
2.
▲
by
lapcat
5d ago
Look in the Keychain Access app.
3.
▲
by
lapcat
6d ago
> This is pretty much how it's suppose to work... No, it's not, and that's not how it ever worked in macOS 26.3 and earlier. This change was introduced in 26.4 for some reason.
4.
▲
by
lapcat
6d ago
Then you're in trouble.
5.
▲
by
lapcat
6d ago
This was introduced, unannounced, in macOS 26.4! See my blog post for more information: https://lapcatsoftware.com/articles/2026/9/4.html
6.
▲
by
lapcat
6d ago
I've tested with VMs. However, I'm unclear about the relationship if any between VMs and the secure enclave.
7.
▲
by
lapcat
6d ago
The iCloud keychain is separate from the login keychain. The Passwords app doesn't use the login keychain.
8.
▲
by
lapcat
6d ago
Migration Assistant uses the old Mac, which can unlock its login keychain and allow the keychain items to be copied.
9.
▲
by
lapcat
6d ago
Does the macoOS login keychain get backed up by Time Machine backups Yes > in a way that could restore the keychain if the original machine's Secure Enclave is lost or destroyed? Apparently not
10.
▲
Copying login keychain no longer works on Secure Enclave Macs with macOS Tahoe
(derflounder.wordpress.com)
4 points
by
lapcat
8d ago
|
1 comments
11.
▲
by
lapcat
8d ago
Original title "Manually copying login keychain files from one Mac to another no longer works on Secure Enclave-equipped Macs running macOS Tahoe" trimmed to fit HN maximum length.
12.
▲
by
lapcat
9d ago
I've just learned that initial-scale was removed from the MDN recommendation only a few days ago... by the submitted article author! https://github.com/mdn/content/pull/45479
13.
▲
by
lapcat
9d ago
> I argue that the latter is preferable I disagree vehemently. I couldn't disagree more. The text has to be readable. If you force the reader to zoom in order to read the text, your website is fundamentally broken. Moreover, neither
14.
▲
by
lapcat
9d ago
> I researched and tested this extensively the other day. `<meta name="viewport" content="width=device-width">` is all you need. This is incorrect. Try adding an <img> that's wider than the device wid
15.
▲
by
lapcat
9d ago
I would add this: <meta name="viewport" content="width=device-width, initial-scale=1"> All you need is initial-scale=1, not width=device-width, which is redundant. "You do not need to set every viewport
16.
▲
by
lapcat
10d ago
> when incompetence becomes an accepted excuse I couldn't have been any more explicit that it's not an accepted excuse: "Google has no excuse for incompetence".
17.
▲
by
lapcat
10d ago
Fielder's "The Rehearsal" on HBO was madly brilliant.
18.
▲
by
lapcat
10d ago
> just for "I want to show you the address bar" I just said that there was another reason: "Also, the first screenshot shows that my start page in Chrome is not Google Search, which is in fact quite relevant to the content
19.
▲
by
lapcat
10d ago
This submission appears to be a self-promotional advertisement by the developer, who created a HN account literally an hour ago. "Please don't use HN primarily for promotion. It's ok to post your own stuff part of the time, b
20.
▲
by
lapcat
11d ago
Interesting, thanks for testing!
21.
▲
by
lapcat
11d ago
Huh? I can't make sense of this criticism. What "faith" do you need? Every screenshot in the blog post is the same size, which made it easier to do the <img> tags. (I write my blog in raw HTML.) Also, the first screensh
22.
▲
by
lapcat
11d ago
> Wonder if OP is experiencing a version of that on his Mac? No.
23.
▲
by
lapcat
11d ago
I did: "As far as I can tell, www.google.com is the only site exempted by Chrome." My screenshots do not show this, but my screenshots were not intended as proof, merely as explanation. Chrome is available to everyone and used by
24.
▲
by
lapcat
15d ago
Idiocracy was not a prediction. Rather, it was a satire of the present, set in the future, much like Woody Allen's Sleeper. The future setting was merely an excuse to exaggerate the present. This is why Idiocracy appears predictive, be
25.
▲
by
lapcat
17d ago
> housing and food for everyone This obviously won't happen, because we could do it now, could have done it already, long before AI. Let me know when AI solves greed and cruelty.
26.
▲
by
lapcat
21d ago
> Whatever line you think is reasonable to draw here, would you trust a bad president with it? I don't think this is a good argument, because it's oddly specific. You can't trust a bad President to properly enforce any l
27.
▲
by
lapcat
21d ago
I think you may be taking for granted the political dupoloy and candidate equality. Third-party candidates are almost always unknown and remain unknown to the public, because they have no money to advertise and achieve name recognition, get
28.
▲
by
lapcat
21d ago
> "It's part and parcel to a system that fully embraces free speech," said Tom Garrett, a vice president at the Institute for Free Speech. "All Americans have the right to express themselves and exercise their right
29.
▲
by
lapcat
25d ago
> Comments can veer wildly off the original topic I'm not complaining about tangents, though, but rather about dismissive insults. A tangent is a conversation starter, whereas a knee-jerk dismissal is a conversation stopper.
30.
▲
by
lapcat
25d ago
Thank you. I appreciate the comment. It's just frustrating that knee-jerk reactions are ubiquitous in the Hacker News comments, on every popular submission, despite the site guidelines urging the opposite.
More ›