11–20 of 397 posts
Ya, fucking with paste is a pet peeve of mine. What's a good argument for fucking with paste?
Nowadays it’s a (hopefully accidental) countermeasure against password managers!
The problem is that even if I read the code, or more likely chose to trust that someone has, it's not guaranteed to remain true for future updates. The author's scruples may weaken with time, or they might sell the extension, etc. (I think Chrome's extensions auto-update, but even if they didn't I'd still have to remember that this extension is one that I can't assume it's safe to update.)
Right up there with hijacking Ctrl-F.
Seems like a cool idea but perhaps a slightly less offensive name would be good.
seems like an unmaintained fork of the less provocative, https://github.com/jswanner/DontF-WithPaste
Ya, fucking with paste is a pet peeve of mine. What's a good argument for fucking with paste?
The only one I've ever heard is "security." Sometimes people try to "yeah it's because for security we don't want some tool to paste credentials or clickjacking mumble something malware hacking clipboard spyware javascript browser" but most of the time the truth is "our sec people need to show controls for hardening the authentication process so they came up with that and we just did it because it wasn't worth the fi…
Seems like a cool idea but perhaps a slightly less offensive name would be good.
Right up there with hijacking Ctrl-F.
Edit: Apparently Firefox has the `permissions.default.shortcuts` config option
UNKNOWN: Services.perms.UNKNOWN_ACTION [0]
ALLOW: Services.perms.ALLOW_ACTION [1]
BLOCK: Services.perms.DENY_ACTION [2]
PROMPT: Services.perms.PROMPT_ACTION [3]
And in the site information panel you can disable the Override keyboard shortcuts permission on a per-site basis. Neat, doesn't solve the paste override issue though. Source: https://support.mozilla.org/en-US/questions/1241294#answer-1...
Ya, fucking with paste is a pet peeve of mine. What's a good argument for fucking with paste?
When you have a confirmation field, like signups that require you to type your email and then verify your email, blocking paste stops the user from typing a typo and then copy-pasting the typo into the confirmation field. Another use case is when you want the user to type in the name of the project or resource before they delete it, sites sometimes block copy and pasting the name to avoid having users get into that h…
This argument is indefensible. Browsers have had autocomplete for over a decade, Contact book applications that store email addresses have existed over a decade, password managers that also handle email addresses over a decade.
> In order to provide the smoothest experience as possible, the extension needs to know when you change active tabs. In order for the extension to know about that event, it needs the tabs permission, which Chrome describes as "can read and change all your data on websites you visit." That description is very scary, and is certainly not what this extension is doing. Being an open-sourced project, you can always read a…
https://github.com/jswanner/DontF-WithPaste?tab=readme-ov-fi...
Ya, fucking with paste is a pet peeve of mine. What's a good argument for fucking with paste?
The only one I've ever heard is "security." Sometimes people try to "yeah it's because for security we don't want some tool to paste credentials or clickjacking mumble something malware hacking clipboard spyware javascript browser" but most of the time the truth is "our sec people need to show controls for hardening the authentication process so they came up with that and we just did it because it wasn't worth the fi…