I just like to re-iterate
this request and by giving an example on how
this can actually work
out:
Some clipboard tools on OSX create "temporary" data into
clipboards,
only to remove it within a second again. An example are
tools that
perform "text expanding".
Here, there's a similar
problem for clipboard recording tools like
ours: The recording tool
needs to tell whether the data in the
clipboard is temporary and thus
should not be recorded.
The solution:
http://www.nspasteboard.org/Site/Transient.htmlAs you can see
there, many developers have already adopted this
protocol. As you can
see, it's just a little effort, and it doesn't
get ignored. And it
makes the user experience better for all of us.
Having our
recording tool simply ignore any clipboard data that comes
from
1Password as you suggest as a work-around is not user friendly
and
not even 100% safe:
1. If the user copies non-secret data from
1pw, it won't get recorded,
although that's what he's using our
clipboard recoding tool for.
2. We cannot even tell all the time
where the clipboard contents
originate from. All we can do is watch
the front process and ignore
anything from 1pw - but that's not
foolproof because a too-fast
content switch might get missed, thereby
our tool identifying the
wrong app as the owner.
So, please -
you're practically the leader in password pasting on the
Mac. If you
go ahead and simply add a special extra flavor
(com.agilebits.password
or even something more generic) when you add a
password to the
clipboard, you'll set the standard quickly. You have
the power to
make this work. Others will follow. You know that, admit
it! :)
Thomas