Fair point, I forget how utterly stupid businesses, particularly large businesses can get about boneheaded requirements that they mandate but do not use or do need, but could better solve it in a separate path rather than mandating it on what should be the 'wrong' product category.

Particularly surprising to forget since I'm basically continuously exposed to that in my job, but guess it eventually faded into the background of me not thinking explicitly about it anymore..

Problem with that is thinking it's vaguely new... This has been possible pretty much all along. The Cameyo demos I saw seemed underwhelming compared to almost every alternative I've seen...

Except it is a whole desktop, but with ability to request an app to maximize... It's kind of embarassingly bare bones for this level of claiming it makes ChromeOS just do Windows...

I certainly would agree with that direction, however this has been an option for an eternity and broadly hasn't moved the needle for Windows market share.

Once upon a time VirtualBox made an effort for this to work as a feature, and eventually dropped it in favor of just using Windows RDP to the same end. Doing it via a browser may be somewhat more convenient, but not fundamentally more accessible than RDP...

After watching a demo, I'd say this is in fact a step back from 'seamless' RDP, since you just get a web page with what looks like full-desktop RDP in it.

Exactly this. Airlines are now essentially banks with a side hustle flying planes.

I've used Firefox Beta as my primary browser on my Android phones for years and have never encountered this. Maybe there's an issue with some specific features used by sites I don't visit. Doesn't prove anything but I guess one anecdote deserves another.

> Sure, do this instead of better tech

Regardless of what you think of the new mascot, do you really think the same people responsible for drawing pretty pictures of foxes are the same ones designing "better tech" and writing code and fixing bugs? Groups of people can do more than one thing at a time.

And I'd guess this is also an attempt to raise some money and awareness to the browser. At this point it doesn't matter how great Firefox "tech" is, they have lost the popularity context against Chrome and Chromium knockoffs, and will never get it back. Google will do and spend whatever it takes to keep Chrome on top, so Mozilla is probably looking for ways to at least retain what they have and keep the lights on.

I fully anticipate there will be branding changes, like adding a '+' for rewards and consumers will learn fairly quickly that merchants frequently don't want to deal with the more expensive 'plus' transactions.

Can't blame them, your rewards points/cash back is just being charged to the merchant.

Or you just carry a couple of cards, one with no rewards that people will actually take, and maybe one or two with rewards that some merchants will still take.

The biggest thing to get right is some simple 'branding' so consumers actually know at a glance what cards might work or might not.

It's just bonkers that the credit card companies have basically made the merchants pay for the credit card companies to motivate cardholders to use the cards that merchants don't want them using in the first place. Those 'cash back' and 'rewards' represent some of cost of goods that a consumer can't really get away from without these measures.

It's right there in the summary, that merchant's would start being able to decline the credit cards with 'points' and 'cash back'. I presume this would come with some rebranding to be phased in, like 'Visa+' and 'Visa Business', with a lot of merchants refusing 'Visa+' just like they reject other high-fee cards.

Z-Wave v. Zigbee largely stemmed from some awkward licensing to implement Z-Wave.

I think the thing driving Matter-over-Thread seems to be a desire to have more commonality with IP stacks, notably Apple's Homekit not having the adoption Apple wanted and Apple deciding to maybe go with something that the device manufacturers will go for, but not wanting to have to have a totally different stack for dealing with Zigbee vs. wifi devices.

So here's Matter, based on IP, with endorsement of 'Thread' as one of the transports. Now talking to a Matter device over Wifi is pretty similar to talking to a Matter device over Thread, except Thread is not generally IP routing.

So Thread is an inherent mesh design, unlike Bluetooth or Wifi, and low power. Bluetooth kind of sucks for this application since it's peer to peer. Wifi somewhat better but it means you have to inject access points even if coverage could be had mesh-style, with a light switch serving as a perfectly viable relay while doing it's job otherwise. Also you have an actual shot of running a Thread radio on modest battery much longer than Wifi.

What is this obsession with pedophilia? I'm really getting rather suspicious of MAGA. I suspect your average Catholic priest or Southern Baptist youth pastor thinks about nude children less than most MAGA individuals.

With a president who solves an existential threat by finding the best expert he can find, and using his own formidable political skills and charisma to run interference for that expert.

Seriously, Comacho was a meathead, but Iâ(TM)d vote for him.

I think the woosh is directed the wrong way, the comment had an example of exactly and obviously useful data, so it has to be sarcastic.

"Matter-over-Thread" is actually a solid strategy compared to most 'cloud connected' wifi smart devices.

This is more akin to Zigbee/Z-Wave. It's a local, non-internet scheme for local communication and control. You can get a totally local air-gapped Matter over Thread setup running without internet. It's if you pick a cloud-connected thread border router when you get in trouble, but you can roll your own, e.g. with Home Assistant platform providing a way forward.