They did. They also said IE6 was the last version of IE.
They probably couldn't go through with it. Increasing the system requirements would leave things in a weird state where you and a friend might both be running Windows 10, but yours is version locked because it's can't upgrade to the newest version as the hardware doesn't support it, while your friend can continue receiving updates. It's better to call the new version "Windows 11" to reduce confusion. Which is exactly what they did.
Furthermore, all Windows 10 users received a free upgrade to Windows 11. So it would be difficult to argue that MS' statement is at all relevant to any damage when the plaintiff already had/has a copy of Windows 11 available to them for free.
From the description this sounds like analytics. Generally these frameworks track how users use an app and anonymize it, and aggregate all the information together. You can use this to determine how users are using the app. For example let's say you have a feature you think is super useful. But you get your analytics back and almost nobody is using it. You may decide it is not worth maintaining and drop it in favor of focusing on areas of the app people are using. Or perhaps you may determine a particular common pattern of usage indicates a screen's layout is confusing, and work to fix that.
In this case it's easy to imagine many users weren't aware this was happening in this particular app. I didn't dig into what exactly what was happening here nor what the claims were so I won't speculate further.
1, Microsoft should add an API to allow apps to declare content to be private/non-indexable. At the same time, they should add overrides in Recall so users can choose to force index or force ignore specific apps regardless of how they mark their content. The power should be in the hands of the user. If the user indicates they want to index their Signal activity, it should be done in an unblockable way. Conversely, the default would allow for ignorant users' privacy to be respected. And Signal would not have to engage in unsupported behavior that could potentially break down the line (imagine a future Windows where rendering to Recall and the screen is treated the same to simplify the code base and reduce bugs).
2. When I run software on my PC I am granting it permission to use my property to perform some task. If that program goes off and starts doing other things I may decide it is violating that trust and terminate it. That is my right as a PC owner. Signal is interfering with Recall's operation which doesn't really fit in with its basic premise as a messaging app and if it is not configurable this can be seen as sketchy behavior. Since they have announced this behavior publically it indicates it is not meant to be hidden behavior which does make the behavior more legitimate.
3. Apps should not claim that content that users can see cannot be permanently stored. This is at best naive and at worst a bold-faced lie. For example I could take a picture of my computer screen and Signal would never know. And of course the person being spoken too can remember what has been said. Users who are under the impression that what they say will have no consequences may end up behaving differently than if they were aware of the reality that anything they put "out there" may very well never go away.
If io_uring requires root then this is a nothingburger.
Raymond Chen, Microsoft developer, uses the phrase "It rather involved being on the other side of this airtight hatchway" to refer to such "exploits".
RADIO SHACK LEVEL II BASIC READY >_