Use case for per-protocol icons

John Bailey rekkanoryo at
Fri Aug 3 18:24:55 EDT 2007

Hash: SHA1

David Totten wrote:
> On 8/3/07, Sean Egan <seanegan at> wrote:
>> On 8/3/07, Etan Reisner <pidgin at> wrote:
>>> The problem would be determining when to show the icon, we can do it for
>>> things like AIM Encryption where the capability is part of the buddy
>>> information, but not for client<->server encrypted connections among other
>>> cases.
>> I think we should only show a buddy as secure if we can guarantee
>> end-to-end encryption.
> Maybe this could be an option when setting up the account. Let the
> user decide if they think it's secure or not.

I wouldn't add this as an account option to Pidgin, myself.  I would take Etan's
earlier suggestion about columns that plugins can touch in the treeview and make
a plugin that would add the lock icon to buddies belonging to accounts the user
marks as secure in said plugin.  The plugin could feel free to add an account
option for this if it so chooses, though.

(I hope my intended meaning is clear here.)

Version: GnuPG v1.4.6 (GNU/Linux)


More information about the Devel mailing list