Woke up this morning after a good night sleep, had my breakfast and then checked for software updates for Chrome – Chrome 142 has been released and with that after the update was installed I then checked for uBlock Origin Lite updates and the release of version 2025.1028.1744 was announced but that’ll appear in the usual stores over the next couple of days (just filter updates, nothing major mention in the github changelog). Microsoft Edge will probably receive an update to Edge 142 probably at the end of this week or possibly next week depending upon the urgency of the update.

There has been a rumour that next year Microsoft will announce a 26H1 version specifically for the X2 chip from Qualcomm and then in 26H2 the mainstream release for both x86-64 and ARM will be made available. It’ll be interesting to see whether the 26H1 will be part of the 26200 series where the support is backported from a newer build number or whether they just base 26H1 on a new build series. It’ll be interesting to see whether FRED makes it way into Patherlake and whether it’ll be supported out of the box with Windows. Given how closely Intel work with Microsoft and how FRED is dated further back than 4-5 years ago I wouldn’t be surprised if there was already support in the kernel with the Microsoft and Intel ensuring that any blind spots are addressed.

I’m still giving Bitwarden a try and everything appears to be going ok although it would be nice if it could pick up Android apps easier like how Google’s own password manager can without having to manually point the app to the right username and password. With that being said, it does integrate well with Edge and the TOTP makes life a lot easier and doesn’t rely on a separate extension so maybe overtime it’ll grow on me. I have noticed that with Microsoft Edge that the performance is slightly better and behaves more reliably when waking up from my laptop going to sleep but then again I have noticed with recent Chrome updates that those issues I had experienced have disappeared so I’m sure it is a situation of a Chrome bug that gets fixed up or has been fixed by Microsoft but hadn’t made it’s way to the main Chrome release.

Posted in ,

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.