>If they really cared, if they had an ethical bone in their body, they would release 18.7.3 to the public WHICH THEY ALREADY HAVE STAGED.
>This is more like blackmail where they are dangling these security issues over everyone's head as some scare tactic to upgrade, instead of giving everyone access to the iOS 18 security patch which already exists.
18.7.3 was released a month ago. Anyone who cared about security updates would have already gotten it using the beta workaround. Anyone who's apathetic about updates isn't going to be swayed by 18.7.3 vs 26.2.
Note the CVEs discussed were patches almost a month ago with iOS 18.7.3. If you used the beta workaround[1] to get that, you're safe and don't have to upgrade to iOS 26... for now.
For windows specifically cached memory looks very similar to unused memory so when someone is complaining about "windows is using all my memory" it's very unlikely to be caused by caches.
Yeah the source is terrible. I'd expect at least some sort of explanation on how they arrived at that conclusion, eg. "someone on breachforums claims to have it for sale" or "some whistleblower at instagram reported". If it's the former, it's possible that instagram themselves aren't at fault, eg. they got it via phishing or credential stuffing.
>Congrats to the latest buyer: you bought pure schwag. Whatever value was in that list got milked long before it ended up public.
Nobody is buying your account specifically, they're buying it bulk. At that scale the fact that a percentage of accounts are fake/burner/bots is baked whatever the buyer is expecting. If anything, the bigger issue is bot accounts, not random privacy-oriented people's burner accounts.
>but it seems like a really good high flash point oil.
On what basis? Using the list of smoke point table someone else linked[1], tallow does indeed have a high smoke point, but it's unclear how it's better than many other oils in that list (peanut, sunflower, soybean) which are far easier to procure.
Most people do not live near "beef operations". Moreover processing tallow is part of procurement. If you value your time at the prevailing minimum wage, it's pretty hard to beat a gallon of vegetable oil for $10.
Pretty much all, if not all, cooking oils/fats when heated past the smoke point create this problem.
Avocado oil has a smoke point of 500F, which is what I use for high heat cooking. By contrast lard is only 370F, which means it supplies less flexibility than avocado oil.
sadly one of the most frustrating things is that everyone groups saturated fats in one big group. there is lots of evidence that only specific types of saturated fats actually cause CVD, in particular some specific configurations of palmitic acid. the other saturated fats are not nearly as problem causing.
Unless something changed with 11, this is opt in, with a specific "save to your microsoft account option". I really don't see the issue here.
>- Hardware attestation
This is either a rehash of the "TPM 2.0 requirement" point above, or just outright false.
>- Telemetry/Data Collection
>- Extensive diagnostic data collection
This are the same thing restated
>- Forced automatic updates
>- Limited update deferral for Home users
Again, these are just the same thing.
>- Feature updates bundled with security updates
That's basically... every commercial OS out there? Good luck getting security updates on android (if your OEM even provides it) if you're not on the latest version. Some linux distros even have it as a selling point, aka. rolling release.
>- Device Management (Enterprise)
>- Intune/MDM integration
These are the same thing AND you have to jump through hoops to enable it. I really don't see the issue here.
>- Copilot integration
>- Windows Autopilot
You can just... not use it?
>- Azure AD requirements
???
Is this just restating the microsoft account requirement?
To be fair, while many of those are indeed optional or non-issues, the problem is that user experience has been degraded in w11 while there has been almost zero value-add for end users.
reply