Right now in the United States let's say this scenario happens. Johnny riding his motorcycle like a dick weaving in and out of traffic and speeding. He was also holding his phone. When pulled over they ask him to put hands on dash. Cops then take the keys and the phone. If Johnny only has his phone setup to unlock with a pin or a pattern on the screen they cannot force him to open the device.... BUT.... If his phone has facial recognition or fingerprint they can request Johnny to unlock it.
Find out why and you will find the answer you seek.
Can something open-source with so many branches be corrupted?! I agree that there will be effort. But, being able to read, modify, and share the code is what make Linux. The Restrict Act is what I think is the response.
Do not use ANY single-sign-on crap (Apple, FB, Google, MS, etc)
Do NOT use any 2FAs offered by "helping 3rd party companies"
Do not tie any of your biometrics to any of your logins or IDs (fingerprint, face-ID)
Do NOT use any password managers that upload your passwords "securely onto the cloud"
Study FIDO2, passless keys, digital-ID alliances (ID2020, etc) and how they all point to the same direction: CBDCs, digital biometric (eventually body-embedded) identification in all digital activities, incl. banking, gov services and using the internet or utilities or paying for anything, social credit score, CDBDs and Everything As a Service (that can be cut off)
Off-topic: I've always wondered why no one builds an app where, if you enter a certain PIN, it puts up a phony "false bottom" screen with a goatse background while it vaporizes the contents and activates your dead hand switch.
"Yes officer, I know I should be more careful but the passcode is 1234."
Right now in the United States let's say this scenario happens. Johnny riding his motorcycle like a dick weaving in and out of traffic and speeding. He was also holding his phone. When pulled over they ask him to put hands on dash. Cops then take the keys and the phone. If Johnny only has his phone setup to unlock with a pin or a pattern on the screen they cannot force him to open the device.... BUT.... If his phone has facial recognition or fingerprint they can request Johnny to unlock it.
Find out why and you will find the answer you seek.
That's my point. Why would the OS company sell us out so badly?
They have bigger more powerful customers than the user.
More users need to go to linux.
Agreed, but that seems like security through obscurity. If linux goes mainstream, I think it will get corrupted by TPTB.
Can something open-source with so many branches be corrupted?! I agree that there will be effort. But, being able to read, modify, and share the code is what make Linux. The Restrict Act is what I think is the response.
Standard reminder:
Do not use ANY single-sign-on crap (Apple, FB, Google, MS, etc)
Do NOT use any 2FAs offered by "helping 3rd party companies"
Do not tie any of your biometrics to any of your logins or IDs (fingerprint, face-ID)
Do NOT use any password managers that upload your passwords "securely onto the cloud"
Study FIDO2, passless keys, digital-ID alliances (ID2020, etc) and how they all point to the same direction: CBDCs, digital biometric (eventually body-embedded) identification in all digital activities, incl. banking, gov services and using the internet or utilities or paying for anything, social credit score, CDBDs and Everything As a Service (that can be cut off)
Off-topic: I've always wondered why no one builds an app where, if you enter a certain PIN, it puts up a phony "false bottom" screen with a goatse background while it vaporizes the contents and activates your dead hand switch.
"Yes officer, I know I should be more careful but the passcode is 1234."
There were really good cheating apps that hid everything, but I think 2023 requires you to have a pretty much empty device.
Extremely underrated post.
https://www.forbes.com/sites/quickerbettertech/2023/05/14/this-week-in-small-business-tech-google-aims-to-kill-passwords/amp/