mark at kingant.net
Tue Aug 27 12:10:00 EDT 2013
On Sun, Aug 25, 2013 at 11:51 PM, Tomasz Wasilczyk
<tomkiewicz at cpw.pidgin.im> wrote:
> 2013/8/26 Mark Doliner <mark at kingant.net>:
>> I kind of hinted at this in the devel at conference.pidgin.im MUC, but
>> you could maybe do some combination of the first and second options:
>> Have the plugin enable itself by default and have the plugin watch for
>> "?OTRvxx?" messages. The plugin would want to avoid altering Pidgin's
>> UI unless:
>> - The user has received an incoming "?OTRvxx?" message and has
>> selected "yes, use OTR"
>> - The user has manually turned on OTR. I'm not sure how this would
>> work, since the plugin would already be enabled. Maybe the user
>> generates a key? Or views the config UI?
> This approach have one advantage: it encloses all OTR code within a
> plugin. However, I don't see any fair solution for usability: if user
> enables the plugin, he is entitled to expect that it works and doesn't
> require going somewhere and flipping another switch to turn it on.
Yeah, I agree. Adding OTR-specific code to the core seems like the
best solution to me.
More information about the Devel