kogir

It’s the passkey that should be protected with MFA (biometrics, PIN), not the account with the third party service.

My Yubikey supports passkeys and protects them with a PIN of my choosing. No services need challenge me further.

I’ve not tried with 10gbps or faster links, but since we’re talking home use my success with 2.5 gbps links on standard amd64 hardware would suggest you’re wrong.

Modern CPUs are quite capable. The problem isn’t performance, but power use.

I’ve always solved this with Multiple Active Result Sets and stored procedures.

Collect the data in the stored procedure with temp/in-memory tables and return minimal, non-duplicated, related result sets.

Single round trip, still accumulates results in efficient bulk batches, and allows results to be processed by the client as they stream in.

With secure boot, full disk encryption, and robust backups, this risk should be largely mitigated, right?

That’s what I’m personally banking on. I think anyone with the resources to bypass these would first just use a rubber hose.

MacOS assumes you won’t full screen every app because all of them ship with large enough, high enough resolution monitors that full screening a single app is a waste of valuable space. Unlike on cheap laptops with 1080p screens.

I suppose you could splurge for a Mac desktop and then get the cheapest, smallest screen possible, but I hope it’s rare.

Yes, and highlighting a failing in email that cannot be fixed, but which is addressed in other services where confidentiality is desired.

OIDC is usually limited to a small selection of providers.

Any properly grounded device will do that with specifically incorrect electrical wiring and/or a shoddy charger. Did this happen with a properly wired outlet, and an undamaged Apple charger?

I have doubts that it did, as that would warrant a safety recall.

  Another example for all you computer folks out there: ultimately, all software
  engineering is just moving electrons around. But imagine how hard your job would
  be if you could only talk about electrons moving around. No arrays, stacks,
  nodes, graphs, algorithms—just those lil negatively charged bois and their 
  comings and goings.

I think this too easily skips over the fact that the abstractions are based on a knowledge of how things actually work - known with certainty. Nobody in CS is approaching the computer as an entirely black box and making up how they think or hope it works. When people don't know how the computer actually works, their code is wrong - they get bugs and vulnerabilities they don't understand and can't explain.

I really miss the feature of CSR devices that allowed keyboard and mouse use before OS boot, and wish any modern Bluetooth receiver was capable of it. Is it a patent issue?

Am I misunderstanding this? Isn’t this just the view, rating, and comment data required to offer the service?

Building an interface to search that data is exactly how you’d evaluate a recommendation engine.

While I’m all for physical controls, especially ones that self-adjust to reflect the state of the remote device at all times, I wonder if the author just doesn’t know you can finely adjust volume in iOS control center by force/long pressing and then dragging.

wget begs to differ.

Kidding aside, where exactly does it end? How do you consider when you’ve hit “too much” and how many pieces must be split out when you do? Should every product in the Office suite be offered only individually?