You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
This is a serious question. I'm an IT expert, IT business owner for 14 years, and have been in tech my whole life – this all to say, that I do my research pretty thoroughly and think about things before I jump to conspiracies.
What is the process and policy applied when it comes to checking for stuff like kill switches? All the time, when services and apps are scheduled to be decommissioned, we see a kill switch version released with the necessary code to receive the kill signal from whatever API it's connected to, often with a message or something stating to the user that the build is no longer supported, and if you repy on it, so what, we don't care, have a nice day (or don't).
Google does this all the time, other companies do this. Is Microsoft doing this with 2407.4000? I believe this is a valid question that should be asked. I don't see anywhere online where anyone has released information about 2407.4000. Microsoft has stayed completely silent, and they usually release a change log stating what's been fixed/optimized/etc. There are a few users over at the WSA GitHub page that have both commented, @'d active devs that were on the project, and created discussion pages, such as this one, all of which have been met with radio silence. If anyone, even @MustardChef, knows what exactly changed, please do let post it, because there is zero online about this, and it has me concerned.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
This is a serious question. I'm an IT expert, IT business owner for 14 years, and have been in tech my whole life – this all to say, that I do my research pretty thoroughly and think about things before I jump to conspiracies.
What is the process and policy applied when it comes to checking for stuff like kill switches? All the time, when services and apps are scheduled to be decommissioned, we see a kill switch version released with the necessary code to receive the kill signal from whatever API it's connected to, often with a message or something stating to the user that the build is no longer supported, and if you repy on it, so what, we don't care, have a nice day (or don't).
Google does this all the time, other companies do this. Is Microsoft doing this with 2407.4000? I believe this is a valid question that should be asked. I don't see anywhere online where anyone has released information about 2407.4000. Microsoft has stayed completely silent, and they usually release a change log stating what's been fixed/optimized/etc. There are a few users over at the WSA GitHub page that have both commented, @'d active devs that were on the project, and created discussion pages, such as this one, all of which have been met with radio silence. If anyone, even @MustardChef, knows what exactly changed, please do let post it, because there is zero online about this, and it has me concerned.
Beta Was this translation helpful? Give feedback.
All reactions