I thought so too until I found out Thread currently (AFAIK) doesn't support multicast requests while Zigbee does, which can be hugely important for smart lighting with 30+ bulbs. Until that gets added to the spec (and supported) you might be better off putting the lighting part of the setup on Zigbee.
> Group messages are also important as they allow simultaneous control of several Matter Nodes through Multicast. In order to route this traffic into the Thread network, both Matter and Thread implement the Unicast Prefix-based IPv6 Multicast Addressing Scheme defined by RFC 3306.
> Thread defines a series of features to support multicast across a heterogeneous network (Thread and Wi-Fi/Ethernet Network segments) for multicast addresses with scope larger than realm local.
I got the phrasing a bit wrong, but it's Matter over Thread that doesn't support multicast on an application level. It's part of the spec that just shipped (1.6.1) but no controllers actually support it right now. It's about to ship with HA:
IIRC they're still offering Zigbee that you can switch to via a manual switching sequence, though some people say it still runs a little worse than the older Zigbee line(s).
I personally don't like the AI-rephrased titles, they feel too editorialized and similar to each other. I realise AI-rephrasing is necessary for the description, but I think the title should (optionally?) be left alone. Could be a toggle.
Not anymore, a lot of apps (from browsers to the system UI) adapt to whether you have a touch screen and whether you use it. For example, Windows Explorer and Edge (and Chrome) still use (relatively-)compact widgets on touchscreen-less computers.
At 100% scaling with "Compact view" on, Windows 11's File Explorer takes 135 pixels to get from the top of the titlebar to the top of the content. The same dimension in Windows 7 is 92 pixels. That's almost 50% vertical space bloat for no discernible benefit.
unless i misunderstand the implication as to their behavior on touchscreenful computers, this would seem to poorly address the concern upthread of explicitly expecting the touchscreen hardware, and thus the concomitant software annoyances, to become effectively unavoidable
Are you making this point from the context where you’ve never tried a touch screen computer?
This isn’t an unimplemented theory. You can head over to Best Buy right now and see what it’s like to use a touch screen laptop.
I feel like all this debate is taking place in an odd vacuum where a lot of us are talking about a bunch of potential problems with having a touch screen on a computer and all these problems are already resolved.
Maybe it’s similar to the whole iPhone duo thing where Apple users are just discovering all the caveats of a foldable phone, but we’ve already gone over all of it with competitors.
In general the vast majority of folks that make these comments are exactly from that viewpoint. It was a valid concern a decade ago--right now it just makes them uninformed.
The low percentage combined with "distillation attack" makes it sound like it was a few scattered requests across a bunch of attacks, and not the hundreds of dollars in third-party usage billed to random users. There's countless reports of OpenCode users impacted by this who woke up to $300-$1700 bills from Anthropic and OpenAI, but OpenCode didn't mention this or offer to compensate users. (Compensation can still come later of course but it's still worth noting right now)
Your viewing habits are not mined by Apple TV the same way that a smart TV does it.
If you use the Apple TV app and if you give permission to the app in the modal to link your HBO Max/Paramount+/etc. app, then that app can call a special API to donate your viewing history to the Apple TV app. You can just decline the prompt, or you can just not use the Apple TV app, and then the other streaming services have no recipient to give this data to.
Conversely, your TV runs something called ACR or Automatic Content Recognition where a screenshot of your TV input/app is taken every ~x seconds. At best, it distills it into a local signature and ships that off to some amount of servers. At worst (e.g.: laptop HDMI) it can send it for processing. Some TVs take screenshots much more often if you use a device connected by HDMI.[1]
The former is generally used for content recommendation, but we can also assume that it could potentially get pooled into stuff like App Store ads. The latter is also used to discern your political affiliation and target you for political campaign ads, among every other type of ad.
It uses a S10 chip, and it offloads to your Apple Intelligence-capable phone for inference. (There's a tiny "requires Apple Intelligence-capable iPhone" footnote somewhere) Basically the same way the Apple Watch has Apple Intelligence.
Honestly, just the new radios are a reason to upgrade. The S5 regularly cuts out and I have HomePod minis well within range going "no connection" for no reason.
reply