I ran into this when trying to paste my generated password into the password field on some kind of financial site and I think it is still the most egregious case of security theater I’ve seen yet.
Anyway, you want the “don’t fuck with paste” extension, available on both chrome and firefox.
Is Sony actually a good guy for holding this patent so that no one else can go and do this shit either?
Yes. Can’t wait to get rid of Google home.
I’m back! Thanks!
How do they enforce this kind of thing? How can we possibly trust that meta isn’t going to say “oh yes we take privacy very seriously” and then simply continue harvesting everything they do now?
Same happened to me
not sure if this is the right place to post this but my profile appears to not exist anymore? i can log in, read stuff, post this comment, but it looks like the api is returning not found for my profile or something.
Nice. You should check out devcontainers if you haven’t already. Maybe it deviates a little from the dev/prod parity idea, but you can use it with a compose file like you described. It’s saved my current team quite a bit of headache in maintaining local dev environments and keeping everyone in sync as the project evolves.
If you have to try really hard to meet their password requirements, that’s how you know it’s super secure.
At home vs. for work are very different. At home, I self host as much as I can. At work, I use as many managed services as I can. Especially databases.
Nice, didn’t know about that one. I imagine there are side effects to disabling it globally though? Those goofy OTP code inputs implemented as six single digit inputs jumps to mind, they probably rely on the paste event. The extension works similarly but lets you only enable it for problematic sites.