4 ms·
Thing is though, it can be worked around as long as js is enabled. Client side fingerprinting plus server side data storage and you get the same functionality
by moffkalast 4y ago
Thing is though, it can be worked around as long as js is enabled.
Client side fingerprinting plus server side data storage and you get the same functionality in a roundabout way.
- 0x0 4y agoSo you get to share preferences with everyone else that matches your fingerprint :)
- moffkalast 4y agoThat's the punishment for blocking local storage. :P
- smoldesu 4y agos/punishment/reward
- treeman79 4y ago/s Even better we could store login information this way. What could go wrong?
- jefftk 4y agoYou don't even need JS: blocking cookies doesn't (but really should) disable the browser cache, which can reasonably reliably store information. Note that you can't use the cache to work around browsers blocking third-party cookies because all the major browsers fragment the cache by site.
- Spivak 4y agoI would actually love to see a demo of this used for comedic effect. "Unlogin, use your browser fingerprint as your password. We already, know who you are, why put up with the hassle of typing a password."
- SilasX 4y agoI actually wrote up an April Fool’s parody based on that premise, modeled after Google’s NoCaptcha announcement. http://blog.tyrannyofthemouse.com/2021/04/leaked-google-initiative-no-more.html http://blog.tyrannyofthemouse.com/2021/04/leaked-google-init...
- cpeterso 4y agoSome websites already do something similar: if you are logging in from an "unrecognized" (unfingerprinted) browser, they might force you to 2FA authenticate and then give you have the option to "trust this browser" for future logins. You might still need to log in with your password, but not 2FA. Of course, that fingerprint can break when your browser auto-updates to a new version.