2,794 karma · joined February 27, 2011
It has at least improved with the second category recently that it seems to be more right than wrong. But it still tends to work your query into whatever results it got, which makes it downright dangerous for when people are doing searches on health-related information.
And that should change going forward with smaller chiplets being integrated in package, vs huge Ultra chips.
Because that market, in aggregate, only spends extra on monitors for gaming.
None. Those ads are additional revenue for the "publishers". Apple doesn't restrict ads in all content.
If an article has those ads, I just block the source in News. There's got to be some other source that both covers the topic and has self respect.
Comments were explicitly disallowed from JSON since the beginning, because they could be used as a side-channel for vendor-specific extension mechanisms and harm interoperability.
Apple Silicon only has support for 16k pages via DART, rather than the 4k pages typically used by AMD/Nvidia. The requirement to coordinate a major change of drivers to understand 16k pages is why both PCIe GPU and eGPU do not work (or rather, did not work - TinyGPU is a compatibility layer that adds eGPU support and is used for AI workflows).
The Mac Pro's biggest redeeming feature for a data center was that it was rack-mountable. The ARM version was still mostly an empty case. It remained mostly for its ability to support PCIe cards for video and audio production use cases, such as live broadcasting.
> especially since they're crawling back to Nvidia to license their interconnect
Licensing the interconnect for broader compatibility. They support other interconnects as well.
You can stand up to government requests when it is legal to do so. Eventually you have to decide to abide by the law or leave the market.
Once there was a standardized interpretation for malformed html, there was a chance that we could have treated that as a transparent conversion layer to xhtml. That isn't how WHATWG went, however.
It actually doesn't help as much for anti-theft, because a thief still might be smart enough at this point to check their phone for AirTag notifications. The audible tone may not even hit in a theft instance.
You can - there will be spurious phone notifications and audible notifications.
But many also haven't updated their custom input code to support the current remote design either.
If you do not have access to your personal Apple account on your work laptop, you would need to find some other passkey provider with native integration.
Under Settings > Privacy and Security, look to see that Firefox is listed and has access under "Passkeys access for Web Browsers". Unlike a native app which only needs passkeys for its own services, Firefox needs access for every potential service you might hit over the internet.
Then under General -> Autofill and Passwords, you'll see any apps which are registered as system password managers. Unfortunately this is a subset of the ones which register on iOS and I'm not familiar who has done integration yet in their Mac release - Chrome (with GPM) for instance is not listed even though it is available on iOS.
The passkey provider vendors are motivated to serve their customer's needs (the end users, and secondarily enterprise deployments) over non-customer needs.
So Apple platform support (for example) will only send an attestation when one is configured via MDM. Your provisioned work device can indicate to work systems that it is in policy.
The compatibility-limiting risk, if it exists, is more likely from regulators putting their hands on the scale and pushing for security policies that would prevent synchronization and backup, and requiring attestations to make sure those policies are in effect.