- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
Have to use Windows for work (I’ve asked), the ads have been getting worse and worse on my work laptop. Today got a game ad notification… That’s clearly too far, right? Like I have to clear notifications, so I have to see it
Omg I loathe those icons. They are so much harder to use than words, cuz I still have to hover over them to make sure it’s the right thing.
Windows 11, in general, feels so shit after being on Ubuntu.
But I see Linux has decent touchscreen support now so as soon as I’m done at this job, that sucker is getting formatted 😈
MS goes out of their way to make shit harder than it needs to be.
For example. The store, they have a store for business where you can simply whitelist known apps buts it’s a PITA to setup AND they have been threatening to decom it for ages
https://learn.microsoft.com/en-us/microsoft-store/microsoft-store-for-business-overview
Want to add safety/security features like secuirty keys. Well if you do it on a non domain joined machine you can just sign into a m365 account to enable a passkey or yuibijey as a second factor.
Want to do that in a business environment. Congrats now you have to deploy a windows CA and issue user certificates to tie to this. Even if you are signing the machine into m365 with ADAL.
They go out of their way to add complexity and failure points.
I read a thing just the other day about essentially that. Not that specific issue, but the way their timekeeping works (by default) and is a disaster (literally) when it fails.
https://arstechnica.com/security/2023/08/windows-feature-that-resets-system-clocks-based-on-random-data-is-wreaking-havoc/
That is crazy. According to a comment on that article, most BIOS uses UTC (as does Linux, obviously), but Windows uses localtime for some reason, so it converts UTC to localtime after boot, then back to UTC when it needs to do little things like networking or TLS.
Yes, it used to break dualbooting, since it reset the clock each time, it was driving me mad.
The solution was simple - erase the ntfs partition.