You noted on the phone hardware but not the software so I'll comment on that. Recently OnePlus has announced as of Android 16 that they will restrict bootloader unlocking to only those who fill out an application.
Nothing Phone 3 and all prior Nothing phone bootloader are still unlockable to this day with no call to restrict it. I would know, I have a Nothing Phone 3 running Shizuku and am waiting for Google to move Play Integrity off of its Kanban board so I can root again. Their forums have a strong development presence and as far as I'm concerned this is the one of the last good holdouts on this new restriction standard.
Pixel was the de facto standard for unlocked bootloaders. However, Google is the core of the "registered developers only" movement for their phones, killing sideloading and removing Pixel images from the development models in AOSP. I no longer support new Pixels (certain used ones are still good, don't get the 6 series though they are BAD).
I got the new Keychron M5 ergonomic mouse with all the gaming features and I love it. It didn't take me long to get used to it and David praised it as well on LTT's Short Circuit channel.
This is the BEST write up I have ever seen on the topic. Had no idea it was out there and explained a lot about the inner workings for security I wasn't expecting.
Is it? Because it sounds like it is the same as what Samsung is doing with Knox. If you unlock your bootloader they have a way to track that now and it hurts the experience on the device. Want to sideload your apps in protest? You'll only be allowed to sideload apps from developers Google screens and says are okay. Want to use custom firmware on your hardware? You can, but they won't pass the integrity checks and even if you pay for the apps they can become incompatible with your device. And as someone else pointed out they stopped providing Pixel configs for AOSP so even getting people to try and make custom ROMs will be more difficult.
Samsung did it first, but Google just took it to the next level.
The Phone 1 and 2 have official lineage os support as well. Nothing is still bootloader unlock friendly (for now). Phone 3 is too new for LineageOS but is still an excellent phone with a good development community on their forums.
This article supports your comment and should be higher up considering two phones 4a and 6a were recently recalled due to being unsafe. Pixel 10 has this feature on at cycle 200 while you can turn it off on the Pro and Pro XL. But what good is 7 years of updates if they are going to hurt your battery charging speed after less than 2 years? Samsung battery tech is FAR superior.
This used to be the case but Google is actively working to kill unlocking the bootloader on their devices (and all devices really) through their Play Integrity Validation. So while you may be able to install ROMs and add Gapps you'll slowly find that less and less apps from the Play Store will work due to stricter integrity requirements from Google; even if you bought the app. The current hoops required to run a custom OS and not be detected by the new framework is daunting with many landmines like people installing software they don't understand to get "Strong" integrity or paying for keyboxes that ultimately get banned.
Google is quickly becoming developer unfriendly and I would encourage people to look into the mess that is Play Integrity before suggesting Pixels, or any Android for that matter, in the context of custom ROMs.
Had this experience today. It was incredibly frustrating. Had to meme about it since I can't get approval for my fix until tomorrow at 9am in another meeting.
I think it is the equivalent of running 'make clean' after a build from source? You can do this manually building arch user repo packages to free up space because the executable and package that you installed is already there through pacman. However, updates in the future would require building those make dependencies again so it might save you time in the future, but probably irrelevant to you running the app today.
Just wait until you get to Transunion's site. It is a dumpster fire of consisting of the worst sign up I've ever seen, "Contact our social team" and "If you haven't logged in for awhile create a new account. I could not believe how awful it was. I had to just call and do it over the phone.
It was in response to the Naomi Brockwell post she did on Twitter about businesses using WiFi, Bluetooth and Location Services to track you in public locations. You can Google it directly "NBTV Advice from Defcon" or this link: https://nbtv.substack.com/p/advice-from-defcon-turn-off-bluetooth
I actually came here to echo this exact sentiment. I was on Lastpass until their first breach and then on Bitwarden both cloud and self-hosted until a few months ago when I set up with Proton. I liked Bitwarden so I put off trying ProtonPass. One weekend I set it up and ended up putting my 2FA items in as well. It feels absolutely seamless to use. The email aliasing for websites is so easy for making new website accounts. In my desktop and laptop browser the way it automatically offers to autofill the 2FA is so clean. I can't see myself going back unless Proton gets prohibitively more expensive or the product declines in usability/security. If you are currently using Proton's suite of apps give Protonpass a try. You can easily import from Last pass/Bitwarden and use both to compare side by side.
Archinstall works until it doesn't. Recently I tried Luks and BTRFS more than 6 times leading to a script error each and every time. Could I have done something simpler and archinstall work? Possibly. But it offers those things out of the box and for it to fail each and every time ultimately led me back to the wiki to do it manually.
You noted on the phone hardware but not the software so I'll comment on that. Recently OnePlus has announced as of Android 16 that they will restrict bootloader unlocking to only those who fill out an application.
Nothing Phone 3 and all prior Nothing phone bootloader are still unlockable to this day with no call to restrict it. I would know, I have a Nothing Phone 3 running Shizuku and am waiting for Google to move Play Integrity off of its Kanban board so I can root again. Their forums have a strong development presence and as far as I'm concerned this is the one of the last good holdouts on this new restriction standard.
Pixel was the de facto standard for unlocked bootloaders. However, Google is the core of the "registered developers only" movement for their phones, killing sideloading and removing Pixel images from the development models in AOSP. I no longer support new Pixels (certain used ones are still good, don't get the 6 series though they are BAD).