Gentlemen! You can't fight in here this is the War Room!

Correct. They removed the ability to connect to anything but an Azure VM instance (of various kinds). There was talk of them 'working' on 'adding this functionality' as if it was never there in the first place and removed by a dickwad product manager to force people into the Azure ecosystem, but even if they did put it back in you'd still need either a corporate or educational - not personal - MS account to launch it.

The 'Remote Desktop' app in the app store, which is the product 'Windows App for Windows' was directly forked from, at first merely rebranded and then feature locked, does allow you to connect to local machines and does not require a corp or edu ms account to use. But that's dead now, so your only option from a Windows desktop is mstsc, which doesn't handle live desktop resizing etc etc.
Kind of weird how they treat Windows Desktop users as second-class citizens for their shiny new RDP app, but let IOS, Macos, and Android enjoy the nicer experience. Fucking weird. Which is why I'm thinking they're going to gimp those too at some stage soon.

Ackshually it's called 'Windows App for Windows', which is a COMPLETELY different product to Windows App for IOS/Android/Mac. The latter support local connections without needing a *corporate*or *educational* MS account login to even run the thing. 'Windows App for Windows' is a very particular kind of retarded. The other Windows Apps are very useful and I dread the day MS decides to fuck with those as well.

Don't Look Up

It seems Linus himself views it the same way I did, from https://lore.kernel.org/rust-f...

I would say the 'hard stance' the maintainer took was itself not professional though. They were refusing to listen to reason, using emotionally charged language, and ultimately were complaining about something that wasn't even a real concern - a consumer of their API that they didn't have to maintain anyway. They were being a dick from the start and stonewalling out of fear for something they didn't even understand.

However brigading on social media was not the answer of course.

No there isn't. Every other single wireless mouse on earth manages to be used while charging. This excuse is pure mental gymnastics.

The 'load' of the mouse sensor and wireless circuitry is measurable in the milliamps, and the charging input in amps. There neither needs to be any load on the battery while charging it as the USB input can handle the load, nor any issues with damaging the battery if loading it instead of taking operational power directly from the USB connection.

There is absolutely no justifiable technical reason for doing this. It's just dumb.

I'd argue that this doesn't even count as form over function because it still looks stupid when charging.

"We have Wuhang at home"
"But muuuuuuum"

Maybe 'those' people shouldn't be managing domain certs in the first place XD

This might cause an issue for a few small sites, but I'll be surprised if anyone besides their own close circles notice.

"affecting about 0.4% of their domain validations"
Ok

"This could literally be thousands of SSL certs."
Wake me when it's 8.5 million.

"This could take a lot of time and potentially cause outages worldwide starting July 30 at 19:30 UTC"
...or not because customers have been notified.

"Be prepared for a long night of cert renewals. DigiCert support line is completely jammed."
Why do you need to call them to renew a cert? Just use the self-service web interface.

I'm expecting a total nothingburger from this one.

We had systems that were bootlooping well beyond 15 reboots and the only fix was to get on the console and boot in safe mode to delete the file in question. Whoever at MS said this is taking the piss.

Try out OpenRGB. It's a little rough around the edges but it does its job and sucks far less than any OEM's own RGB crapware.

No worries!

Please, do